Re: Feature request: pg_basebackup --force - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: Feature request: pg_basebackup --force
Date
Msg-id 4DA1E5BB.1040207@enterprisedb.com
Whole thread Raw
In response to Re: Feature request: pg_basebackup --force  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Feature request: pg_basebackup --force  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-hackers
On 10.04.2011 20:06, Robert Haas wrote:
> On Sun, Apr 10, 2011 at 12:41 PM, Robert Haas<robertmhaas@gmail.com>  wrote:
>> Admittedly, the above is a slightly different problem, but I think it
>> all points in the direction of needing more automation and more ease
>> of use.
>
> And let me also note that the difficulty of getting this all exactly
> right is one of the things that causes people to come up with creative
> solutions like this:
>
> http://archives.postgresql.org/pgsql-hackers/2010-12/msg02514.php
>
> That's why we need to put it in a box, tie a bow around it, and put up
> a big sign that says "do not look into laser with remaining eye".

That's exactly what pg_basebackup does. Once you move into more 
complicated scenarios with multiple standbys and WAL archiving, it's 
inevitably going to be more complicated to set up.

That doesn't mean that we can't make it easier - we can and we should - 
but I don't think the common complaint that replication is hard to set 
up is true anymore.

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Vaibhav Kaushal
Date:
Subject: Re: How would sorting work with millions of rows in a huge DB with PG?
Next
From: Oleg Bartunov
Date:
Subject: Re: k-neighbourhood search in databases