Skip site navigation (1) Skip section navigation (2)

9.2 commitfest closure (was "Command Triggers, v16")

From: Thom Brown <thom(at)linux(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: 9.2 commitfest closure (was "Command Triggers, v16")
Date: 2012-03-26 22:24:51
Message-ID: CAA-aLv5gE03gGOuiTjRJBnHuGCMXV-o_ZC363hbxrqs-7a5deQ@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On 26 March 2012 23:16, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Mar 26, 2012, at 5:36 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Well, I think I'm definitely on the hook for the pg_stat_statements,
>> pgsql_fdw, foreign table stats, and caching-stable-subexpressions
>> patches, and I should look at the libpq alternate row returning
>> mechanism because I suspect I was the last one to mess with that libpq
>> code in any detail.  I don't claim any special insight into the other
>> stuff on the list.  In particular I've not been paying much attention
>> to command triggers.
>
> How long will that all take?
>
> I guess I'll work on command triggers, pg_archivecleanup, and buffer I/O timings next.

This is probably a dumb question but... surely there's more than 2
committers able to review?

-- 
Thom

pgsql-hackers by date

Next:From: Daniel FarinaDate: 2012-03-26 23:09:42
Subject: Re: Cross-backend signals and administration (Was: Re: pg_terminate_backend for same-role)
Previous:From: Robert HaasDate: 2012-03-26 22:16:37
Subject: Re: Command Triggers, v16

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group