| From: | Ondřej Světlík <osvetlik(at)flexibee(dot)eu> |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Autovacuum of pg_database |
| Date: | 2016-05-05 15:35:58 |
| Message-ID: | 572B685E.9020902@flexibee.eu |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Dne 5.5.2016 v 17:19 Ondřej Světlík napsal(a):
> Dne 5.5.2016 v 17:16 Ondřej Světlík napsal(a):
>> Hello again,
>>
>> we have another strange problem with autovacuum. The process goes well
>> until it reaches the table pg_database (in some databases, not all),
>> then it loops over it forever (until I run vacuum full analyze on that
>> table, simple vacuum doesn't help):
>>
>> 2016-05-05 17:13:33 CEST 34818LOG: automatic vacuum of table
>> "somedatabase.pg_catalog.pg_database": index scans: 0
>> pages: 0 removed, 233 remain
>> tuples: 0 removed, 5817 remain, 0 are dead but not yet removable
>> buffer usage: 87 hits, 0 misses, 0 dirtied
And now the same goes for pg_authid. Sorry for spamming, I hope this is
the last one.
Ondřej
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ondřej Světlík | 2016-05-05 15:42:17 | Very long startup after crash with no message in log |
| Previous Message | Ondřej Světlík | 2016-05-05 15:19:59 | Re: Autovacuum of pg_database |