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 Raw
In response to Re: Preventing deadlock on parallel backup  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
<p dir="ltr">Tom,<p dir="ltr">Yes, it is what I mean. Is what pg_dump uses to get things synchronized. It seems to me a
clearmarker that the same task is using more than one connection to accomplish the one job.<br /><div
class="gmail_extra"><br/><div class="gmail_quote">Em 08/09/2016 6:34 PM, "Tom Lane" <<a
href="mailto:tgl@sss.pgh.pa.us">tgl@sss.pgh.pa.us</a>>escreveu:<br type="attribution" /><blockquote
class="gmail_quote"style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Lucas <<a
href="mailto:lucas75@gmail.com">lucas75@gmail.com</a>>writes:<br /> > The queue jumping logic can not use the
distributedtransaction id?<br /><br /> If we had such a thing as a distributed transaction id, maybe the<br /> answer
couldbe yes.  We don't.<br /><br /> I did wonder whether using a shared snapshot might be a workable proxy<br /> for
that,but haven't pursued it.<br /><br />                         regards, tom lane<br /></blockquote></div></div> 

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?