Tom Lane wrote:
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
Why are you running a vacuum every 45 seconds? Increase your fsm_pages and
run it every hour.
If I understood his description correctly, he's turning over 10% of a
500-row table every minute. So waiting an hour would mean 3000 dead
row
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> Why are you running a vacuum every 45 seconds? Increase your fsm_pages and
> run it every hour.
If I understood his description correctly, he's turning over 10% of a
500-row table every minute. So waiting an hour would mean 3000 dead
rows in a 500-l
Hello,
Perhaps you could provide some more detailed information?
Example of queries?
Type of hardware?
Operating system?
Why are you running a vacuum every 45 seconds? Increase your fsm_pages and
run it every hour.
Are you sure the vacuums are trampling eachother and thus getting more
than one
vac
Hi
I am using Postgres 7.3.4 over linux Redhat 7.3 on
i686 machine.
My app has one parent table and five child tables. I
mean the parent table has a primary key and child
tables have foreign key relationship with parent.
My App is doing 500 inserts initially in each table.
After all this done, w
