From: | Jim Nasby <decibel(at)decibel(dot)org> |
---|---|
To: | Andrew Hammond <andrew(dot)george(dot)hammond(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: 10 weeks to feature freeze (Pending Work) |
Date: | 2007-02-07 03:43:48 |
Message-ID: | 7664DD51-8315-44A1-B0C9-A5070F4E88A3@decibel.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Feb 5, 2007, at 12:53 PM, Andrew Hammond wrote:
> On Jan 26, 2:38 pm, t(dot)(dot)(dot)(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane) wrote:
>> Rick Gigger <r(dot)(dot)(dot)(at)alpinenetworking(dot)com> writes:
>>> I thought that the following todo item just barely missed 8.2:
>>> "Allow a warm standby system to also allow read-only statements
>>> [pitr]
>>
>> No, it's a someday-wishlist item; the work involved is not small.
>
> Slony1 has supported log-shipping replication for about a year now. It
> provides similar functionality.
Not really....
1) It's not possible for a PITR 'slave' to fall behind to a state
where it will never catch up, unless it's just on inadequate
hardware. Same isn't true with slony.
2) PITR handles DDL seamlessly
3) PITR is *much* simpler to configure and maintain
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Nasby | 2007-02-07 03:49:04 | Re: [PATCHES] Fix "database is ready" race condition |
Previous Message | Jim Nasby | 2007-02-07 03:36:36 | Re: Modifying and solidifying contrib |