From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | 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:06:24 |
Message-ID: | BANLkTi=aKzjwWY7JCk9UjXreHsx5RW3-zw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Apr 10, 2011 at 12:41 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> It's not integrated and I doubt it's conveniently available on Windows.
>
> One of the biggest problems with our replication functionality right
> now is that it's hard to set up. We've actually done a good job
> making the very simplest case (one slave, no archive) reasonably
> simple, but how many PostgreSQL users do you think can manage to set
> up SR + HS + archiving, with two slaves that can use the archive if
> they fall too far behind the master, but with the archive regularly
> trimmed to the farthest-back segment that is still needed?
>
> We have pg_archivecleanup, but AIUI that's only smart enough to handle
> the one-standby case.
>
> 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".
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Vaibhav Kaushal | 2011-04-10 17:08:48 | Re: How would sorting work with millions of rows in a huge DB with PG? |
Previous Message | Robert Haas | 2011-04-10 16:41:36 | Re: Feature request: pg_basebackup --force |