Postgres Pro
Downloads
Home   >   mailing lists

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

From Sergei Kornilov
Subject Re: Making WAL receiver startup rely on GUC context for primary_conninfo and primary_slot_name
Date
Msg-id 67523061547115016@iva5-d3020dc3459d.qloud-c.yandex.net
Whole thread Raw
In response to Re: Making WAL receiver startup rely on GUC context forprimary_conninfo and primary_slot_name  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Making WAL receiver startup rely on GUC context forprimary_conninfo and primary_slot_name  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
Tree view 
Hello

> I was just double-checking the code, and it is possible to remove the
> part from RequestXLogStreaming() which sets slotname and conninfo to
> '\0', so I removed that part from my local branch to simplify the
> code.

Without both ready_to_display and cleaning in RequestXLogStreaming we do not show outdated PrimaryConnInfo in case
walreceiverjust started, but does not connected yet? While waiting walrcv_connect for example.
 

regards, Sergei

pgsql-hackers by date:

Previous
From: Dean Rasheed
Date:
Subject: Policy on cross-posting to multiple lists
Next
From: Michael Paquier
Date:
Subject: Re: [Sender Address Forgery]Re: error message when subscriptiontarget is a partitioned table