Re: Preventing deadlock on parallel backup - Mailing list pgsql-hackers

From Lucas
Subject Re: Preventing deadlock on parallel backup
Date
Msg-id CAEWGB6_jv4QcJtuTdhpqkwrmWH1n+o0a89QuUWhkd4tDskV=tw@mail.gmail.com
Whole thread
In response to Re: Preventing deadlock on parallel backup  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers

Tom,

Yes, it is what I mean. Is what pg_dump uses to get things synchronized. It seems to me a clear marker that the same task is using more than one connection to accomplish the one job.


Em 08/09/2016 6:34 PM, "Tom Lane" <tgl@sss.pgh.pa.us> escreveu:
Lucas <lucas75@gmail.com> writes:
> The queue jumping logic can not use the distributed transaction id?

If we had such a thing as a distributed transaction id, maybe the
answer could be yes.  We don't.

I did wonder whether using a shared snapshot might be a workable proxy
for that, but haven't pursued it.

                        regards, tom lane

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: CVE-2016-1238 fix breaks (at least) pg_rewind tests
Next
From: Andres Freund
Date:
Subject: mdtruncate leaking fd.c handles?