From: | Rick Gigger <rick(at)alpinenetworking(dot)com> |
---|---|
To: | Jim Nasby <decibel(at)decibel(dot)org> |
Cc: | Andrew Hammond <andrew(dot)george(dot)hammond(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: 10 weeks to feature freeze (Pending Work) |
Date: | 2007-02-11 01:13:45 |
Message-ID: | 45CE6DC9.5060906@alpinenetworking.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Jim Nasby wrote:
> 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
Which is why I was hoping for a PITR based solution. Oh well, I will
have to figure out what is my best option now that I know it will not be
available any time in the near future.
From | Date | Subject | |
---|---|---|---|
Next Message | Hideyuki Kawashima | 2007-02-11 01:34:19 | Acclerating INSERT/UPDATE using UPS |
Previous Message | Benjamin Arai | 2007-02-11 00:56:21 | Priorities for users or queries? |