Re: 10 weeks to feature freeze (Pending Work)

From: Rick Gigger <rick(at)alpinenetworking(dot)com>
To: Gregory Stark <stark(at)enterprisedb(dot)com>
Cc: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: 10 weeks to feature freeze (Pending Work)
Date: 2007-02-07 00:04:52
Message-ID: 45C917A4.7010401@alpinenetworking.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Gregory Stark wrote:
> "Rick Gigger" <rick(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]
>> This is useful for checking PITR recovery."
>
> No, nobody worked on it prior to 8.2. Afaik there's still nobody working on
> it. It's not trivial. Consider for example that your read-only query would
> still need to come up with a snapshot and there's nowhere currently to find
> out what transactions were in-progress at that point in the log replay.
>
> There's also the problem that currently WAL replay doesn't take have allow for
> any locking so there's no way for read-only queries to protect themselves
> against the WAL replay thrashing the buffer pages they're looking at.
>
> It does seem to be doable and I agree it would be a great feature, but as far
> as I know nobody's working on it for 8.3.

Thanks again for the update.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan Wieck 2007-02-07 00:29:11 Re: Proposal: Commit timestamp
Previous Message Rick Gigger 2007-02-07 00:03:30 Re: 10 weeks to feature freeze (Pending Work)