Re: Unable to compare _bpchar for similarity in WHERE-clause - Mailing list pgsql-bugs

From Bill Studenmund
Subject Re: Unable to compare _bpchar for similarity in WHERE-clause
Date
Msg-id Pine.NEB.4.33.0112191037160.26926-100000@vespasia.home-net.internetconnect.net
Whole thread Raw
In response to Re: Unable to compare _bpchar for similarity in WHERE-clause (MINOR A NNOYANCE)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Mon, 17 Dec 2001, Tom Lane wrote:

> Justin <aa2@bigpond.net.au> writes:
> > On Saturday 15 December 2001 03:06, Tom Lane wrote:
> >> It's too late to fix this in the standard catalogs for 7.2, but I'll
> >> make a note for 7.3.
>
> > Suitable for 7.2.1?
>
> Nyet.  We don't do initdbs for dot-releases.

But whouldn't a patch script be enough for this change? A few insert with
fixed oid commands would do it. No initdb needed, and the oid numbers
could be taken from what will be used for 7.3.

The script would need to make sure there isn't already something at that
oid, and that it hadn't been run already. But nothing should get inserted
with oids in the reserved space anyway. :-)

Take care,

Bill

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: After ~Crash Sequence not correct
Next
From: "Henshall, Stuart - WCP"
Date:
Subject: Re: After ~Crash Sequence not correct