Re: Hot Standby Feedback should default to on in 9.3+

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Hot Standby Feedback should default to on in 9.3+
Date: 2012-11-30 19:26:30
Message-ID: CA+U5nMJuDGTM4nPgmEWWKYU9dTSfdoiDJ5eBnsjdMgHOWcmw_w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 30 November 2012 19:02, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:

> 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?

I don't see a technical objection, perhaps others do.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2012-11-30 19:30:24 Re: pg_basebackup is taking backup of extra files inside a tablespace directory
Previous Message Tom Lane 2012-11-30 19:16:47 Re: missing LockBuffer(buffer, BUFFER_LOCK_SHARE) in trigger.c GetTupleForTrigger?