Re: Replication: slave is in permanent startup 'recovery' - Mailing list pgsql-general

From Henry C.
Subject Re: Replication: slave is in permanent startup 'recovery'
Date
Msg-id 815aa26cae02e9a9eca185addb1cfcda.squirrel@zenmail.co.za
Whole thread Raw
In response to Re: Replication: slave is in permanent startup 'recovery'  ("Henry C." <henka@cityweb.co.za>)
List pgsql-general
> However, a SELECT eventually fails with "canceling statement due to conflict
> with recovery".
>
> Where else can I check, or what else can I do to determine what the problem
> is?

...or maybe there _is_ no problem.

select count(*) from big_table; -- will fail because it's long-lived and rows
are changing (deletes, inserts, updates) underneath it.

select * from big_table where id=nnn; -- succeeds because the window for
something in that particular row to change during the select is too small.

All's good!

Sorry about the noise.

h


pgsql-general by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Cannot start Postgres : invalid data in PID file
Next
From: "Henry C."
Date:
Subject: Re: SSDs with Postgresql?