Re: Making WAL receiver startup rely on GUC context forprimary_conninfo and primary_slot_name - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Making WAL receiver startup rely on GUC context forprimary_conninfo and primary_slot_name
Date
Msg-id 20190111180451.5sojlylsx5e7xgkp@alap3.anarazel.de
Whole thread Raw
In response to Re: Making WAL receiver startup rely on GUC context forprimary_conninfo and primary_slot_name  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Hi,

Thanks for chiming in.

On 2019-01-11 12:52:08 -0500, Robert Haas wrote:
> And on that basis I'm inclined to think that Andres is really quite
> correct to be worried about this.  The problem he's talking about here
> is very low-probability because the race condition is narrow, but it's
> real, and it surely needs to be handled somehow.

I think it's also going to get more likely with projects we really got
to tackle like providing more builtin support for failing over to
different systems and such.

Greetings,

Andres Freund


pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Acceptable/Best formatting of callbacks (for pluggable storage)
Next
From: Andres Freund
Date:
Subject: Re: Ryu floating point output patch