Re: Per tuple overhead, cmin, cmax, OID

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: "Marc G(dot) Fournier" <scrappy(at)hub(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(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-07 16:27:08
Message-ID: 200206071627.g57GR8017232@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Marc G. Fournier wrote:
> On Fri, 7 Jun 2002, Bruce Momjian wrote:
>
> > I will say that I was disappointed by previous release delays and will be
> > more vocal about moving things forward than I have in the past.
>
> I don't know ... I kinda like being able to confidently say to clients
> that "the latest release is always the most stable/reliable" and not being
> burned by it :) Hell, last release, I started moving to v7.2 on some of
> our production servers around beta4 or so, since a) I was confident and b)
> I needed some of the features ...
>
> Not many software packages you can say that about anymore, eh?

Yes, true, I am not going to push the schedule. What I want to try to
do is keep people more informed of where we are in the release process,
and more informed about the open issues involved.

That squishy freeze is one of those items that is very hard to organize
because it is so arbitrary about what should be added. I think we need
to communicate CODE-CODE-CODE until September 1, then communicate
TEST-TEST-TEST after that. We will not release before it is ready, but
we will marshall our forces better.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2002-06-07 17:42:11 Re: Roadmap for a Win32 port
Previous Message Marc G. Fournier 2002-06-07 16:18:20 Re: Per tuple overhead, cmin, cmax, OID