| From: | "Merlin Moncure" <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | "Peter Eisentraut" <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "Dave Page" <dpage(at)pgadmin(dot)org>, "Douglas McNaught" <doug(at)mcnaught(dot)org>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, "David Fetter" <david(at)fetter(dot)org>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Core team statement on replication in PostgreSQL |
| Date: | 2008-05-29 20:22:13 |
| Message-ID: | b42b73150805291322m3b08a3a3o1bcdc1ecd22c0d47@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-hackers |
On Thu, May 29, 2008 at 3:59 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> Merlin Moncure wrote:
>> Read only slave is the #1 most anticipated feature in the
>> circles I run with.
>
> Do these circles not know about slony and londiste?
Sure.
For various reasons mentioned elsewhere on this thread, a PITR based
replication solution would have a lot of appeal, assuming it could be
made to work. The main thing is that it is completely non-invasive to
the master database and all the work is handled on the standby. It
also operates on a trivial mechanism to transfer the files.
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2008-05-29 20:35:41 | Re: Core team statement on replication in PostgreSQL |
| Previous Message | Peter Eisentraut | 2008-05-29 20:14:14 | Re: Core team statement on replication in PostgreSQL |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2008-05-29 20:26:24 | Re: Avoiding second heap scan in VACUUM |
| Previous Message | Peter Eisentraut | 2008-05-29 20:14:14 | Re: Core team statement on replication in PostgreSQL |