| From: | Jim Nasby <jim(at)nasby(dot)net> |
|---|---|
| To: | Joel Jacobson <joel(at)gluefinance(dot)com>, Herrera Alvaro <alvherre(at)commandprompt(dot)com> |
| Cc: | pgsql-hackers Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: obj_unique_identifier(oid) |
| Date: | 2011-01-07 20:18:41 |
| Message-ID: | 3FFEEAAD-9BBE-4429-AF21-FD29A27F7A23@nasby.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Jan 7, 2011, at 1:46 PM, Tom Lane 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.
BTW, if you're looking at making pg_depnd easier to use, see http://archives.postgresql.org/message-id/1290000774-sup-2218@alvh.no-ip.org
--
Jim C. Nasby, Database Architect jim(at)nasby(dot)net
512.569.9461 (cell) http://jim.nasby.net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2011-01-07 20:34:55 | Re: system views for walsender activity |
| Previous Message | Joachim Wieland | 2011-01-07 20:18:26 | pg_dump directory archive format / parallel pg_dump |