| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: logical changeset generation v6.2 |
| Date: | 2013-10-28 16:28:46 |
| Message-ID: | CA+TgmoYVBuc2QcwXpUUnbvYys23S7onkgV56w-VuHsbF47w-Nw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Oct 28, 2013 at 12:17 PM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
>> In general, I don't think waiting on an XID is sufficient because a
>> process can acquire a heavyweight lock without having an XID. Perhaps
>> use the VXID instead?
>
> But decoding doesn't care about transactions that haven't "used" an XID
> yet (since that means they haven't modified the catalog), so that
> shouldn't be problematic.
Hmm, maybe. But what if the deadlock has more members? e.g. A is
blocking decoding by holding AEL w/no XID, and B is blocking A by
doing VF on a rel A needs, and decoding is blocking B.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-10-28 16:28:47 | Re: OSX doesn't accept identical source/target for strcpy() anymore |
| Previous Message | Andres Freund | 2013-10-28 16:26:52 | Re: Darwin: make check fails with "child process exited with exit code 134" |