Re: Per tuple overhead, cmin, cmax, OID

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Marc G(dot) Fournier" <scrappy(at)hub(dot)org>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Manfred Koizar <mkoi-pg(at)aon(dot)at>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Per tuple overhead, cmin, cmax, OID
Date: 2002-06-08 04:10:34
Message-ID: 11319.1023509434@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Uh guys ... what I *said* was:

> I think we are planning to go beta in late summer (end of August, say).
> Probably in July we'll start pressing people to finish up any major
> development items, or admit that they won't happen for 7.3.

By which I meant that in July we should start hounding anyone who's got
major unfinished work. (Like, say, me, if the schema changes are still
incomplete then.) Not that we won't accept the work when it gets here,
just that that'll be the time to start demanding closure on big 7.3
changes.

And yes, I *would* be pretty upset with the idea of applying major
patches in the last weeks of August, if they are changes that pop up
out-of-the-blue at that time. If it's finishing up work that the
community has already approved, that's a different scenario. But big,
poorly-reviewed feature additions right before beta are exactly my idea
of how to mess up that reputation for stability that Marc was touting...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2002-06-08 04:42:20 Re: [HACKERS] Schemas: status report, call for developers
Previous Message Bruce Momjian 2002-06-08 04:08:47 Re: postgresql.conf -> debug_level