| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Ondřej Světlík <osvetlik(at)flexibee(dot)eu>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Autovacuum of pg_database |
| Date: | 2016-05-06 14:17:04 |
| Message-ID: | 13485.1462544224@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> These are all shared catalogs. There are others, so you may still see
> more. We got another report for pg_database
> https://www.postgresql.org/message-id/A9D40BB7-CFD6-46AF-A0A1-249F04878A2A%40amazon.com
> so I suppose there really is a bug. I don't know what's going on there.
I think it's pretty obvious: autovacuum.c's rule for detecting whether
some other worker is already processing table X is wrong when X is a
shared table. I propose the attached patch.
regards, tom lane
| Attachment | Content-Type | Size |
|---|---|---|
| autovac-shared-table-handling.patch | text/x-diff | 7.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2016-05-06 16:05:47 | Re: Autovacuum of pg_database |
| Previous Message | Thomas SIMON | 2016-05-06 10:12:52 | Autovacuums not triggering anymore |