Re: Parameter name standby_mode
От | Mario González Troncoso |
---|---|
Тема | Re: Parameter name standby_mode |
Дата | |
Msg-id | CAFsReFXq4zGj13ZEizbKK_SQS8m5oRf9j5df=DLpM5ZhoH-zWA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Parameter name standby_mode (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-hackers |
On Fri, 10 Oct 2025 at 18:30, Tom Lane <tgl@sss.pgh.pa.us> wrote: > > Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes: > > Joachim Wieland wrote: > >> If no primary_conninfo variable is set explicitly in the configuration > >> file, check the environment variables. If the environment variable is > >> not set, don't try to establish a connection. > > > The environment variables in question are the libpq environment > > variables like PGHOST, PGPORT. The server shouldn't need to know about > > them. > > Even more to the point is that some of them, like PGPORT, are highly > likely to be set in a server's environment to point to the server > itself. It would be extremely dangerous to automatically try to start > replication just because we find those set. In fact, I would argue that > we should fix things so that any such variables inherited from the > server environment are intentionally *NOT* used for making SR > connections. > I found this at https://wiki.postgresql.org/wiki/Todo#Standby_server_mode and I know it's been discussed *a long* time ago. I'm not sure if this is still required but at the moment, I'm having a look. Were you guys discussing if variables like PGHOST should be required in the connection string for the WAL receiver? > regards, tom lane > > -- https://www.linkedin.com/in/gonzalemario
В списке pgsql-hackers по дате отправления: