u15074 <[EMAIL PROTECTED]> writes:
> Can you specify more exactly what you mean with update rate? I moslty perform
> inserts on the database (is that what you mean?).
Sure, inserts/updates/deletes.
> Also I do not understand, why checkpoint does not touch WAL, but RAM. I thought
> that a checkpo
Zitat von Tom Lane <[EMAIL PROTECTED]>:
> Probably insufficient disk bandwidth. If you have two drives available,
> try putting the WAL files (pg_xlog directory) on a different drive from
> the data files. Assuming you have adequate RAM, updates will be mainly
> limited by writes to WAL, while ch
u15074 <[EMAIL PROTECTED]> writes:
> By the way, if you say, checkpointing is happening in the background, I don't
> know what causes the pauses.
Probably insufficient disk bandwidth. If you have two drives available,
try putting the WAL files (pg_xlog directory) on a different drive from
the dat
Zitat von Tom Lane <[EMAIL PROTECTED]>:
> A checkpoint pushes out all unwritten data since the last checkpoint.
> So yeah, it stands to reason that if you increase the time between
> checkpoints, each checkpoint will take longer. Whether this is really
> a problem is not clear --- the checkpoint
On 21/07/2003 07:30 u15074 wrote:
To improve the performance of PostgreSQL, resp. to avoid too frequently
occuring
checkpoints, it is recommended to increase the number of wal files
(checkpoint_segments).
So I increased the number of checkpoint segments to be able to write a
lot of
data into the da