Hi,
I set up an warm standby server which fetches WAL logs from a remote
server. It has been working very well. But today, I was editing the
restore script(which is set as the restore_command) with vi. Just right
after I saved the script, I noticed suddenly the standby server
terminated. I
Rural Hunter ruralhun...@gmail.com wrote:
I set up an warm standby server which fetches WAL logs from a
remote server. It has been working very well. But today, I was
editing the restore script(which is set as the restore_command)
with vi. Just right after I saved the script, I noticed
Got it. thanks.
于2011年9月21日 1:31:09,Kevin Grittner写到:
Rural Hunterruralhun...@gmail.com wrote:
I set up an warm standby server which fetches WAL logs from a
remote server. It has been working very well. But today, I was
editing the restore script(which is set as the restore_command)
with vi.
Hello everybody,
am new to postgre, and I hope I finde som help in this mailing list.
I have created a warm standby successfully, everything work fine also the
applying of the archive from primary, my problem is that the Service under
windows 2008r2 doesn't start if the standby is running (I
On Tue, 2011-09-06 at 14:12 +0200, Al-Salami, Adel wrote:
I have created a warm standby successfully, everything work fine also
the applying of the archive from primary, my problem is that the
Service under windows 2008r2 doesn't start if the standby is running
(I get a start service timeout).
Thanks alot.
-Ursprüngliche Nachricht-
Von: pgsql-admin-ow...@postgresql.org [mailto:pgsql-admin-ow...@postgresql.org]
Im Auftrag von Devrim GÜNDÜZ
Gesendet: Dienstag, 6. September 2011 14:40
An: Al-Salami, Adel
Cc: pgsql-admin@postgresql.org
Betreff: Re: [ADMIN] Warm standby Service
Alanoly Andrews alano...@invera.com writes:
Hello,
Is it possible to set up a warm standby pair of postgres instances
without using the pg_standby utility? The PG manuals appear to say it
is possible. But I dont see the details of how to set this up. How
do you keep the standby instance in
On Thu, Apr 14, 2011 at 1:06 PM, Alanoly Andrews alano...@invera.com wrote:
Thanks, Simon, for your quick response. I'll try it out with your pg_standby
utility. And...if I may ask you one more question on the subject, once the
standby is up and running, is there a way to determine whether
Hello,
Is it possible to set up a warm standby pair of postgres instances without
using the pg_standby utility? The PG manuals appear to say it is possible. But
I don't see the details of how to set this up. How do you keep the standby
instance in permanent recovery mode?
Thanks.
Alanoly.
On Wed, Apr 13, 2011 at 8:53 PM, Alanoly Andrews alano...@invera.com wrote:
Is it possible to set up a warm standby pair of postgres instances without
using the pg_standby utility? The PG manuals appear to say it is possible.
But I don’t see the details of how to set this up. How do you keep
Kevin Grittner kevin.gritt...@wicourts.gov writes:
that script to not delete. Personally, I like to keep the last two
base backups and all the WAL files needed to restore from the
earlier of those forward. We have cleanup script that deletes the
oldest backup and WAL files only needed for
Dimitri Fontaine dimi...@2ndquadrant.fr wrote:
Kevin Grittner kevin.gritt...@wicourts.gov writes:
that script to not delete. Personally, I like to keep the last
two base backups and all the WAL files needed to restore from the
earlier of those forward. We have cleanup script that deletes
Kevin Grittner kevin.gritt...@wicourts.gov writes:
I don't suppose there's something which looks *into* a backup file
and deletes all WAL files not needed to restore the related base
backup? That would eliminate an even *uglier* bash script here.
Well with some luck Magnus will be able to
Hello all,
We have a two Postgres servers running 8.3 set up for warm standby using xlog
shipping. We had some problems with our warm standby locking up and needing to
be rebooted and have grub reinstalled for the system to boot. Once the server
was back up we noticed the xlog file it was
Colin Wilson cwil...@blackducksoftware.com wrote:
Once the server was back up we noticed the xlog file it was
looking for was one that the logs say was already applied. It
was 7 xlogs back to be exact.
It is not unusual for WAL replay to ask for files out of order or
multiple times in
Of Kevin Grittner
Sent: 24 January 2011 17:03
To: Colin Wilson; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Warm Standby looking for already applied log files
Colin Wilson cwil...@blackducksoftware.com wrote:
Once the server was back up we noticed the xlog file it was
looking for was one
Hi again,
After copying a new dump of the MASTER cluster data and starting the SLAVE with
this data, I now get:
Database cluster state: in production
..
Minimum recovery ending location: 0/0
Still not exactly as expected, I guess. The log says things like :
cp: cannot stat
On Fri, Apr 09, 2010 at 10:19:20AM +0200, Dennis Thrys?e wrote:
cp: cannot stat `/psql_archive/0001.history': No such file or directory
By the way, one of these lines each second!
2010-04-09 09:09:49 IST FATAL: the database system is starting up
I asked about this a few weeks ago and
Dennis Thrysøed...@geysirit.dk wrote:
After copying a new dump of the MASTER cluster data and starting
the SLAVE with this data, I now get:
Database cluster state: in production
..
Minimum recovery ending location: 0/0
Somehow it completed archive recovery and switched
Hi,
I have a few elaborating questions in regard to setting up Warm Standby.
1) The master keeps writing WAL files even though I'm quite sure nothing is
happening. This seems like a large waste of diskspace?
2) Sometimes my slave does not read and delete WAL files when in recovery mode.
This
Dennis Thrysøed...@geysirit.dk wrote:
1) The master keeps writing WAL files even though I'm quite sure
nothing is happening. This seems like a large waste of diskspace?
What is your setting for archive_timeout? This limits how long
before a WAL file is sent. You could extend the time,
Hi,
Back in October 2009, I reported on strange warm-standby problems in
this thread: http://archives.postgresql.org/pgsql-admin/2009-10/msg00170.php
Just in case anyone still cares or is wondering, we found the problem.
The machine had bad RAM; we were getting undetected/uncorrected single-bit
On Wed, Jan 20, 2010 at 10:10:26AM -0500, David F. Skoll wrote:
The machine had bad RAM; we were getting undetected/uncorrected single-bit
errors creeping through!
who's the machine/memory vendor?
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your
Ray Stell wrote:
The machine had bad RAM; we were getting undetected/uncorrected single-bit
errors creeping through!
who's the machine/memory vendor?
I don't know exactly; it's a colocated machine that we don't own.
dmidecode (trimmed down) says:
System Information
Manufacturer:
Hello -
I am working on setting up warm standby for one of my servers and I am a
little confused about the documentation. I am using pg_standby on
postgres 8.4.1 running on linux.
My recovery.conf is very basic:
restore_command = 'pg_standby /shared_pitr %f %p %r'
On the secondary, I can see two
Tom Lane wrote:
What about the other direction: the script invoked by the archive
returns done before the bits have all been shipped?
Do you mean the wal_archive_command? It waits for scp to finish.
It's written in Perl; here is the relevant part.
Regards,
David.
[Stuff deleted...]
my
Hi,
In an effort to track down the problem, I switched to using rsync rather
than scp to copy the files. I also take the SHA1 hash on each end, and
have my archiving script exit with a non-zero status if there's a mismatch.
Sure enough:
Oct 27 14:26:35 colo2vs1
David F. Skoll d...@roaringpenguin.com wrote:
(My script exits with non-zero status if the SHA1s mismatch, and
PostgreSQL re-archives the WAL a short time later, and that
succeeds, so I'm happy for now.)
Just out of curiosity, could you show us the non-comment portions of
your
Kevin Grittner wrote:
Just out of curiosity, could you show us the non-comment portions of
your postgresql.conf file?
Sure! Here they are.
Regards,
David.
=
data_directory = '/var/lib/postgresql/8.3/main'
hba_file
David F. Skoll d...@roaringpenguin.com writes:
Sure enough:
Oct 27 14:26:35 colo2vs1 canit-failover-wal-archive[29118]:
Warning: rsync succeeded, but local_sha1
1fe9fc62b2a05d21530decac1c5442969adc5819
!= remote_sha1 4f9f8bcd151129db64acd05470f0f05954b56232 !!
This is a can't happen
Tom Lane wrote:
So, when it archives successfully the second time, which if either of
the two mismatched sha1's proves to have been correct?
The one on the master server (lines wrapped for readability).
local refers to the master server, and remote to the standby
server.
Oct 27 14:26:35
David F. Skoll d...@roaringpenguin.com wrote:
shared_buffers = 24MB
You should probably set that higher. Different workloads favor
different settings, but if you've got any reasonable amount of RAM for
a modern machine, somewhere between 256MB and one-third of total RAM
is usually best.
Kevin Grittner wrote:
shared_buffers = 24MB
You should probably set that higher.
Nah. This machine is totally bored; tweaking PostgreSQL would be pointless
since it's so under-utilized.
archive_command = '/usr/bin/wal_archive_command.pl %p'
It would probably be safer to pass in %f, too,
David F. Skoll d...@roaringpenguin.com writes:
Tom Lane wrote:
So, when it archives successfully the second time, which if either of
the two mismatched sha1's proves to have been correct?
The one on the master server (lines wrapped for readability).
However, the sha1 is taken after rsync
Hi,
I have one PostgreSQL 8.3 machine feeding WAL files to another PostgreSQL 8.3
machine that's running in recovery mode. However, fairly often (every
few days), the standby machine breaks out of recovery mode with log messages
like:
2009-10-23 21:47:40 EDT LOG: incorrect resource manager
David F. Skoll d...@roaringpenguin.com writes:
I have one PostgreSQL 8.3 machine feeding WAL files to another PostgreSQL 8.3
machine that's running in recovery mode. However, fairly often (every
few days), the standby machine breaks out of recovery mode with log messages
like:
2009-10-23
Tom Lane wrote:
No; there's no WAL change between 8.3.7 and 8.3.8. What seems more
likely is that you're somehow shipping the WAL files before they're
quite finished.
I doubt it. Our archive_command works like this:
1) scp the file over to the backup server as root. It's stored in a
file
David F. Skoll d...@roaringpenguin.com writes:
Tom Lane wrote:
No; there's no WAL change between 8.3.7 and 8.3.8. What seems more
likely is that you're somehow shipping the WAL files before they're
quite finished.
So unless there's a possibility that the master server invokes our archive
Hi,
I'm running PostgreSQL 8.3. Suppose I have master server A shipping logs
to backup server B. At some time in the past, I did a full backup from A
to B, and now B is running in recovery mode, happily consuming WALs.
Q1. If I stop and restart master server A gracefully, do I need to do
On Oct 13, 2009, at 1:17 PM, David F. Skoll wrote:
Hi,
I'm running PostgreSQL 8.3. Suppose I have master server A shipping
logs
to backup server B. At some time in the past, I did a full backup
from A
to B, and now B is running in recovery mode, happily consuming WALs.
I'm running 8.4,
On Tue, 2009-10-13 at 13:17 -0400, David F. Skoll wrote:
Q2. If I stop and restart backup server B while master server A continues
to run, will B continue eating WALs from where it left off? Or do we need
another full backup? (We'll assume WAL shipping continues successfully during
the
, October 13, 2009 12:45 PM
To: David F. Skoll
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Warm standby questions
On Oct 13, 2009, at 1:17 PM, David F. Skoll wrote:
Hi,
I'm running PostgreSQL 8.3. Suppose I have master server A shipping
logs
to backup server B. At some time in the past, I did
Insufficient coffee:
My environment is a little strange (at least I never read about one
set up like this before I built it) and has some associated oddities
in the old segment cleanup process - All of my slaves mount an
archive partition on the master (read-only) and every log file is
On Fri, Aug 21, 2009 at 10:46 AM, james bardinjbar...@bu.edu wrote:
The first move runs easily as expected- postgres ships the last
partial wal immediately on shutdown, trigger the standby and we're up.
I'm now running into issues bringing the first server back up in
standby mode. After the
Hello,
I have a working warm standby system, running 8.4 (thanks for urging
me to upgrade from the rehdat provided release).
One of the new requirements is going to be for (a non-DBA) admin to
easily swap services between the two servers for maintenance.
The first move runs easily as expected-
Hello,
I'm working on a warm standby system, and we would like to stick with
the RHEL5 distributed version of postgres, which is still 8.1.
I can setup the system to a point where it's adequate for disaster
recovery, but I'm not comfortable keeping the systems in sync for
failover, maintenance,
James,
You really, really, really should upgrade to a more recent
release. The list of improvements and bugfixes is long and
well worth having. 8.1 was released 4 years ago. If you
cannot, please, please make certain that you are running
the latest point release -- regardless of what is shipping
Thanks Ken. The more I think about it, the more I feel we should move
away from upstream, and pull the latest version for this.
So on with newer versions -
When using the built-in systems for warm standby, how do I ensure that
the latest transactions have been archived? Does a clean shutdown
On Tue, Aug 18, 2009 at 12:09:25PM -0400, james bardin wrote:
Thanks Ken. The more I think about it, the more I feel we should move
away from upstream, and pull the latest version for this.
So on with newer versions -
When using the built-in systems for warm standby, how do I ensure that
does a file named 000100CD exist anywhere on your disk?
-lee
On Fri, Feb 27, 2009 at 2:47 AM, Brad Wiemerslage wieme...@yahoo.com wrote:
I'm attempting to get warm standby up and running with a pair of servers
running ubuntu 8.04 and postgresql 8.3. Been following the docs:
I'm attempting to get warm standby up and running with a pair of servers
running ubuntu 8.04 and postgresql 8.3. Been following the docs:
http://www.postgresql.org/docs/8.3/static/warm-standby.html
http://www.postgresql.org/docs/current/static/pgstandby.html
Also, basically following the
thank you all for your help. It was indeed my copy script that
destroyed the database. I now understand that postgresql shouldn't be
concerned with validating a WAL segment, that's the responsibility of
the script that hands the segment to postgres.
-lee
On Fri, Jan 30, 2009 at 9:52 AM, Tom Lane
On Fri, Jan 30, 2009 at 7:52 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Jaume Sabater jsaba...@gmail.com writes:
On Fri, Jan 30, 2009 at 2:22 AM, Tom Lane t...@sss.pgh.pa.us wrote:
We probably should add a caution about this to the manual's discussion
of how to write archiving scripts.
I presume
On Fri, Jan 30, 2009 at 2:22 AM, Tom Lane t...@sss.pgh.pa.us wrote:
We probably should add a caution about this to the manual's discussion
of how to write archiving scripts.
I presume you mean the copy/transfer process did not do its job
correctly, Tom. Therefore, I would advise using a script
I'm new to the list. So hello everyone. This morning my monitoring
system sent me an alert that my warm standby database had exited
recovery mode. I checked on it when I woke up and sure enough, it had
stopped looking for new WAL files and became available for queries.
After some digging, I
Lee Azzarello l...@dropio.com writes:
cp: writing `pg_xlog/./0001002F00AA': No space left on device
2009-01-29 12:48:14 UTC LOG: could not read from log file 47, segment
170, offset 3129344: Success
2009-01-29 12:48:14 UTC LOG: redo done at 2F/AA2FBE08
The bottom line here seems
What I'm hearing is that I have to perform a base backup on my master in
Mass. after recovery completes, send that over a secure network
To Virginia, and lay it down there. Simple enough but the time to travel
Over the network becomes an issue - 12 - 13 hours at best.
If we have to do this then
On Fri, 2008-12-19 at 09:14 -0500, Mark Steben wrote:
What I'm hearing is that I have to perform a base backup on my master in
Mass. after recovery completes, send that over a secure network
To Virginia, and lay it down there. Simple enough but the time to travel
Over the network becomes an
On Thu, 2008-12-18 at 16:43 -0500, Mark Steben wrote:
3. I am currently in a state where a log got partially copied and
postgres
cannot find a valid checkpoint to restart. What is the best way to
remedy
this situation? Pg_resetxlog perhaps?
Now, pg_resetxlogs, but in future don't delete
On Fri, 2008-12-19 at 08:51 -0800, Joshua D. Drake wrote:
On Fri, 2008-12-19 at 09:14 -0500, Mark Steben wrote:
What I'm hearing is that I have to perform a base backup on my master in
Mass. after recovery completes, send that over a secure network
To Virginia, and lay it down there.
Mark Steben mste...@autorevenue.com wrote:
What I'm hearing is that I have to perform a base backup on my master
in
Mass. after recovery completes, send that over a secure network
To Virginia, and lay it down there.
I'm not sure we're understanding each other. I was suggesting that
you
Thanks for the clarifications Kevin, Josh, Simon
I am trying out Kevin's suggestion to create a second standby copy now.
I know I have to create the base copy and send it over, at least
For the first time to start recovery. I will look at rsync to do that.
Thanks for all the help -- Mark
I'm
Mark Steben mste...@autorevenue.com wrote:
We are at postgresql 8.2.5
You really should update to 8.2.11 or consider going to 8.3.5.
http://www.postgresql.org/support/versioning
We plan on using the Norfolk server not so much as a recovery
failover but
as a replicated database
To run
On Thu, 2008-12-18 at 16:43 -0500, Mark Steben wrote:
Hi folks,
recovery mode, letting the updates catch up for the
next days processing.
My questions are:
1. Is this a proper usage of log shipping?
Sure but you will have to run a base backup every night. You can't exit
recovery, run
Hi,
I am using pg 8.3 and configured warm standby server. It is working
well, but my db is relative big ( ~ 40 GB).
Is it possible to stop running ?Warm standby server and? when it
starts again to continue executing WALs from the stop moment.
I'm using following command to stop the
On Wed, 2008-12-10 at 14:23 +0200, [EMAIL PROTECTED] wrote:
Hi,
I am using pg 8.3 and configured warm standby server. It is working
well, but my db is relative big ( ~ 40 GB).
Is it possible to stop running Warm standby server and when it
starts again to continue executing WALs from
I'm attempting a warm standby setup. I'm running Postgres 8.3 on both
master and slave.
Unfortunately the master is a 32 bit machine and the slave is a 64 bit
machine. Both running
Linux Redhat. After I bring in the master base file copy into the slave and
attempt to
Start postgres I get an
Mark Steben [EMAIL PROTECTED] writes:
I'm attempting a warm standby setup. I'm running Postgres 8.3 on both
master and slave.
Unfortunately the master is a 32 bit machine and the slave is a 64 bit
machine.
You do need the same architecture on both ends. You might be able to
run a 32-bit
Scott Montaseri,
Montaseri wrote:
While I am not an expert on WAL, but again I question the merits of
such sophisticated HA configuration. Of course there are use cases for
such configs, but I am only advocating best price performance kind of
mentality
As WAL writes the journals all the
I've got 3 different database servers (db01, db02 and db03).
I would like to have a WAL standby server that replays logs for all 3 in
case one goes down, so I can promote that particular server.
Can I do this by installing 3 separate postmasters on this machine?
Obviously, if 2 went down at the
On Thu, 2008-06-26 at 10:19 -0500, Scott Whitney wrote:
I've got 3 different database servers (db01, db02 and db03).
I would like to have a WAL standby server that replays logs for all 3 in
case one goes down, so I can promote that particular server.
Can I do this by installing 3 separate
I am not so sure of this arrangement's mertis
From HA (High Availability) point of view, the host/server is a single point
of failure which will bring your entire infrastructure down if any of the
server hardware components fail.
From Performance point of view, you have increased the load on
(at my office)?
Assume no auto-failover.
-Original Message-
From: Montaseri [mailto:[EMAIL PROTECTED]
Sent: Jun 26, 2008 12:51 PM
To: Simon Riggs
Cc: Scott Whitney; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Warm standby server
I am not so sure of this arrangement's mertis
From HA (High
duplicating to standby1 (at my coloc), and standby2 (at my office)?
Assume no auto-failover.
-Original Message-
From: Montaseri [mailto:[EMAIL PROTECTED]
Sent: Jun 26, 2008 12:51 PM
To: Simon Riggs
Cc: Scott Whitney; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Warm standby
PM
To: Scott Whitney
Cc: Simon Riggs; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Warm standby server
While I am not an expert on WAL, but again I question the merits of such
sophisticated HA configuration. Of course there are use cases for such
configs, but I am only advocating best price
On Thu, 2008-06-26 at 13:01 -0500, Scott Whitney wrote:
A 2nd question: Is it possible to have 2 standby servers with a single
master duplicating to standby1 (at my coloc), and standby2 (at my office)?
Assume no auto-failover.
Yes, that works too.
--
Simon Riggs
On Thu, 2008-06-19 at 19:31 -0400, Bhella Paramjeet-PFCW67 wrote:
We have created a postgres database with a warm-standby in postgres 8.2
following the document on the archive by Charles Duffy.
Please can you read the main docs? The above document is out of date.
If there is something not
On Thu, Jun 19, 2008 at 6:31 PM, in message
[EMAIL PROTECTED],
Bhella
Paramjeet-PFCW67 [EMAIL PROTECTED] wrote:
we need to monitor the standby database to
check that it is up, it is getting synced every 10 minutes, and that
it
is not out of sync with primary database. What would be the
Hi,
We have created a postgres database with a warm-standby in postgres 8.2
following the document on the archive by Charles Duffy. The standby
database is in continuous recovery mode and archived logs are synced to
the standby from primary, every 10 minutes. The primary and the standby
database
On Thu, 2008-06-19 at 19:31 -0400, Bhella Paramjeet-PFCW67 wrote:
Hi,
We have created a postgres database with a warm-standby in postgres 8.2
following the document on the archive by Charles Duffy. The standby
database is in continuous recovery mode and archived logs are synced to
the
I have setup this feature using postgresql 8.3.1 on a suse linux version
and pg_standby as a recovery script, works very good and I use rsync as a
script to ship logs
This is my configuration in the primary D.B
archive_mode = on
archive_command = 'rsync -atz %p
Hi List;
I'm setting up a warm standby server on version 8.1.9
I setup a recovery.sh script to keep the standby cluster in recovery
mode waiting for the next WAL segment. everything works fine as long
as the standby server is in recovery mode. I see the recovery taking
place in the
Hi Kevin,
On Mon, Apr 28, 2008 at 7:34 AM, kevin kempter
[EMAIL PROTECTED] wrote:
Hi List;
I'm setting up a warm standby server on version 8.1.9
I didn't think 8.1 supported warm-standby...
I setup a recovery.sh script to keep the standby cluster in recovery mode
waiting for the next
On Tue, Dec 18, 2007 at 12:55 PM, in message [EMAIL PROTECTED],
Tom Lane [EMAIL PROTECTED] wrote:
David F. Skoll [EMAIL PROTECTED] writes:
My question is this: If the master database is fairly busy, gets
VACUUMed once a day, etc. can we expect the warm standby server
to work correctly after
Kevin Grittner wrote:
On Tue, Dec 18, 2007 at 12:55 PM, in message [EMAIL PROTECTED],
Tom Lane [EMAIL PROTECTED] wrote:
David F. Skoll [EMAIL PROTECTED] writes:
My question is this: If the master database is fairly busy, gets
VACUUMed once a day, etc. can we expect the warm standby
Hi,
We have two PostgreSQL 8.2 database servers: A master and a warm-standby
server. We plan on making an initial backup of the master onto the standby
and then use log-shipping with real-time WAL-file processing as described
in http://www.postgresql.org/docs/8.2/static/warm-standby.html
My
David F. Skoll [EMAIL PROTECTED] writes:
My question is this: If the master database is fairly busy, gets
VACUUMed once a day, etc. can we expect the warm standby server
to work correctly after days/weeks/months/years of log shipping,
or should we periodically take new base backups?
I don't
Hi there,
A bit of background information:
I am running Postgres 8.2.4 on Solaris 10 in a warm standby configuration.
My archive command scp's WAL logs from the live server to the standby
server. The standby server runs in a recovery mode waiting for the WAL logs
and processing them as they
Hi All,
I was wondering if anyone has had success implementing a warm spare
database using WAL archiving on a v8.0.4 database. I know the
documentation that states warm spare was in 8.2.4 manual but having read
and re-read it, it should work as it is not using any v8.2-specific
feature to
Ali, Luqman [EMAIL PROTECTED] writes:
I was wondering if anyone has had success implementing a warm spare
database using WAL archiving on a v8.0.4 database. I know the
documentation that states warm spare was in 8.2.4 manual but having read
and re-read it, it should work as it is not using any
On Tue, Feb 27, 2007 at 10:34:37AM +0200, Johann Spies wrote:
I want to setup a form of replication for postgresql using the warm
standby option
(http://www.postgresql.org/docs/8.2/static/warm-standby.html)
I have had success to let server A to copy the WAL logs to server B (the
standby
I want to setup a form of replication for postgresql using the warm
standby option
(http://www.postgresql.org/docs/8.2/static/warm-standby.html)
I have had success to let server A to copy the WAL logs to server B (the
standby server). But I have had no success on the recovery side of
things. I
92 matches
Mail list logo
