Re: Solving the OID-collision problem

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Solving the OID-collision problem
Date: 2005-08-08 20:55:37
Message-ID: 9081.1123534537@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Simon Riggs <simon(at)2ndquadrant(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-08-08 20:57:17 Re: #escape_string_warning = off
Previous Message Marko Kreen 2005-08-08 20:34:57 Re: Simplifying wal_sync_method