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 have the scp/rsync
functionality, I would have to either modify it, change the way we do
things, or 'reinvent' a little different wheel.
You wouldn't modify pg_standby. You would create a new utility that
ships logs (or pulls logs) for pg_standby to utilize.
I assume a script that pulls the logs to the warm standby and then calls
pg_standby. That's a thought.
There is also an objection to using the python tools as we are small
shop and do not have anyone who is versed in python.
At best this seems like a very odd requirement. You aren't doing any
development. You are using a utility which is written in a specific
language.
Well, we are an odd group. :)
I have not had a chance to look at walmgr, I will do that shortly.
I believe it is written in Python.
Hmm, I guess I should brush up on my Python.
Anyway good luck!
Thank you.
Joshua D. Drkae
echo Joshua D. Drkae |sed 's/ka/ak/'
:)
--
Until later, Geoffrey
Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.
- Benjamin Franklin
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
