Re: Reading recovery.conf earlier - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: Reading recovery.conf earlier
Date
Msg-id 4B1CB920.6030807@enterprisedb.com
Whole thread Raw
In response to Re: Reading recovery.conf earlier  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Reading recovery.conf earlier  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
Simon Riggs wrote:
> What postgresql.conf already does is read file separately in each
> process, so no data passing.

No it doesn't. Postmaster reads the file once, and backends inherit the
values at fork(). In EXEC_BACKEND case, postmaster writes all the
non-default values to a separate file, which the child process reads at
startup.

Reading the file separately in each process would cause trouble with
PGC_POSTMASTER params. All backends must agree on their values.

--  Heikki Linnakangas EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Hot standby, recent changes
Next
From: Hitoshi Harada
Date:
Subject: Re: YAML Was: CommitFest status/management