Re: Solving the OID-collision problem - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Solving the OID-collision problem
Date
Msg-id 9081.1123534537@sss.pgh.pa.us
Whole thread Raw
In response to Re: Solving the OID-collision problem  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: Solving the OID-collision problem  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
Simon Riggs <simon@2ndquadrant.com> writes:
> On Wed, 2005-08-03 at 19:43 -0400, Tom Lane wrote:
>> We've sort of brushed this problem aside in the past by telling people
>> they could just retry their transaction ... but why don't we make the
>> database do the retrying?  I'm envisioning something like the attached
>> quick-hack, which arranges that the pg_class and pg_type rows for tables
>> will never be given OIDs duplicating an existing entry.

> I'd like to suggest that we backpatch this to 7.3 at least.

Considering we don't even have code to do this, much less have expended
one day of beta testing on it, back-patching seems a bit premature.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Mark Woodward"
Date:
Subject: Re: shrinking the postgresql.conf
Next
From: Tom Lane
Date:
Subject: Re: #escape_string_warning = off