| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-hackers(at)postgresql(dot)org, jd(at)commandprompt(dot)com, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us> |
| Subject: | Re: 8.4 release planning |
| Date: | 2009-01-28 03:24:07 |
| Message-ID: | 603c8f070901271924r709ef31bv895120ffc09c3872@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> I think the best thing we could do overall is to set release dates and
> stick to them. If your patch is not ready, well, at least it will get
> out in a defined amount of time. Right now, the *real* problem with it
> being pushed to the next release is you don't know how successful some
> other guy will be at persuading us to delay the next release.
+1, LOL.
Let's not forget that we've already got CTE, window functions, partial
vacuums, and column-level permissions, all of which are major features
that should benefit a lot of people. I hope Hot Standby gets
committed but even if it doesn't, I'm still going to get a lot of
benefit out of this release, so I'd like it to happen on some sort of
reasonable time scale.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jaime Casanova | 2009-01-28 03:48:19 | Re: 8.4 release planning |
| Previous Message | Robert Haas | 2009-01-28 03:12:42 | Re: pg_upgrade project status |