Re: [HACKERS] Re: [COMMITTERS] pgsql: Reduce the chatter to the log when starting a standby server.

2010-02-14 Thread Fujii Masao
On Sat, Feb 13, 2010 at 4:33 AM, Richard Huxton d...@archonet.com wrote: 2. Why have a finish.replication file, rather than SELECT pg_finish_replication()? I thought that the trigger file method was more easy-to-use for the existing users since it had been used in pg_standby for a long time so

Re: [HACKERS] Re: [COMMITTERS] pgsql: Reduce the chatter to the log when starting a standby server.

2010-02-14 Thread Heikki Linnakangas
Fujii Masao wrote: On Sat, Feb 13, 2010 at 4:33 AM, Richard Huxton d...@archonet.com wrote: 2. Why have a finish.replication file, rather than SELECT pg_finish_replication()? I thought that the trigger file method was more easy-to-use for the existing users since it had been used in

[HACKERS] Re: [COMMITTERS] pgsql: Reduce the chatter to the log when starting a standby server.

2010-02-12 Thread Simon Riggs
On Fri, 2010-02-12 at 09:49 +, Heikki Linnakangas wrote: Log Message: --- Reduce the chatter to the log when starting a standby server. Don't echo all the recovery.conf options. Don't emit the initializing recovery connections message, which doesn't mean anything to a user.

[HACKERS] Re: [COMMITTERS] pgsql: Reduce the chatter to the log when starting a standby server.

2010-02-12 Thread Heikki Linnakangas
Simon Riggs wrote: * entering standby mode isn't a more informative message. Two people have already said on-list that standby mode name might need to be changed. Well, I'm all ears for better suggestions. More informative, for me, would be something like entering streaming replication mode

Re: [HACKERS] Re: [COMMITTERS] pgsql: Reduce the chatter to the log when starting a standby server.

2010-02-12 Thread Robert Haas
On Fri, Feb 12, 2010 at 9:55 AM, Heikki Linnakangas heikki.linnakan...@enterprisedb.com wrote: That doesn't accurately describe what the standby_mode setting does. It doesn't imply streaming replication. It means that the server doesn't end recovery when it reaches end of WAL, but keeps trying.

Re: [HACKERS] Re: [COMMITTERS] pgsql: Reduce the chatter to the log when starting a standby server.

2010-02-12 Thread Heikki Linnakangas
Robert Haas wrote: Furthermore, if you're wanting to use pg_standby, you might be forgiven for thinking that you should set standby_mode = on; but in fact that's exactly the wrong thing to do. Yeah, I think that's the main weakness of the name standby_mode. It's pretty descriptive otherwise,

Re: [HACKERS] Re: [COMMITTERS] pgsql: Reduce the chatter to the log when starting a standby server.

2010-02-12 Thread Robert Haas
On Fri, Feb 12, 2010 at 10:27 AM, Heikki Linnakangas heikki.linnakan...@enterprisedb.com wrote: Robert Haas wrote: Furthermore, if you're wanting to use pg_standby, you might be forgiven for thinking that you should set standby_mode = on; but in fact that's exactly the wrong thing to do.

Re: [HACKERS] Re: [COMMITTERS] pgsql: Reduce the chatter to the log when starting a standby server.

2010-02-12 Thread Fujii Masao
On Sat, Feb 13, 2010 at 12:28 AM, Robert Haas robertmh...@gmail.com wrote: Well, let's come up with something else then. continuous_recovery ? Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center -- Sent via pgsql-hackers mailing list

Re: [HACKERS] Re: [COMMITTERS] pgsql: Reduce the chatter to the log when starting a standby server.

2010-02-12 Thread Richard Huxton
On 12/02/10 15:37, Fujii Masao wrote: On Sat, Feb 13, 2010 at 12:28 AM, Robert Haasrobertmh...@gmail.com wrote: Well, let's come up with something else then. continuous_recovery ? One problem with the otherwise entirely wonderful HS/SR pairing is the whole business of the config

Re: [HACKERS] Re: [COMMITTERS] pgsql: Reduce the chatter to the log when starting a standby server.

2010-02-12 Thread Dimitri Fontaine
Heikki Linnakangas heikki.linnakan...@enterprisedb.com writes: Robert Haas wrote: Furthermore, if you're wanting to use pg_standby, you might be forgiven for thinking that you should set standby_mode = on; but in fact that's exactly the wrong thing to do. Yeah, I think that's the main