Re: 10 weeks to feature freeze (Pending Work) - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: 10 weeks to feature freeze (Pending Work)
Date
Msg-id 7664DD51-8315-44A1-B0C9-A5070F4E88A3@decibel.org
Whole thread Raw
In response to Re: 10 weeks to feature freeze (Pending Work)  ("Andrew Hammond" <andrew.george.hammond@gmail.com>)
Responses Re: 10 weeks to feature freeze (Pending Work)  ("Andrew Hammond" <andrew.george.hammond@gmail.com>)
Re: 10 weeks to feature freeze (Pending Work)  (Rick Gigger <rick@alpinenetworking.com>)
List pgsql-hackers
On Feb 5, 2007, at 12:53 PM, Andrew Hammond wrote:
> On Jan 26, 2:38 pm, t...@sss.pgh.pa.us (Tom Lane) wrote:
>> Rick Gigger <r...@alpinenetworking.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@nasby.net
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)




pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: doxygen.postgresql.org
Next
From: Jim Nasby
Date:
Subject: Re: [PATCHES] Fix "database is ready" race condition