Re: Synchronous replication: status of standby side - Mailing list pgsql-hackers

From Kolb, Harald (NSN - DE/Munich)
Subject Re: Synchronous replication: status of standby side
Date
Msg-id 8F6635BC27831E4BB0923D8A55136C26018DB6A6@DEMUEXC005.nsn-intra.net
Whole thread Raw
In response to Re: Synchronous replication: status of standby side  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: Synchronous replication: status of standby side  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers
Hi,


> -----Original Message-----
> From: ext Fujii Masao [mailto:masao.fujii@gmail.com]
> Sent: Thursday, June 04, 2009 6:25 AM
> To: Kolb, Harald (NSN - DE/Munich)
> Cc: pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Synchronous replication: status of standby side
>
> Hi,
>
> On Thu, Jun 4, 2009 at 12:28 AM, Kolb, Harald (NSN - DE/Munich)
> <harald.kolb@nsn.com> wrote:
> > Hi,
> >
> > will there be a possibility to retrieve the standby
> situation in case of
> > synchronous replication ?
> > We would need a command or similar to report the current
> state and state
> > changes
> > (like: syncing, in-sync, replication broken, ..).
> > Observing and scaning the logfile would not be appropriate.
> > Are there plans for such an interface ?
>
> No, not yet. You think that this feature is a high-priority TODO item?

We are planning to use the HotStandby feature too.
That would require to have the correct state information since we have
to
control the DB clients when and how they can connect or reconnect.
But also in general, from our platform POV it's an important feature to
have the right view on the system at any point of time (e.g. in case of
update avoid switchover if standby is out of sync, ...).
In addition, can we expect that a replication break will be logged as an
important event ?

Regards, Harald.


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: PANIC: corrupted item lengths
Next
From: Magnus Hagander
Date:
Subject: Re: It's June 1; do you know where your release is?