Re: Proposal: make "opaque" obsolete - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Proposal: make "opaque" obsolete
Date
Msg-id 200208202043.g7KKhR903255@candle.pha.pa.us
Whole thread Raw
In response to Re: Proposal: make "opaque" obsolete  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> > I think we should throw the notices right away, although this makes me
> > wonder in general about upgrade path.  Are we ever planning to make that
> > an error, and if so, how are we going to handle functions that are coming
> > from previous versions where it was okay?
> 
> We can't make it an error until sufficiently far down the road that we
> don't care about forward compatibility from 7.2-or-before dump files.
> That'll be a long while, probably.
> 
> Throwing a notice right away is okay with me personally, but I wanted to
> see what other people thought...

NOTICE seems good.  We will have all this mentioned in the release notes
too.  In fact, we can point to the release notes in the NOTICE if
desired.

I like the array storage format change too.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: @(#)Mordred Labs advisory 0x0003: Buffer overflow in PostgreSQL (fwd)
Next
From: Neil Conway
Date:
Subject: Re: @(#)Mordred Labs advisory 0x0003: Buffer overflow in PostgreSQL (fwd)