On Wed, Oct 26, 2011 at 6:41 PM, Chris Redekop ch...@replicon.com wrote:
Caveat #2 applies here
http://developer.postgresql.org/pgdocs/postgres/hot-standby.html#HOT-STANDBY-CAVEATS
The consistent state is delayed until your long running transactions
end, which is workload dependent but
Caveat #2 applies here
http://developer.postgresql.org/pgdocs/postgres/hot-standby.html#HOT-STANDBY-CAVEATS
The consistent state is delayed until your long running transactions
end, which is workload dependent but transient.
I'm not quite sure how this correlates to what I'm seeing in
On Tue, Oct 18, 2011 at 6:39 PM, Samuel Hwang sam...@replicon.com wrote:
The log is getting from PostgreSQL 9.0.4
Basically we set up streaming replication hot-standby slave while master is
under heavy load
The slave started but not accepting read-only queries,
every request will trigger the
On 19/10/11 01:39, Samuel Hwang wrote:
The log is getting from PostgreSQL 9.0.4
Basically we set up streaming replication hot-standby slave while master
is under heavy load
The slave started but not accepting read-only queries,
every request will trigger the FATAL: the database system is
The log is getting from PostgreSQL 9.0.4
Basically we set up streaming replication hot-standby slave while master is
under heavy load
The slave started but not accepting read-only queries,
every request will trigger the FATAL: the database system is starting up
error.
The slave will eventually
