Re: Proposal: make "opaque" obsolete

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Proposal: make "opaque" obsolete
Date: 2002-08-20 20:43:27
Message-ID: 200208202043.g7KKhR903255@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Neil Conway 2002-08-20 20:43:31 Re: @(#)Mordred Labs advisory 0x0003: Buffer overflow in PostgreSQL (fwd)
Previous Message Tom Lane 2002-08-20 20:36:09 Re: @(#)Mordred Labs advisory 0x0003: Buffer overflow in PostgreSQL (fwd)