On Thu, Dec 17, 2009 at 9:02 PM, Heikki Linnakangas <heikki.linnakan...@enterprisedb.com> wrote: >> And, I think that such backend should switch to walsender mode when the >> startup >> packet arrives. Otherwise, we would have to authenticate such backend twice >> on different context, i.e., a normal backend and walsender. So the settings >> for >> each context would be required in pg_hba.conf. This is odd, I think. Thought? > > True.
Currently this switch depends on whether XLOG_STREAMING_CODE is sent from the standby or not, also which depends on whether PQstartXLogStreaming() is called or not. But, as the next step, we should get rid of also such changes of libpq. I'm thinking of making the standby send the "walsender-switch-code" the same way as application_name; walreceiver always specifies the option like "replication=on" in conninfo string and calls PQconnectdb(), which sends the code as a part of startup packet. And, the environment variable for that should not be defined to avoid user's mis-configuration, I think. Thought? Better idea? Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
