Re: obj_unique_identifier(oid)

From: Joel Jacobson <joel(at)gluefinance(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: obj_unique_identifier(oid)
Date: 2011-01-07 19:57:34
Message-ID: 5552680124847797655@unknownmsgid
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Sent from my iPhone

On 7 jan 2011, at 20:46, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Joel Jacobson <joel(at)gluefinance(dot)com> writes:
>> The function obj_unique_identifier(oid) will return a unique name for _any_ oid.
>
> Surely this is broken by design? You can *not* assume that the same OID
> isn't in use for different things in different system catalogs. They're
> only guaranteed unique within a catalog. That's the main reason why
> pg_depend has to include the classid.
>
> regards, tom lane

Correct. That is why the regclass name (classid) is included in the unique name.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joel Jacobson 2011-01-07 19:59:09 Re: obj_unique_identifier(oid)
Previous Message Jim Nasby 2011-01-07 19:56:12 Re: estimating # of distinct values