Skip site navigation (1) Skip section navigation (2)

Re: obj_unique_identifier(oid)

From: Joel Jacobson <joel(at)gluefinance(dot)com>
To: Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Jim Nasby <jim(at)nasby(dot)net>, Herrera Alvaro <alvherre(at)commandprompt(dot)com>, pgsql-hackers Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: obj_unique_identifier(oid)
Date: 2011-01-08 13:05:17
Message-ID: AANLkTin6a26dn1J7WREsc9vsQKp+d5OLwnvNwST2wfvT@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
2011/1/8 Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>:
>  http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=6cc2deb86e9183262493a6537700ee305fb3e096

Nice! Has the patch been accepted and will be made available in future
versions of pg?

Also, why return NULL for pinned objects? They can also be described
using a unique identifier.
(+   /* for "pinned" items in pg_depend, return null */)

It is useful to describe such objects to be able to diff different
versions of pg, i.e. comparing which pinned objects exists, doing so
can tell you the odds for an application depending on certain pinned
objects being compatible with a specific version of the database.

-- 
Best regards,

Joel Jacobson
Glue Finance

In response to

Responses

pgsql-hackers by date

Next:From: Stephen FrostDate: 2011-01-08 13:14:19
Subject: Re: DISCARD ALL ; stored procedures
Previous:From: Marko TiikkajaDate: 2011-01-08 12:50:39
Subject: Re: join functions

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group