Re: Feature request: pg_basebackup --force

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Joshua Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Feature request: pg_basebackup --force
Date: 2011-04-10 17:15:39
Message-ID: 4DA1E5BB.1040207@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 10.04.2011 20:06, Robert Haas wrote:
> On Sun, Apr 10, 2011 at 12:41 PM, Robert Haas<robertmhaas(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Oleg Bartunov 2011-04-10 17:45:12 Re: k-neighbourhood search in databases
Previous Message Vaibhav Kaushal 2011-04-10 17:08:48 Re: How would sorting work with millions of rows in a huge DB with PG?