Greg Smith wrote:
On Thu, 4 Jun 2009, Geoffrey wrote:
For now, I'm still looking at the other tools as well as attempting to
verify that my current solution doesn't miss any 'little issues.'
The main thing you want to test out are that it acts sanely when the
network connection to the destin
On Thu, 4 Jun 2009, Geoffrey wrote:
For now, I'm still looking at the other tools as well as attempting to verify
that my current solution doesn't miss any 'little issues.'
The main thing you want to test out are that it acts sanely when the
network connection to the destination server is out
Joshua D. Drake wrote:
On Wed, 2009-06-03 at 15:07 -0400, Geoffrey wrote:
You are still going to need to either:
A. Reinvent the wheel, by scripting it all yourself
B. Use solutions that are already used by others such as walmgr or
pitrtools
My assumption was that since pg_standby does not hav
Greg Smith wrote:
On Wed, 3 Jun 2009, Geoffrey wrote:
My assumption was that since pg_standby does not have the scp/rsync
functionality, I would have to either modify it, change the way we do
things, or 'reinvent' a little different wheel.
There are three things to setup here:
1) archive_co
On Wednesday 03 June 2009 17:11, Joshua D. Drake wrote:
> On Wed, 2009-06-03 at 16:45 -0400, Terry Lee Tucker wrote:
> > > --
> > > * Greg Smith gsm...@gregsmith.com http://www.gregsmith.com Baltimore,
> > > MD
> >
> > Our circumstance here is that we will be feeding multiple warm stand-by
> > serv
On Wed, 2009-06-03 at 16:45 -0400, Terry Lee Tucker wrote:
> > --
> > * Greg Smith gsm...@gregsmith.com http://www.gregsmith.com Baltimore, MD
>
> Our circumstance here is that we will be feeding multiple warm stand-by
> servers; one local and the rest remote, that is, at least one in other stat
On Wednesday 03 June 2009 15:26, Greg Smith wrote:
> On Wed, 3 Jun 2009, Geoffrey wrote:
> > My assumption was that since pg_standby does not have the scp/rsync
> > functionality, I would have to either modify it, change the way we do
> > things, or 'reinvent' a little different wheel.
>
> There ar
On Wed, 2009-06-03 at 15:07 -0400, Geoffrey wrote:
> > You are still going to need to either:
> >
> > A. Reinvent the wheel, by scripting it all yourself
> > B. Use solutions that are already used by others such as walmgr or
> > pitrtools
>
> My assumption was that since pg_standby does not have
On Wed, 3 Jun 2009, Geoffrey wrote:
My assumption was that since pg_standby does not have the scp/rsync
functionality, I would have to either modify it, change the way we do things,
or 'reinvent' a little different wheel.
There are three things to setup here:
1) archive_command on the master
Joshua D. Drake wrote:
On Wed, 2009-06-03 at 14:43 -0400, Geoffrey wrote:
pg_standby is in no way dependent on PITRTools. PITRTools is, however,
dependent on pg_standby. Put another way: you do not need to use
PITRTools to use pg_standby. In fact, you also don't need any perl or
shell sc
On Wed, 2009-06-03 at 14:43 -0400, Geoffrey wrote:
>
> > pg_standby is in no way dependent on PITRTools. PITRTools is, however,
> > dependent on pg_standby. Put another way: you do not need to use
> > PITRTools to use pg_standby. In fact, you also don't need any perl or
> > shell scripts t
Erik Jones wrote:
On Jun 3, 2009, at 5:13 AM, Geoffrey wrote:
Thank you Greg for taking the time to explain this as throughly as you
have. I have found a logic problem in my code. I still don't know if
we will use pg_standby as the wrapper code in PITRTools is python and
we are not a pytho
On Jun 3, 2009, at 5:13 AM, Geoffrey wrote:
Thank you Greg for taking the time to explain this as throughly as
you have. I have found a logic problem in my code. I still don't
know if we will use pg_standby as the wrapper code in PITRTools is
python and we are not a python shop. Kinda w
On Wed, Jun 03, 2009 at 08:13:48AM -0400, Geoffrey wrote:
> I'm certainly looking at rsync rather then scp, which really makes more
> sense.
You can mix ssh and rsync. The man pages has this example:
rsync -az -e ssh --delete ~ftp/pub/samba/ nimbus:"~ftp/pub/tridge/samba"
--
Sent via pg
Thank you Greg for taking the time to explain this as throughly as you
have. I have found a logic problem in my code. I still don't know if
we will use pg_standby as the wrapper code in PITRTools is python and we
are not a python shop. Kinda want to stick with what we know (C, perl,
shell).
Joshua D. Drake wrote:
On Tue, 2009-06-02 at 19:44 -0400, Geoffrey wrote:
pg_standby it self isn't a solution for warm standby. It is a component
thereof. Also don't use SCP. Use rsync. Take a look at walmgr or
PITRTools it will make your life easier.
I still don't understand why the pg_standb
On Tue, 2 Jun 2009, Geoffrey wrote:
The problem with my current process is as noted, my script keeps looking
for the *.history file, but never sees it.
From the restore_command section of the documentation:
"The command will be asked for log files that are not present in the
archive; it mu
On Tue, 2009-06-02 at 19:44 -0400, Geoffrey wrote:
>
> > pg_standby it self isn't a solution for warm standby. It is a component
> > thereof. Also don't use SCP. Use rsync. Take a look at walmgr or
> > PITRTools it will make your life easier.
>
> I still don't understand why the pg_standby code
Joshua D. Drake wrote:
On Tue, 2009-06-02 at 15:21 -0400, Geoffrey wrote:
My problem is, I never see a *.history file, thus my script sits in a
loop looking for it. I see the WAL files showing up on the archive
server, but I don't see a *.history file.
What am I missing?
pg_standby it sel
Joshua D. Drake wrote:
On Tue, 2009-06-02 at 15:21 -0400, Geoffrey wrote:
My problem is, I never see a *.history file, thus my script sits in a
loop looking for it. I see the WAL files showing up on the archive
server, but I don't see a *.history file.
What am I missing?
pg_standby it sel
Geoffrey wrote:
Joshua D. Drake wrote:
On Tue, 2009-06-02 at 15:21 -0400, Geoffrey wrote:
My problem is, I never see a *.history file, thus my script sits in a
loop looking for it. I see the WAL files showing up on the archive
server, but I don't see a *.history file.
What am I missing?
Joshua D. Drake wrote:
On Tue, 2009-06-02 at 15:21 -0400, Geoffrey wrote:
My problem is, I never see a *.history file, thus my script sits in a
loop looking for it. I see the WAL files showing up on the archive
server, but I don't see a *.history file.
What am I missing?
pg_standby it sel
On Tue, 2009-06-02 at 15:21 -0400, Geoffrey wrote:
> My problem is, I never see a *.history file, thus my script sits in a
> loop looking for it. I see the WAL files showing up on the archive
> server, but I don't see a *.history file.
>
> What am I missing?
pg_standby it self isn't a solutio
I'm trying to set up a warm standby via WAL shipping. I'm digging
through the source of pg_standby.c to determine the proper method.
Since we are using scp to access the archive files, pg_standby doesn't
provide a solution to our problem.
From reading the comments in pg_standby.c, I see:
'Ch
24 matches
Mail list logo
