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 103671544630104@myt5-262fb1897c00.qloud-c.yandex.net
Whole thread Raw
In response to Re: Making WAL receiver startup rely on GUC context for primary_conninfo and primary_slot_name  (Andres Freund <andres@anarazel.de>)
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

> This allows the state of walrcv and startup to diverge, they could e.g. have different configuration, due to
differentlytime config reloads.
 
So we have exactly same problem with, for example, hot_standby_feedback, right?
We change hot_standby_feedback value, reload it and we can have 'show hot_standby_feedback' different to currently
runningwalreceiver.
 
But why we have nothing about hot_standby_feedback in pg_stat_get_wal_receiver()?
Where is difference?

regards, Sergei

pgsql-hackers by date:

Previous
From: Andreas Karlsson
Date:
Subject: Re: Reorganize collation lookup time and place
Next
From: Tom Lane
Date:
Subject: Upgrading pg_statistic to handle collation honestly