Alvaro Herrera wrote:
Yeah, we have a configurable autovacuum log on 8.3.
Sorry, I looked but didn't see it.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
The following bug has been logged online:
Bug reference: 4020
Logged by: Joseph S
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.5
Operating system: CentOS 5
Description:RFE: have way to log autovacuum activity
Details:
When autovacuum decides to vacuum
Flavio Botelho wrote:
I know the application should not be doing this. But i wonder if lots of the
complaints about postgres performance couldnt be related to problems like
this. I suggest that you change the behaviour of something like that from
silently accepting the string value to throwing a
From this snipped you can see that the Bitmap Heap scan returns 123
rows, but the BitmapAnd under it returns 0. I would find it useful to
determine how many rows were thrown out by the recheck.
-> Bitmap Heap Scan on d (cost=4959.18..16848.23
rows=754 width=10) (actual
