Allow wal_keep_segments to keep all segments
in [PgSql]
|
Prev: [HACKERS] Allow wal_keep_segments to keep all segments
Next: recovery getting interrupted is not so unusual as it used to be
From: Alvaro Herrera on 3 Jun 2010 15:16 Excerpts from Bruce Momjian's message of jue jun 03 08:36:28 -0400 2010: > Using this only temporarily is mentioned in the doc patch. Do I need > more? Yeah, it's far too easy to miss. Besides, I think the wording you used is ambiguous -- it can be read as "the server will temporarily keep all segments if you set it to -1", which is not the same thing at all. If you can't add a 20-point-font red blinking warning with a pink dancing elephant in a tutu, maybe it's best to not offer the dangerous setting in the first place. -- Álvaro Herrera <alvherre(a)commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- 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: Bruce Momjian on 3 Jun 2010 15:35 Alvaro Herrera wrote: > Excerpts from Bruce Momjian's message of jue jun 03 08:36:28 -0400 2010: > > > Using this only temporarily is mentioned in the doc patch. Do I need > > more? > > Yeah, it's far too easy to miss. Besides, I think the wording you used > is ambiguous -- it can be read as "the server will temporarily keep all > segments if you set it to -1", which is not the same thing at all. If > you can't add a 20-point-font red blinking warning with a pink dancing > elephant in a tutu, maybe it's best to not offer the dangerous setting > in the first place. Well, it seems enough people don't want this features that I am not going to add it. If we decide we want it later, we can add it. -- Bruce Momjian <bruce(a)momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + None of us is going to be here forever. + -- 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: Andrew Dunstan on 3 Jun 2010 17:31
Heikki Linnakangas wrote: > > We leave that up to the DBA to clean out one way or another. We > provide restartpoint_command and the %r option in restore_command to > help with that. > > I was in fact just looking into this, and I see that there is no example restartpoint_comand script given in the docs, nor in the wiki. A sample of such a command would be useful. This is all going to feel a bit strange to lots of users, and the more we can hold their hands the better off we and they will be. cheers andrew -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers |