| From: | Gevik Babakhani <pgdev(at)xs4all(dot)nl> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Martijn van Oosterhout <kleptog(at)svana(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: OID conflicts |
| Date: | 2006-09-18 16:04:32 |
| Message-ID: | 1158595472.24177.5.camel@voyager.truesoftware.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 2006-09-18 at 10:43 -0400, Andrew Dunstan wrote:
> Martijn van Oosterhout wrote:
> > On Mon, Sep 18, 2006 at 04:02:56PM +0200, Gevik Babakhani wrote:
> >
> >> I was wondering how one can avoid OID conflicts?
> >> I was testing the uuid patch on a new download from the CVS and
> >> I noticed that some of the OIDs I thought to be free are used by someone
> >> else :(
> >>
> >
> > Not really. At the point of committing it should get sorted out. Did
> > you use the scripts to find free numbers?
> >
> >
> >
>
> Actually, it would be nice to be able to reserve some. It would help
> stop patch bitrot. I know Tom Dunstan wanted to do just that while he
> was working on the enums patch.
>
Yes it would be very. If Tom Dunstan decided not to do that I would like
build such a thing.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2006-09-18 16:09:39 | Re: Release notes |
| Previous Message | Greg Sabino Mullane | 2006-09-18 16:03:41 | Re: information_schema vs temp tables (was Re: [COMMITTERS] pgsql: Sequences were not being shown due to the use of lowercase `s`) |