Re: CF3+4 (was Re: Parallel query execution) - Mailing list pgsql-hackers

From Robert Haas
Subject Re: CF3+4 (was Re: Parallel query execution)
Date
Msg-id CA+TgmoaAG656SYdR4zGod+GBNc-EqD2-eXdRNHgCOS-TY4forg@mail.gmail.com
Whole thread Raw
In response to Re: CF3+4 (was Re: Parallel query execution)  (Phil Sorber <phil@omniti.com>)
Responses Re: CF3+4 (was Re: Parallel query execution)
List pgsql-hackers
On Mon, Jan 21, 2013 at 6:23 PM, Phil Sorber <phil@omniti.com> wrote:
> On Wed, Jan 16, 2013 at 8:18 AM, Abhijit Menon-Sen <ams@2ndquadrant.com> wrote:
>> Here's a breakdown based purely on the names from the CF page (i.e. I
>> didn't check archives to see who actually posted reviews, and didn't
>> take into account reviews posted without updating the CF page).
>
> FWIW, I reviewed at least one at the point you did this survey, and I
> did update the CF page, but I didn't put my name into that box marked
> reviewers because it is an extra step (Edit Patch) that isn't
> immediatly obvious. Isn't there a way to automatically populate that
> based on people linking in their reviews?

Sadly, the CF application doesn't have access to the user name -> real
name mappings.  And while it's only mildly annoying that the updates
are displayed under user name rather than realname, showing username
for the author and reviewers fields would be really annoying,
especially because not all patch authors necessarily even have
accounts.

> I guess it might be
> difficult when a CF manager comes along to add them and they aren't
> their reviews.

That's also an issue.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Request for vote to move forward with recovery.conf overhaul
Next
From: Peter Geoghegan
Date:
Subject: Re: Prepared statements fail after schema changes with surprising error