Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] Hot Standby utility and administrator functions

From: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: pgadmin-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] Hot Standby utility and administrator functions
Date: 2008-10-24 08:33:58
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgadmin-hackerspgsql-generalpgsql-hackers
Simon Riggs a écrit :
> On Fri, 2008-10-24 at 09:54 +0200, Guillaume Lelarge wrote:
>> Is there a way to get the IP of the salve (if we are connected to the
>> master? and vice-versa?
> No. They are separately configurable and don't pass that info.

I definitely need to read your mails on pgsql-hackers.

> [...]
>>>> * pg_start_backup()/pg_stop_backup() could work during recovery, but the
>>>> backup history file would need to be manually inserted into the archive
>>>> once complete. Is that acceptable? (Note that we don't know where the
>>>> archive is or how to access that; the information is all in
>>>> recovery_command. We cannot assume that archive_command points to same
>>>> archive. So making it happen automatically is too much work for this
>>>> release, if ever.) If that seems useful, we could do this by avoiding
>>>> any operation that changes WAL stream during recovery: no checkpoints,
>>>> log switches etc.. 
>>>> pg_start_backup() would return XLogRecPtr of last restartpoint.
>>>> pg_stop_backup() would return last known xlrec recovered (we won't keep
>>>> track of this record by record).
>> No interest from pgAdmin's pov.
> I would ask: why not? Why is PITR not part of pgAdmin's capability?

Strictly speaking, pgAdmin is already able to configure PITR. Go on the
configure tool, put your archive command, reload (pre8.3) or restart
(8.3) the server. That's all it needs.

But LogShipping is a different matter. For LogShipping to be part of
pgAdmin's capabilities, we would need to be able to copy all PGDATA
files from the master server to a slave server within pgAdmin. I'm not
sure how we can handle this. Moreover, we would also need to launch the
slave server.

I mean, I would love to build a "PITR/LogShipping wizard": ask the slave
IP, configure postgresql.conf on the master, recovery.conf on the slave,
reload conf on the master, start the slave... but how do we copy files
from one server to the other? how do we start the slave server?

> [...]
>> Oh, I almost forgot. I see you mailed a few projects (pgAdmin, pgpool,
>> pgbouncer). Perhaps you should ask phpPgAdmin's guys too?
> Not on that list, if you are could you pass it on.



In response to

pgsql-hackers by date

Next:From: KaiGai KoheiDate: 2008-10-24 09:01:33
Subject: Re: SE-PostgreSQL wiki updates, but ...
Previous:From: Zdenek KotalaDate: 2008-10-24 08:28:22
Subject: Re: Any reason to have heap_(de)formtuple?

pgadmin-hackers by date

Next:From: Dave PageDate: 2008-10-27 12:37:23
Subject: Re: extending functionality strategy
Previous:From: Simon RiggsDate: 2008-10-24 08:10:36
Subject: Re: [HACKERS] Hot Standby utility andadministrator functions

pgsql-general by date

Next:From: Thom BrownDate: 2008-10-24 08:34:20
Subject: Re: Storing questionnaire data
Previous:From: Simon RiggsDate: 2008-10-24 08:10:36
Subject: Re: [HACKERS] Hot Standby utility andadministrator functions

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group