Joshua D. Drake wrote:
On Fri, 2010-02-12 at 10:22 -0800, Josh Berkus wrote:
In addition to the changes you've proposed, one thing our docs could
really use is a single reference page which we could go to for all of
the .conf files. Right now, you need to rely on postgresql.org doc
search in
On 2/13/10 10:17 AM, Greg Stark wrote:
But having the separate recovery.conf seems kind of pointless legacy
structure at this point.
Agreed, but I've been trying to minimize my tinkering with HS/SR.
Several things would need to be changed to get rid of Recovery.conf for
HS and PITR.
I expect
On fre, 2010-02-12 at 11:14 +0200, Heikki Linnakangas wrote:
So the new layout would be:
III. Server Administration
...
21. Managing Databases
22. Localization
23. Routine Database Maintenance Tasks
24. Backup and Restore
25. High Availability, Load Balancing,
On Fri, Feb 12, 2010 at 9:14 AM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
One glaring issue with the current documentation layout is that the
documentation for the various options in recovery.conf is split in two
places.
I've been trying to explain to someone how to set
One glaring issue with the current documentation layout is that the
documentation for the various options in recovery.conf is split in two
places. The old options, restore_command, recovery_target_* and so forth
are in section 24.3.3.1 Recovery Settings, while the new streaming
replication related
On Fri, Feb 12, 2010 at 6:14 PM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
So the new layout would be:
III. Server Administration
...
21. Managing Databases
22. Localization
23. Routine Database Maintenance Tasks
24. Backup and Restore
25. High
Fujii Masao wrote:
We might need to add the following code of pg_standby into the core,
to prefer it for many cases.
#ifdef WIN32
/*
* Windows 'cp' sets the final file size before the
copy is
* complete, and not yet ready
On Fri, Feb 12, 2010 at 7:15 PM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
That's actually a bit questionable, always has been even in pg_standby.
It adds a constant 1 s delay to the recovery each WAL file, which
effectively rate-limits the WAL recovery to 16MB per second. I
On 2/12/10 1:14 AM, Heikki Linnakangas wrote:
It's pretty clear that we should have a single place that documents all
the recovery.conf options. I suggest that we move the 24.3.3.1 Recovery
Settings section after High Availability, Load Balancing, and
Replication, and add the new streaming
Heikki,
Crossing this thread over to pgsql-docs, where I think it actually belongs.
In addition to the changes you've proposed, one thing our docs could
really use is a single reference page which we could go to for all of
the .conf files. Right now, you need to rely on postgresql.org doc
On Fri, 2010-02-12 at 10:22 -0800, Josh Berkus wrote:
Heikki,
Crossing this thread over to pgsql-docs, where I think it actually belongs.
In addition to the changes you've proposed, one thing our docs could
really use is a single reference page which we could go to for all of
the .conf
11 matches
Mail list logo
