On Fri, Jul 9, 2010 at 12:54 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>>>> How long should I wait before I start breaking things?
>>>
>>> Did you have any particular breakage in mind?
>
>> Well, you can see for yourself what I've submitted for the next CF.
>
> You might want to hold off on the get_whatever_oid patches for a bit,
> but the other stuff I see there looks pretty localized.  No objection
> to pressing forward with CF work otherwise.

I can hold off on those for a bit - I don't think there will be enough
drift to matter very much, but if it makes you more comfortable, it's
not a big deal.  What I really want to get committed is this one,
which is infrastructure for a further large patch:

include Backend ID in relpath for temp rels
https://commitfest.postgresql.org/action/patch_view?id=302

However, I need someone fairly knowledgeable to review it first.

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

In response to

• Re: [COMMITTERS] pgsql: Stamp HEAD as 9.1devel. at 2010-07-09 04:54:00 from Tom Lane

Responses

• Re: [COMMITTERS] pgsql: Stamp HEAD as 9.1devel. at 2010-08-03 23:33:23 from Robert Haas

pgsql-hackers by date

Next:	From: Robert Haas	Date: 2010-07-09 14:35:10
	Subject: Re: including backend ID in relpath of temp rels - updated patch
Previous:	From: Robert Haas	Date: 2010-07-09 14:07:33
	Subject: Re: ExecutorCheckPerms() hook

pgsql-committers by date

Next:	From: Simon Riggs	Date: 2010-07-09 14:51:27
	Subject: Re: [COMMITTERS] pgsql: Add a hook in ExecCheckRTPerms().
Previous:	From: Robert Haas	Date: 2010-07-09 14:06:01
	Subject: pgsql: Add a hook in ExecCheckRTPerms().