Re: [HACKERS] LIMITS

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: Jan Wieck <jwieck(at)debis(dot)com>
Cc: Chris Bitmead <chris(dot)bitmead(at)bigfoot(dot)com>, pgsql-hackers(at)hub(dot)org
Subject: Re: [HACKERS] LIMITS
Date: 1999-06-01 15:53:22
Message-ID: 199906011553.LAA14381@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Chris Bitmead wrote:
>
> >
> > Tom Lane wrote:
> > >
> > > Chris Bitmead <chris(dot)bitmead(at)bigfoot(dot)com> writes:
> > > > getTypes(): SELECT failed. Explanation from backend: 'ERROR: nodeRead:
> > > > Bad type 0
> > > > '.
> > >
> > > Did you do a full recompile and initdb?
> >
> > I did a full compile, but I didn't do an initdb. I was upgrading from a
> > 6.5 beta of about a month ago to the latest CVS. Should it be necessary?
>
> I think we shouldn't call anything BETA until it is released.
> The current CVS tree has ALPHA state.
>
> Until the official release (when Marc rolls the tarball),
> development can cause all kind of changes, including schema
> changes to system catalogs, print strings for
> parsetrees/plans etc. Those changes require an initdb run
> because the db files aren't binary compatible any more or the
> corresponding node read functions aren't able to get back the
> right trees from the string representations found in the
> catalogs.
>
> Until Marc officially releases BETA, you should allways
> compile clean and run initdb after cvs updates. It's not the
> first time you've got trapped by this.

But we have been in beta officially since at least May 1. Why is this
not beta?

--
Bruce Momjian | http://www.op.net/~candle
maillist(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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pablo Funes 1999-06-01 16:09:36 Re: [HACKERS] please?
Previous Message Bruce Momjian 1999-06-01 15:49:18 Re: [HACKERS] Re: [SQL] Column name's length