Re: Re: multiple hot standby streaming replication scenario with "rotating" the primary server - Mailing list pgsql-admin

From Gerhard Hintermayer
Subject Re: Re: multiple hot standby streaming replication scenario with "rotating" the primary server
Date
Msg-id BANLkTikKGej=BmKaBUPcQu5z16J3J085vw@mail.gmail.com
Whole thread Raw
In response to Re: multiple hot standby streaming replication scenario with "rotating" the primary server  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: Re: multiple hot standby streaming replication scenario with "rotating" the primary server
List pgsql-admin
Because tests & docs say so:
http://www.postgresql.org/docs/9.0/static/continuous-archiving.html#CONTINUOUS-ARCHIVING-CAVEATS
;-) Docs say that this might be fixed sometime.

Also when I try a SELECT statement on the new primary, which makes use
of an index, I get an empty result, even though the tuple is in the
table (by just listing all tuples and see if it is there)

Gerhard

On Mon, Apr 11, 2011 at 6:09 PM, Kevin Grittner
<Kevin.Grittner@wicourts.gov> wrote:
> Gerhard Hintermayer <gerhard.hintermayer@gmail.com> wrote:
>
>> Unfortunately I had to insert 2.1 reindex database [for all
>> databases] after creating the trigger file on the new dedicated
>> primary
>
> Why?
>
> -Kevin
>

pgsql-admin by date:

Previous
From: Vibhor Kumar
Date:
Subject: Re: unsupported header version error
Next
From: "Kevin Grittner"
Date:
Subject: Re: Re: multiple hot standby streaming replication scenario with "rotating" the primary server