Re: An Idea for OID conflicts

From: Gevik Babakhani <pgdev(at)xs4all(dot)nl>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: An Idea for OID conflicts
Date: 2006-09-18 18:46:57
Message-ID: 1158605217.5590.39.camel@voyager.truesoftware.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 2006-09-18 at 14:36 -0400, Tom Lane wrote:
> Gevik Babakhani <pgdev(at)xs4all(dot)nl> writes:
> > 3. Make a small utility that goes through a patch, finds the new OIDs
> > and changes them back to a value specified by the committer(s).
>
> > Would this be workable?
>
> That utility sounds AI-complete to me ...

Maybe I am missing something here but if the developer used the OIDs
sequentially it won't be that difficult to find and replace the used
range within the patch.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Pascal Meunier 2006-09-18 18:49:23 Re: minor feature request: Secure defaults during
Previous Message Gregory Stark 2006-09-18 18:46:41 Re: An Idea for OID conflicts