From: Jeff Davis <pgsql@j-davis.com>
To: Florian Pflug <fgp@phlo.org>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: postgres hackers <pgsql-hackers@postgresql.org>
Cc: pgsql-rrreviewers@postgresql.org
Subject: Re: [RRR] Three patches which desperately need reviewers
Date: Wed, 13 Jul 2011 19:08:19 -0700
Message-ID: <1310609299.31101.4.camel@jdavis> (raw)
In-Reply-To: <731C9ABF-5B67-487A-B73B-97C37CA7CF0F@phlo.org>
References: <4E1E3B7E.5020605@agliodbs.com>
<731C9ABF-5B67-487A-B73B-97C37CA7CF0F@phlo.org>
On Thu, 2011-07-14 at 02:54 +0200, Florian Pflug wrote:
> On Jul14, 2011, at 02:42 , Josh Berkus wrote:
> > lazy vxid locks
> > https://commitfest.postgresql.org/action/patch_view?id=585
>
> I can try to review that. It does seems to depend on
> the fastlock patch though, and that patch seems to be
> somewhat of a moving target. I'm thus not sure what the
> most reasonable approach is here. I could wait for the
> fastlock patch to be applied, but since the commitfest
> is drawing to a close that might not be the best course
> of action. How is such a situation handled usually?
Moving target? Hopefully not. I marked it "ready for committer" already.
I did give some feedback, but it's nothing that would get in the way of
reviewing the VXID patch.
So please do take a look at the VXID patch. Just apply it over the last
version of the fastlock patch.
I also plan to take a look, but the earliest will be tomorrow.
Regards,
Jeff Davis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-rrreviewers@postgresql.org
Cc: pgsql@j-davis.com, fgp@phlo.org, josh@agliodbs.com, pgsql-hackers@postgresql.org
Subject: Re: [RRR] Three patches which desperately need reviewers
In-Reply-To: <1310609299.31101.4.camel@jdavis>
References: <4E1E3B7E.5020605@agliodbs.com> <731C9ABF-5B67-487A-B73B-97C37CA7CF0F@phlo.org> <1310609299.31101.4.camel@jdavis>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox