| From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
|---|---|
| To: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "pgsql-committers(at)postgresql(dot)org" <pgsql-committers(at)postgresql(dot)org> |
| Subject: | Re: pgsql: Teach autovacuum about multixact member wraparound. |
| Date: | 2015-05-08 17:23:16 |
| Message-ID: | 1674734486.2821256.1431105796306.JavaMail.yahoo@mail.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Robert Haas <rhaas(at)postgresql(dot)org> wrote:
> This patch leaves unsolved the problem of ensuring that emergency
> autovacuums are triggered even when autovacuum=off. We'll need
> to fix that via a separate patch.
I think we also need something like your previously-posted
multixact-truncate-race.patch as a follow-on. I'm not at all
convinced that there is no possibility of truncating new data as
things stand; and even if that is true now, it seems terribly
fragile. (Only mentioning it because it wasn't noted in the commit
message.)
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2015-05-08 17:24:30 | pgsql: Minor ON CONFLICT related comments and doc fixes. |
| Previous Message | Robert Haas | 2015-05-08 17:00:34 | pgsql: Teach autovacuum about multixact member wraparound. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-05-08 17:25:22 | Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0 |
| Previous Message | Robert Haas | 2015-05-08 17:00:34 | pgsql: Teach autovacuum about multixact member wraparound. |