recovery_connections cannot start
in [PgSql]
|
From: Dimitri Fontaine on 27 Apr 2010 09:10 Robert Haas <robertmhaas(a)gmail.com> writes: > Treating the string "true" as a special case seems like a kludge to > me. Maybe a robust set of internal commands wouldn't be a kludge, but > that's not what's being proposed here. I guess it's just a matter of > opinion. I don't see how to have internal commands without having special cases for the setting, and I did propose "pg_archive_bypass" as the name. I guess the implementation would be what Simon was talking about, though. I don't see "true" as meaningful in the context of an archive_command⦠Regards, -- dim -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Simon Riggs on 27 Apr 2010 09:20 On Tue, 2010-04-27 at 15:10 +0200, Dimitri Fontaine wrote: > Robert Haas <robertmhaas(a)gmail.com> writes: > > Treating the string "true" as a special case seems like a kludge to > > me. Maybe a robust set of internal commands wouldn't be a kludge, but > > that's not what's being proposed here. I guess it's just a matter of > > opinion. > > I don't see how to have internal commands without having special cases > for the setting, and I did propose "pg_archive_bypass" as the name. I > guess the implementation would be what Simon was talking about, though. > > I don't see "true" as meaningful in the context of an archive_command… Saying "its a kludge" doesn't really address the issue and goes nowhere towards fixing it. If we don't like the proposal, fine, then what is the alternative solution? -- Simon Riggs www.2ndQuadrant.com -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Robert Haas on 27 Apr 2010 10:52 On Apr 27, 2010, at 9:20 AM, Simon Riggs <simon(a)2ndQuadrant.com> wrote: > On Tue, 2010-04-27 at 15:10 +0200, Dimitri Fontaine wrote: >> Robert Haas <robertmhaas(a)gmail.com> writes: >>> Treating the string "true" as a special case seems like a kludge to >>> me. Maybe a robust set of internal commands wouldn't be a kludge, >>> but >>> that's not what's being proposed here. I guess it's just a matter >>> of >>> opinion. >> >> I don't see how to have internal commands without having special >> cases >> for the setting, and I did propose "pg_archive_bypass" as the name. I >> guess the implementation would be what Simon was talking about, >> though. >> >> I don't see "true" as meaningful in the context of an >> archive_command > > Saying "its a kludge" doesn't really address the issue and goes > nowhere > towards fixing it. If we don't like the proposal, fine, then what is > the > alternative solution? I proposed one upthread. ....Robert -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
First
|
Prev
|
Pages: 1 2 Prev: standbycheck was:(Re: [HACKERS] testing hot standby Next: CIText and pattern_ops |