Re: max_standby_delay considered harmful - Mailing list pgsql-hackers

From Greg Stark
Subject Re: max_standby_delay considered harmful
Date
Msg-id s2h407d949e1005090947s7bbab437v1b2acd8a67e6b066@mail.gmail.com
Whole thread Raw
In response to Re: max_standby_delay considered harmful  (Greg Smith <greg@2ndquadrant.com>)
Responses Re: max_standby_delay considered harmful
List pgsql-hackers
On Sun, May 9, 2010 at 4:00 AM, Greg Smith <greg@2ndquadrant.com> wrote:
>  The use cases are covered as best they can be without better support from
> expected future SR features like heartbeats and XID loopback.

For what it's worth I think deferring these extra complications is a
very useful exercise. I would like to see a system that doesn't depend
on them for basic functionality. In particular I would like to see a
system that can be useful using purely WAL log shipping without
streaming replication at all.

I'm a bit unclear how the boolean proposal would solve things though.
Surely if you set the boolean to recovery-wins then when using
streaming replication with any non-idle master virtually every query
would be cancelled immediately as every HOT cleanup would cause a
snapshot conflict with even short-lived queires in the slave.



--
greg


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: 9.0b1: "ERROR: btree index keys must be ordered by attribute"
Next
From: Robert Haas
Date:
Subject: Re: max_standby_delay considered harmful