Re: [COMMITTERS] pgsql: Include more status information in walsender results

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [COMMITTERS] pgsql: Include more status information in walsender results
Date: 2011-02-06 00:54:42
Message-ID: AANLkTim02aOuBGCXxmzHT99HZT8_L8mwfg9jub4S90n+@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Thu, Feb 3, 2011 at 7:56 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> Include more status information in walsender results
>
> Add the current xlog insert location to the response of
> IDENTIFY_SYSTEM, and adds result sets containing start
> and stop location of backups to BASE_BACKUP responses.

Does this have anything to do with the following error message I'm now
getting when trying to use streaming replication?

FATAL: invalid response from primary server
DETAIL: Expected 1 tuple with 2 fields, got 1 tuples with 3 fields.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2011-02-06 05:30:58 pgsql: Tighten ALTER FOREIGN TABLE .. SET DATA TYPE checks.
Previous Message Bruce Momjian 2011-02-05 04:28:15 pgsql: Add C comment about why older compilers complain about basebacku

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2011-02-06 05:40:23 Re: SSI patch version 14
Previous Message Noah Misch 2011-02-06 00:44:31 Re: ALTER TYPE 2: skip already-provable no-work rewrites