Added to TODO:
Allow archive_mode to be changed without server restart?
* http://archives.postgresql.org/pgsql-hackers/2008-10/msg01655.php
---
Simon Riggs wrote:
Currently we enable archive_mode
On Wed, 12 Nov 2008, Jonah H. Harris wrote:
In a large-scale OLTP environment, uptime is paramount, and having to
restart the database to enable PITR is a big PITA.
What I did last time I was stuck with this problem was make the
archive_command point to a script I could toggle on and off
Anyway, I think this is worth fixing before release but it clearly isn't
worth attempting to rush a patch in the next few hours. I don't think
we'll find anyone who is happy with making it a restart-required option.
I couldn't find a patch/commit for this and was just wondering whether
someone
On Wed, 2008-11-12 at 10:48 -0500, Jonah H. Harris wrote:
Anyway, I think this is worth fixing before release but it clearly isn't
worth attempting to rush a patch in the next few hours. I don't think
we'll find anyone who is happy with making it a restart-required option.
I couldn't
Currently we enable archive_mode only at server start. The reason for
this was to protect against people enabling archive_mode half way
through somebody else running a bulk load without WAL and then having an
incomplete backup.
All we need to do is this:
* When we change archive_mode to on get
Simon Riggs [EMAIL PROTECTED] wrote:
Currently we enable archive_mode only at server start. The reason
for
this was to protect against people enabling archive_mode half way
through somebody else running a bulk load without WAL and then having
an
incomplete backup.
All we need to do is
Simon Riggs [EMAIL PROTECTED] writes:
Objections?
Why is this worth spending effort on? I doubt that your sketch is
correct/complete anyway (you at least neglected to describe starting
and stopping the archiver, as well as how it knows where to start
archiving).
Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
Objections?
Why is this worth spending effort on?
The addition of archive_mode changeable with restart only was a
significant loss of usability going from 8.2 to 8.3, in the minds of
many people.
--
Sent via pgsql-hackers mailing
Peter Eisentraut wrote:
Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
Objections?
Why is this worth spending effort on?
The addition of archive_mode changeable with restart only was a
significant loss of usability going from 8.2 to 8.3, in the minds of
many people.
It certainly
Joshua D. Drake [EMAIL PROTECTED] wrote:
It certainly makes more sense to do this:
archive_mode = on
pg_ctl reload
archive_mode = off
pg_ctl reload
versus
archive_command = '/path/to/really/long/archive/string'
pg_ctl reload
archive_command = '/bin/true'
pg_ctl reload
Kevin Grittner wrote:
Joshua D. Drake [EMAIL PROTECTED] wrote:
It certainly makes more sense to do this:
archive_mode = off
archive_command = '/archive/command/used/during/snapshot/backups'
I could live with diddling the command to control archiving.
It doesn't log anything extra when
Joshua D. Drake wrote:
Kevin Grittner wrote:
Joshua D. Drake [EMAIL PROTECTED] wrote:
It certainly makes more sense to do this:
archive_mode = off
archive_command = '/archive/command/used/during/snapshot/backups'
I could live with diddling the command to control archiving.
It doesn't
Joshua D. Drake [EMAIL PROTECTED] wrote:
Kevin Grittner wrote:
It doesn't log anything extra when archive_mode is on?
Depends on your logging level.
I guess my question wasn't clear -- I meant into the Write-Ahead Log
(WAL) files.
-Kevin
--
Sent via pgsql-hackers mailing list
Heikki Linnakangas [EMAIL PROTECTED] writes:
archive_mode = on disables the optimization to skip WAL-logging when
loading into a new table that was created in the same transaction.
... and affects a whole bunch of other behaviors too, in processes all
across the database that could not
On Fri, 2008-10-31 at 17:38 +0200, Peter Eisentraut wrote:
Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
Objections?
Why is this worth spending effort on?
The addition of archive_mode changeable with restart only was a
significant loss of usability going from 8.2 to 8.3, in
Brad Nicholson [EMAIL PROTECTED] wrote:
On Fri, 2008-10-31 at 17:38 +0200, Peter Eisentraut wrote:
Tom Lane wrote:
Why is this worth spending effort on?
The addition of archive_mode changeable with restart only was a
significant loss of usability going from 8.2 to 8.3, in the minds of
On Fri, 2008-10-31 at 13:14 -0400, Tom Lane wrote:
Heikki Linnakangas [EMAIL PROTECTED] writes:
archive_mode = on disables the optimization to skip WAL-logging when
loading into a new table that was created in the same transaction.
... and affects a whole bunch of other behaviors too,
17 matches
Mail list logo
