From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: scheduling |
Date: | 2010-08-08 15:41:15 |
Message-ID: | 3587.1281282075@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> Do we have a projected data for the next 9.0 wrap, and will it be
> beta5 or rc1?
No, and don't know ;-). It won't be till after the 15th because
assorted people are on vacation. Perhaps a reasonable plan is to
wrap on the 19th (week from Thursday), and to decide mid next week
whether we feel good about calling it rc1.
> How much should we worry about the remaining open items?
> http://wiki.postgresql.org/wiki/PostgreSQL_9.0_Open_Items
> I am inclined to say that all three of the items currently on the list
> need to be addressed in some way before we move forward... or at least
> the last two.
> * ExplainOnePlan handles snapshots differently than ProcessQuery
> * Backup procedure is wrong?
> * Walreceiver crashes in AIX
I don't think that now is an appropriate time to be messing with the
first item. It is not a 9.0 regression --- the behavior has been that
way for years --- and it is not closely related to any changes we made
in 9.0. If we'd discovered the issue after 9.0.0 release there would
have been absolutely no suggestion of back-patching a change. Also,
it didn't seem to me that we had consensus on what to do about it,
so the thought of a hasty change scares me.
We do need to resolve the others.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-08-08 15:59:52 | Re: pg_stat_user_functions' notion of user |
Previous Message | David Fetter | 2010-08-08 15:40:13 | Re: pg_stat_user_functions' notion of user |