| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Francisco Olarte <folarte(at)peoplecall(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Question / requests. |
| Date: | 2016-10-03 21:44:16 |
| Message-ID: | 20161003214416.GA597461@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas wrote:
> On Fri, Sep 30, 2016 at 11:20 AM, Francisco Olarte
> <folarte(at)peoplecall(dot)com> wrote:
> > After some messages due to vacuumdb auto-deadlocking itself on the
> > system tables when doing paralell vacuum of a full database I
> > suggested adding some flags to make vacuumdb process schemas. I was
> > asked wether I could write a patch for that and I am thinking on doing
> > it.
>
> What messages are you seeing, exactly? "auto-deadlocking" isn't a thing.
https://www.postgresql.org/message-id/57EBC9AE.2060302%40163.com
I wonder if the real answer isn't just to disallow -f with parallel
vacuuming.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2016-10-03 21:55:24 | pnstrdup considered armed and dangerous |
| Previous Message | Gilles Darold | 2016-10-03 21:23:56 | Re: proposal: psql \setfileref |