Fwd: [HACKERS] [streaming replication] 9.1.3 streaming replication bug ?

From: Michael Nolan <htfoot(at)gmail(dot)com>
To: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Fwd: [HACKERS] [streaming replication] 9.1.3 streaming replication bug ?
Date: 2012-04-11 19:09:53
Message-ID: CAOzAqu+3MWmZCMKisuihuNfeqFvJPi7sF53mwaCTKyY_gDZsog@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

---------- Forwarded message ----------
From: Michael Nolan <htfoot(at)gmail(dot)com>
Date: Wed, 11 Apr 2012 14:48:18 -0400
Subject: Re: [HACKERS] [GENERAL] [streaming replication] 9.1.3
streaming replication bug ?
To: Robert Haas <robertmhaas(at)gmail(dot)com>

On Wed, Apr 11, 2012 at 2:14 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:

>
>
> We've talked about teaching the master to keep track of how far back
> all of its known standbys are, and retaining WAL back to that specific
> point, rather than the shotgun approach that is wal_keep_segments.
> It's not exactly clear what the interface to that should look like,
> though.
>
>
Moreover, how does the database decide when to drop a known standby from
the queue because it has failed or the DBA notify the database that a
particular standby should no longer be included?

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message patrick keshishian 2012-04-11 22:08:34 non-static LIKE patterns
Previous Message Kenneth Tilton 2012-04-11 18:18:33 Re: efficient trigger function selection?

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2012-04-11 19:09:54 Re: how to create a non-inherited CHECK constraint in CREATE TABLE
Previous Message Tom Lane 2012-04-11 19:06:17 Re: how to create a non-inherited CHECK constraint in CREATE TABLE