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(dot)Grittner(at)wicourts(dot)gov> wrote:
> Gerhard Hintermayer <gerhard(dot)hintermayer(at)gmail(dot)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
>