Hot Standby Feedback should default to on in 9.3+ - Mailing list pgsql-hackers

From Andres Freund
Subject Hot Standby Feedback should default to on in 9.3+
Date
Msg-id 20121130190227.GJ3957@awork2.anarazel.de
Whole thread Raw
Responses Re: Hot Standby Feedback should default to on in 9.3+  (Simon Riggs <simon@2ndQuadrant.com>)
Re: Hot Standby Feedback should default to on in 9.3+  (Robert Haas <robertmhaas@gmail.com>)
Re: Hot Standby Feedback should default to on in 9.3+  (Josh Berkus <josh@agliodbs.com>)
Re: Hot Standby Feedback should default to on in 9.3+  (Heikki Linnakangas <hlinnakangas@vmware.com>)
List pgsql-hackers
Hi,

The subject says it all.

There are workloads where its detrimental, but in general having it
default to on improver experience tremendously because getting conflicts
because of vacuum is rather confusing.

In the workloads where it might not be a good idea (very long queries on
the standby, many dead tuples on the primary) you need to think very
carefuly about the strategy of avoiding conflicts anyway, and explicit
configuration is required as well.

Does anybody have an argument against changing the default value?

Greetings,

Andres Freund

-- Andres Freund                       http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Re: missing LockBuffer(buffer, BUFFER_LOCK_SHARE) in trigger.c GetTupleForTrigger?
Next
From: Tom Lane
Date:
Subject: Re: Re: missing LockBuffer(buffer, BUFFER_LOCK_SHARE) in trigger.c GetTupleForTrigger?