| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Alexey Bashtanov <bashtanov(at)imap(dot)cc>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Autovacuum fails to keep visibility map up-to-date in mostly-insert-only-tables |
| Date: | 2014-10-09 21:11:26 |
| Message-ID: | 20141009211125.GI29124@awork2.int |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2014-10-09 18:03:00 -0300, Alvaro Herrera wrote:
> Bruce Momjian wrote:
>
> > I agree this is a serious problem. We have discussed various options,
> > but have not decided on anything. The TODO list has:
> >
> > https://wiki.postgresql.org/wiki/Todo
> >
> > Improve setting of visibility map bits for read-only and insert-only
> > workloads
> >
> > http://www.postgresql.org/message-id/20130906001437.GA29264@momjian.us
>
> I hate to repeat myself, but I think autovacuum could be modified to run
> actions other than vacuum and analyze. In this specific case we could
> be running a table scan that checks only pages that don't have the
> all-visible bit set, and see if it can be set.
Isn't that *precisely* what a plain vacuum run does?
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2014-10-09 21:16:46 | Re: Autovacuum fails to keep visibility map up-to-date in mostly-insert-only-tables |
| Previous Message | Kevin Grittner | 2014-10-09 21:10:42 | Re: Autovacuum fails to keep visibility map up-to-date in mostly-insert-only-tables |