On Thu, 2008-01-24 at 00:01 -0300, Alvaro Herrera wrote:
IMO it's a usability bug which will be gone when we move to
pg_class.reloptions -- you won't need to set random values for options
you don't know what to set to.
But this is a problem in *this* release (and the last also?).
As for
On 1/23/08, Tom Lane [EMAIL PROTECTED] wrote:
Steven Flatt [EMAIL PROTECTED] writes:
I noticed that the Postgres autovacuum process was vacuuming some tables
that had enabled = false in pg_autovacuum.
I think what is happening is that because you set
pg_autovacuum.freeze_max_age to zero,
The following bug has been logged online:
Bug reference: 3898
Logged by: Steven Flatt
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.4
Operating system: FreeBSD 6.1
Description:Postgres autovacuum not respecting pg_autovacuum.enabled
= false
Details:
I
Steven Flatt [EMAIL PROTECTED] writes:
I noticed that the Postgres autovacuum process was vacuuming some tables
that had enabled = false in pg_autovacuum.
I think what is happening is that because you set
pg_autovacuum.freeze_max_age to zero, the thing always thinks that it's
time to force an
Tom Lane escribió:
Steven Flatt [EMAIL PROTECTED] writes:
I noticed that the Postgres autovacuum process was vacuuming some tables
that had enabled = false in pg_autovacuum.
I think what is happening is that because you set
pg_autovacuum.freeze_max_age to zero, the thing always thinks
