Re: Immediate standby promotion

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Immediate standby promotion
Date: 2014-09-25 18:00:30
Message-ID: CA+TgmoZYC7RCHLUzuSzmz2BYnnfzwxbasbMzLoGt0VjvdMPFJA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Sep 25, 2014 at 1:30 PM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
>> Yes it does cause data loss. The clueful operator has no idea where
>> they are so there is no "used rightly" in that case.
>
> What? There definitely are cases where you don't need to know that to
> the T. Just think of the - quite frequently happening - need to promote
> a standby to run tests or reporting queries that can't be run on a
> standby.
>
> Sure, you shouldn't use it if you expect a very specific set of the data
> being there, but that's not always necessary.

Very well put. +1.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2014-09-25 18:02:51 Re: proposal: rounding up time value less than its unit.
Previous Message Andres Freund 2014-09-25 17:32:06 Re: jsonb format is pessimal for toast compression