I insert data every second in my table. Every minute I delete from the
table some row to keep max 1 rows in the table.
At the beginning deletes consume about 20% CPU time. After 24 houts
every delete needs up tu 100% CPU time (updates too).
Vacuuming doesn't help.
After I restart postmaster,
On Tue, 2003-07-01 at 08:10, Hilary Forbes wrote:
I'm just trying to improve performance on version 7 before doing some
tests and hopefully upgrading to 7.3.
At the moment we have
B=64 (no of shared buffers)
N=32 (no of connections)
in postmaster.opt which I take it is the equivalent of
Thanks.
Some theoretical questions.
The documentation says that Effective Cache Size sets the optimizer's
assumption
about the effective size of the disk cache ( that is, the portion of the
kernel's disk
cache that will be used for PostgreSQL data files ).
What then will be the effect of
