Thank You, I will have a look.
-Original Message-
From: Adrian Klaver [mailto:adrian.kla...@aklaver.com]
Sent: Tuesday, June 10, 2014 3:45 PM
To: Khangelani Gama; pgsql-general@postgresql.org
Subject: Re: [GENERAL] pg_standby replication problem
On 06/09/2014 10:02 PM, Khangelani Gama
On 06/09/2014 10:02 PM, Khangelani Gama wrote:
-Original Message-
From: Adrian Klaver [mailto:adrian.kla...@aklaver.com]
Sent: Tuesday, June 10, 2014 1:42 AM
To: Khangelani Gama; pgsql-general@postgresql.org
Subject: Re: [GENERAL] pg_standby replication problem
On 06/09/2014 11:15 AM
-Original Message-
From: Adrian Klaver [mailto:adrian.kla...@aklaver.com]
Sent: Tuesday, June 10, 2014 1:42 AM
To: Khangelani Gama; pgsql-general@postgresql.org
Subject: Re: [GENERAL] pg_standby replication problem
On 06/09/2014 11:15 AM, Khangelani Gama wrote:
> This is the stan
On 06/09/2014 11:15 AM, Khangelani Gama wrote:
This is the standby replication setting with archive_command sending the
WALs from master to standby.
What are the conf settings on the standby server?
--
Adrian Klaver
adrian.kla...@aklaver.com
--
Sent via pgsql-general mailing list (pgsql-g
On Monday, June 09, 2014 08:05:41 PM Khangelani Gama wrote:
> Hi All
>
> I would like to re-post the problem we have. The secondary server ran out
> the disc space due the replication problem (Connection Time out).
The secondary server would not (could not) run out of drive space due to a
proble
This is the standby replication setting with archive_command sending the
WALs from master to standby.
-Original Message-
From: Khangelani Gama [mailto:kg...@argility.com]
Sent: Monday, June 09, 2014 8:06 PM
To: pgsql-general@postgresql.org
Subject: pg_standby replication problem
Hi All
Hi All
I would like to re-post the problem we have. The secondary server ran out
the disc space due the replication problem (Connection Time out).Since there
was a Connection time out Problem in the primary server, how can I make disc
space in the secondary server for the replication to continue f
-Original Message-
From: Khangelani Gama [mailto:kg...@argility.com]
Sent: Monday, June 09, 2014 5:26 PM
To: 'Alan Hodgson'; 'pgsql-general@postgresql.org'
Subject: RE: [GENERAL] pg_standby replication problem
I just saw got this from the primary server (/tmp/ru
I just saw got this from the primary server (/tmp/run_replication.sh.out),
secondary server's IP 10.58.101.10.
replication started: Sun Jun 8 00:05:26 SAST 2014 source:
pg_xlog/00054BAF00AF, dest: 00054BAF00AF
replication finished: Sun Jun 8 00:05:33 SAST 2014
replicati
-Original Message-
From: pgsql-general-ow...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] On Behalf Of Alan Hodgson
Sent: Monday, June 09, 2014 4:51 PM
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] pg_standby replication problem
On Monday, June 09, 2014 04:28:53 PM
On Monday, June 09, 2014 04:28:53 PM Khangelani Gama wrote:
> Please help me with this, my secondary server shows a replication problem.
> It stopped at the file called *00054BAF00AF …*then from here
> primary server kept on sending walfiles, until the walfiles used up the
> disc space
On 06/09/2014 07:28 AM, Khangelani Gama wrote:
Please please help
Before anyone can help you will need to provide more information on what
your archiving, replication setup is. To begin:
1)Are you doing both archiving and streaming replication?
2) What are the settings in the configuration
Please please help
*From:* Khangelani Gama [mailto:kg...@argility.com]
*Sent:* Monday, June 09, 2014 1:42 PM
*To:* pgsql-general@postgresql.org
*Subject:* pg_standby replication problem
Please help me with this, my secondary server shows a replication problem.
It stopped at the file called
The big question we can’t answer is that when the replication was at this
point (*Command for restore: cp
"/pgsql2/walfiles/00054BAF00B0" "pg_xlog/RECOVERYXLOG"*
) , it then started to say WAL file not present yet. We can’t find
this *00054BAF00B0
*file any where* . *
*
FilesystemSize Used Avail Use% Mounted on
/dev/sda3 57G 15G 39G 28% /
/dev/mapper/vg0-pgsql2
5.4T 5.3T 0 100% /pgsql2
/dev/sda1 99M 12M 83M 13% /boot
tmpfs 30G 0 30G 0% /dev/shm
*Disc spac
Please help me with this, my secondary server shows a replication problem.
It stopped at the file called *00054BAF00AF** …*then from here
primary server kept on sending walfiles, until the walfiles used up the
disc space in the data directory. How do I fix this problem. It’s postgres
9.
Am 05.12.2011 17:02, schrieb Cédric Villemain:
> Le 5 décembre 2011 12:16, Frank Lanitz a écrit :
>> Hi list,
>>
>> We had in past from time to time the issue, that the standby server is
>> stopping recovering, creating a new timeline and become up and running.
>> In parallel to check for the reas
Le 5 décembre 2011 12:16, Frank Lanitz a écrit :
> Hi list,
>
> We had in past from time to time the issue, that the standby server is
> stopping recovering, creating a new timeline and become up and running.
> In parallel to check for the reasons of this behavior we are looking for
> a clean way
On Mon, Dec 05, 2011 at 12:16:29PM +0100, Frank Lanitz wrote:
> Hi list,
>
> We had in past from time to time the issue, that the standby server is
> stopping recovering, creating a new timeline and become up and running.
> In parallel to check for the reasons of this behavior we are looking for
>
Hi list,
We had in past from time to time the issue, that the standby server is
stopping recovering, creating a new timeline and become up and running.
In parallel to check for the reasons of this behavior we are looking for
a clean way to check whether warm standby database is still in
recovering
Hi Robert,
Thanks for ur views, I got an advice from a DB professional
Raghavendra Rao as below it worked
From your contrib/pg_standby location you need to first set the path
for pg_config and do ./configure or directly make, make install. This
will create pg_standby executable in pos
On Tue, Nov 22, 2011 at 4:09 AM, khizer wrote:
> Hi,
>
> May i know how to install pg_standby for postgresql8.2 in ubuntu 10.10
> OS
> I copied the pg_standby folder for compilation which has the files
> pg_standby.c, Makefile
>
> initially i tried with make, make install inside contrip/pg_sta
Hi,
May i know how to install pg_standby for postgresql8.2 in ubuntu
10.10 OS
I copied the pg_standby folder for compilation which has the files
pg_standby.c, Makefile
initially i tried with make, make install inside contrip/pg_standby
folder but i got an err Makefile.global no such fil
On Tue, 2010-12-07 at 16:19 -0800, Greg Swisher wrote:
> Anything more elegant out there?
http://projects.2ndquadrant.com/2warm
--
Simon Riggs http://www.2ndQuadrant.com/books/
PostgreSQL Development, 24x7 Support, Training and Services
--
Sent via pgsql-general mailing list (pg
Hi,
I am using pg_standby in the recovery_command of recover.conf, and with the
d option I am getting an entry every few seconds when it checks for the
trigger and WAL files.
If I leave out the d option, I seem to get nothing. What messages should I
see without the d option? ( I want to try
On Fri, Nov 27, 2009 at 14:19, akp geek wrote:
[...]
> TypeError: iteration over non-sequence
> I am not able to interpret any thing from the above message. Can you please
> give me some thoughts
I can't say anything about the application itself, but the cryptic
message means that the variable
When I execute the command cmd_archiver -I I am getting the following
response
Traceback (most recent call last):
File "/export/home/postgres/8.4/pitrtools/cmd_archiver", line 56, in ?
config.read(configfile)
File "/usr/lib/python2.4/ConfigParser.py", line 262, in read
for filename in
On Wed, 2009-11-25 at 17:24 -0500, akp geek wrote:
> OSError: [Errno 2] No such file or directory: '/opt/postgres/archive/
> 10.100.101.150'
Did you see this message?
--
Devrim GÜNDÜZ, RHCE
Command Prompt - http://www.CommandPrompt.com
devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linu
On Wed, 2009-11-25 at 17:24 -0500, akp geek wrote:
> I have been trying to use the PITR tools , I am running into the
> following issue. I don't know how to resolve it. can you please help?
> I tried to search the online blogs, I did not find much for the error.
> OSError: [Errno 2] No such file o
I have been trying to use the PITR tools , I am running into the following
issue. I don't know how to resolve it. can you please help?
I tried to search the online blogs, I did not find much for the error.
NOTICE: check_config_func()
NOTICE: Performing standard archive
NOTICE: archive_func()
NOTIC
akp geek wrote:
One small doubt I have is , do we have to keep the backup_label on
the standby, I deleted it before I start the restore process , it
still worked .. Just curious
The backup label is strictly for you to read, to help make sure you got
all of the archived segments necessary for t
Thanks a lot Richard. The culprit in my case is the restore command , I
modified it as follows per your instructions , it is fine now
restore_command = 'pg_standby -d -s 5 -t /tmp/pg_standby.trigger.5432
/opt/postgres/archive %f %p %r 2>>/tmp/standby.log'
One small doubt I have is , do we have
akp geek wrote:
> Hi experts -
>
> I am running into issue with pg_standby. May be my
> understanding is not correct. Please help. here is what I did .
>
>
>1. I made changes in the postgresql.conf ( archive_mode = on
>,archive_command = 'cp -i %p /opt/postgres/archi
Hi experts -
I am running into issue with pg_standby. May be my
understanding is not correct. Please help. here is what I did .
1. I made changes in the postgresql.conf ( archive_mode = on
,archive_command = 'cp -i %p /opt/postgres/archive/%f' , archive_timeout =
60
On Fri, 2009-11-20 at 12:14 -0500, akp geek wrote:
> Thanks for the response . I was not able to get back on this.. Our set
> up is Solaris. will be there any thing that I can use on Solaris
They should work on Solaris. It is just Python + Utilities you can
already get (like rsync and ssh).
>
>
Thanks for the response . I was not able to get back on this.. Our set
up is Solaris. will be there any thing that I can use on Solaris
Regards
On Wed, Nov 18, 2009 at 4:58 PM, Joshua D. Drake wrote:
> On Wed, 2009-11-18 at 16:46 -0500, akp geek wrote:
>> Hi All -
>>
>> I would lik
On Wed, 2009-11-18 at 16:46 -0500, akp geek wrote:
> Hi All -
>
> I would like to know if any one has instructions on how
> to setup pg_standby, if so can you please share?
If you are on a *nix platform, I would suggest PITRTools which utilizes
pg_standby but gives you a more comple
Hi All -
I would like to know if any one has instructions on how
to setup pg_standby, if so can you please share?
Thanks for the help
Regards
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mail
2) What file is not found? It sorta looks like the pg_standby
binary, but I'm not sure that I believe that.
Permissions problems on some containing directory, perhaps?
It's the same directory as the postgresql binaries, and they all have
sane
permissions. (root:root, 755). Ls finds it,
Eric Soroos writes:
> 2009-03-12 13:40:18 PDT LOG: starting archive recovery
> 2009-03-12 13:40:18 PDT LOG: restore_command = "/usr/lib/postgresql/
> 8.2/bin/pg_standby -l -d -k 100 -r 2 -s 2 -w 0 -t /tmp/pgsql.trigger.
> 5432 /data/pg/repl-db3 %f %p 2>> standby.log"
> 2009-03-12 13:40:18 PDT
Hi,
I'm setting up a replacement standby server. I've had this working
before until the old standby server lost a drive array and a
motherboard. So, my process was working. On the other hand, the old
slave was debian etch, with a backported 8.2 release, and the new one
is ubuntu 8.04.
Are there any known issues with pg_standby in linking mode with the WAL
source on a read only filesystem?Everything works as expected until I
touch the trigger file. When it is in copy mode everything works
perfectly.
LOG: archive recovery complete
PANIC: could not open file "pg_xlog/0
On Wed, May 21, 2008 at 4:14 AM, Vlad Kosilov <[EMAIL PROTECTED]> wrote:
> as Greg pointed out: my use of rsync --remove-sent-files option had
> contributed to a short sized wal log file on standby.
> changing master's postgres crontab to the following helped to resolve the
> issue:
>
> # ship log
as Greg pointed out: my use of rsync --remove-sent-files option had
contributed to a short sized wal log file on standby.
changing master's postgres crontab to the following helped to resolve
the issue:
# ship logs to standby:
*/2 * * * * rsync -aq /wal_archive_local/ 10.10.10.12::wal_archi
I've been having problem with pgsql-8.2.5 master/slave warm standby
replication setup where occasionally master node generates a wal file
smaller then expected 16MB. pg_standby on slave gets stuck on such short
files, and replication halts from that moment on. we have to do
pg_start_backup/ rsy
Greg, I think you might be onto something here. your suggestion prompts
to get rid off --remove-sent-files in my rsync command, and clean up wal
files from master by some other means, this way even if master's rsync
picks partial file on the first run, it should update and complete file
once it
On Sat, 17 May 2008, Ioannis Tambouras wrote:
The archive command tests if the wal segment exists and is a file,
but it does not check if the file is still being written.
That's because it doesn't have to; the archive command doesn't get called
until the writing is done.
I don't have sourc
On Sun, May 18, 2008 at 5:48 AM, Vlad Kosilov <[EMAIL PROTECTED]> wrote:
> is this wrong of me to expect that postgres would not make a wal file
> available to archive_command unless it was completely ready to let go of
> that wal file?
>
thats a perfectly reasonable expectation; and thats exactl
is this wrong of me to expect that postgres would not make a wal file
available to archive_command unless it was completely ready to let go of
that wal file?
thanks,
V.
Ioannis Tambouras wrote:
archive_command = 'test ! -f /usr/local/wal_archive_local/%f && cp %p
/usr/local/wal_archive_loca
Gurjeet Singh wrote:
archive_command = 'test ! -f /usr/local/wal_archive_local/%f && cp %p
/usr/local/wal_archive_local/%f'
archive files are then moved on master to standby every other minute:
rsync -aq --remove-sent-files /usr/local/wal_archive_local/
slave::wal_archive/
slave's recovery.co
> archive_command = 'test ! -f /usr/local/wal_archive_local/%f && cp %p
> /usr/local/wal_archive_local/%f'
The archive command tests if the wal segment exists and is a file,
but it does not check if the file is still being written. You need to
copy the file after writing has finished (it re
On Sun, May 18, 2008 at 12:17 AM, Vladimir Kosilov <[EMAIL PROTECTED]>
wrote:
> I've been having problem with pgsql-8.2.5 master/slave warm standby
> replication setup where occasionally master node generates a wal file
> smaller then expected 16MB. pg_standby on slave gets stuck on such short
> f
I've been having problem with pgsql-8.2.5 master/slave warm standby
replication setup where occasionally master node generates a wal file
smaller then expected 16MB. pg_standby on slave gets stuck on such short
files, and replication halts from that moment on. we have to do
pg_start_backup/ rsy
On Tuesday 13 May 2008 12:48:38 Guillaume Lelarge wrote:
> Alvaro Herrera a écrit :
> > someone wrote:
> Can I shutdown Server B (backup/recovery postmaster) simply by
> killing the postmaster and restart it back in recovery mode to
> continue re-syncing where it left off? Or does s
Alvaro Herrera a écrit :
someone wrote:
Can I shutdown Server B (backup/recovery postmaster) simply by
killing the postmaster and restart it back in recovery mode to
continue re-syncing where it left off? Or does stopping Server B
while in recovery mode require any manual re-sync steps be
David Wall <[EMAIL PROTECTED]> writes:
>> IIRC, it works conveniently in 8.2 and up. Just do pg_ctl stop -m fast.
> Thanks, Tom. What about if the postmaster is just killed (kill pid, or
> kill -9 pid) or the server/OS crashes? Will PG 8.3 in recovery mode be
> able to come back up okay and r
Thanks, Guillaume. Can anyone confirm his answer to the question below
about restarting the backup postmaster?
IIRC, it works conveniently in 8.2 and up. Just do pg_ctl stop -m fast.
Thanks, Tom. What about if the postmaster is just killed (kill pid, or
kill -9 pid) or the serve
David Wall <[EMAIL PROTECTED]> writes:
> Thanks, Guillaume. Can anyone confirm his answer to the question below
> about restarting the backup postmaster?
IIRC, it works conveniently in 8.2 and up. Just do pg_ctl stop -m fast.
regards, tom lane
--
Sent via pgsql-gener
someone wrote:
>>> Can I shutdown Server B (backup/recovery postmaster) simply by
>>> killing the postmaster and restart it back in recovery mode to
>>> continue re-syncing where it left off? Or does stopping Server B
>>> while in recovery mode require any manual re-sync steps before it can
Thanks, Guillaume. Can anyone confirm his answer to the question below
about restarting the backup postmaster?
It seems counter-intuitive since the backup server is only waiting for
new WAL files to restore, it would seem it could be killed and restarted
at any time and it should just recover
David Wall a écrit :
[...]
During regular operations, Server A and Server B may independently need
to be rebooted or postgresql restarted, etc. Is there any sync-ing
between Server A and Server B I have to worry about when doing this?
That is, will Server B need to know anything about the fact
Just wanted to see if others would confirm my impressions about running
WAL archiving and pg_standby restore.
Server A (Primary): Runs PG 8.3 with WAL archiving enabled. Each WAL is
copied over the network to Server B. (A previous 'tar backup' of the
database along with the requisite psql co
Hi all -
I've setup a warm standby using WAL archiving and pg_standby and it
seems to be mostly working. I do have a few questions though:
Here's my archive_comand and restore_command for reference
(postgres_db_2 is a hosts entry in case you were wondering).
archive_command = 'scp -q %p postgre
On Sun, 2007-09-16 at 11:18 -0700, Jeff Davis wrote:
> On Sun, 2007-09-16 at 09:25 +0100, Simon Riggs wrote:
> > Well, the definition of it working correctly is that a "restored log
> > file..." message occurs. Even with archive_timeout set there could be
> > various delays before that happens. We
On Mar 7, 2008, at 8:49 AM, Tonton Dede wrote:
Hi,
I have downloaded the bin postgresql)8.3 for solaris x86. Where can
I find the pg_standby binary. Or do I really need to compile it myself
pg_standby is a pg client program, i.e a separate program. So, unless
the place from which you do
Hi,
I have downloaded the bin postgresql)8.3 for solaris x86. Where can I
find the pg_standby binary. Or do I really need to compile it myself
Kind regards,
TD
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.or
On Sun, 2007-09-16 at 09:25 +0100, Simon Riggs wrote:
> Well, the definition of it working correctly is that a "restored log
> file..." message occurs. Even with archive_timeout set there could be
> various delays before that happens. We have two servers and a network
> involved, so the time might
On Thu, 2007-09-13 at 11:38 -0700, Jeff Davis wrote:
> I think it would be useful if pg_standby (in version 8.3 contrib) could
> be observed in some way.
>
> Right now I use my own standby script, because every time it runs, it
> touches a file in a known location. That allows me to monitor that f
On Thu, 2007-09-13 at 15:13 -0500, Erik Jones wrote:
> On Sep 13, 2007, at 3:02 PM, Jeff Davis wrote:
>
> > On Thu, 2007-09-13 at 14:05 -0500, Erik Jones wrote:
> >> If you include the -d option pg_standby will emit logging info on
> >> stderr so you can tack on something like 2>> logpath/standby.
On Sep 13, 2007, at 3:02 PM, Jeff Davis wrote:
On Thu, 2007-09-13 at 14:05 -0500, Erik Jones wrote:
If you include the -d option pg_standby will emit logging info on
stderr so you can tack on something like 2>> logpath/standby.log.
What it is lacking, however, is timestamps in the output when
On Thu, 2007-09-13 at 14:05 -0500, Erik Jones wrote:
> If you include the -d option pg_standby will emit logging info on
> stderr so you can tack on something like 2>> logpath/standby.log.
> What it is lacking, however, is timestamps in the output when it
> successfully recovers a WAL file.
On Sep 13, 2007, at 1:38 PM, Jeff Davis wrote:
I think it would be useful if pg_standby (in version 8.3 contrib)
could
be observed in some way.
Right now I use my own standby script, because every time it runs, it
touches a file in a known location. That allows me to monitor that
file,
and
I think it would be useful if pg_standby (in version 8.3 contrib) could
be observed in some way.
Right now I use my own standby script, because every time it runs, it
touches a file in a known location. That allows me to monitor that file,
and if it is too stale, I know something must have gone wr
On Mon, 2007-06-18 at 13:26 -0400, Woody Woodring wrote:
> I am wondering if there is a proper procedure for shutting down the
> warm_standby server (8.2.4)? I am using pg_standby as my restore script in
> my testing:
>
> [EMAIL PROTECTED] cat recovery.conf
> restore_command = 'pg_standby -m -d -
I am wondering if there is a proper procedure for shutting down the
warm_standby server (8.2.4)? I am using pg_standby as my restore script in
my testing:
[EMAIL PROTECTED] cat recovery.conf
restore_command = 'pg_standby -m -d -s 5 -w 0 -t /tmp/pgsql.trigger.5432
/usr/local2/pg_archive %f %p 2>>
After being asked to implement a warm standby server, I was pleased
to happen upon Simon's pg_standby contribution. I was even more
pleased to discover that it was designed to be compatible with the
8.2.x releases despite not being officially released until 8.3. I was
then even more pleased
On Mar 29, 2:17 pm, [EMAIL PROTECTED] ("Thomas F. O'Connell") wrote:
> I see that Simon has pushed pg_standbyinto contrib for 8.3. Is there
> anything that would make the current version in CVS unsuitable for
use
> in 8.2.x? I've done a cursory inspection of the code, but I'll admit
> that I ha
I've been testing pg_standby as a helper application for a warm
standby setup. So far, so good. When the environment is controlled
and everything happens as expected, I'm able to operate a basic
primary/standby setup. (This is all using 8.2.3 on Solaris x86, btw.)
One thing I noticed in ear
I see that Simon has pushed pg_standby into contrib for 8.3. Is there
anything that would make the current version in CVS unsuitable for use
in 8.2.x? I've done a cursory inspection of the code, but I'll admit
that I haven't looked up the interfaces used from postgres_fe.h and
pg_config_manual.h to
On Thu, 2007-01-11 at 14:20 -0500, Merlin Moncure wrote:
> I am looking into using pg_standby (v3) in a warm standby system. I'm
> going to double check it, but same machine replication seemed to work
> ok. When I tried to do remote server log shipping however, I had some
> issues.
>
> Initial
I am looking into using pg_standby (v3) in a warm standby system. I'm
going to double check it, but same machine replication seemed to work
ok. When I tried to do remote server log shipping however, I had some
issues.
Initial setup and launch is working ok, my archive command is:
'test ! -f /va
81 matches
Mail list logo
