| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Francisco Olarte <folarte(at)peoplecall(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Question / requests. |
| Date: | 2016-10-03 20:27:51 |
| Message-ID: | CA+TgmoYbe9bm=ExUHe30UNjvhtvSukoAfXmk_GzcLoU9R8RBhA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Emrul | 2016-10-03 20:30:31 | Re: Learning to hack Postgres - Keeping track of ctids |
| Previous Message | Robert Haas | 2016-10-03 20:26:32 | Re: Learning to hack Postgres - Keeping track of ctids |