Tom Lane <t...@sss.pgh.pa.us> writes:
> Joel Jacobson <j...@gluefinance.com> writes:
>> a) pg_describe_object should always include the schema in the name,
>> even for object in public and pg_catalog.
>
> I knew you were going to demand that next, as soon as you figured out
> that it was an obstacle for using pg_describe_object output as a
> globally unique identifier. But I'm going to reply, once again, that
> pg_describe_object is not meant to guarantee that and we're not going to
> make it so.
And it's easy to pretend it's already coded this way if you're motivated
enough. Just find a schema name that's not already existing:
dim=# set search_path to public, utils;
SET
dim=# select pg_describe_object('pg_proc'::regclass, 16602, 0);
pg_describe_object
---------------------------------------------------------------
function unaccent_lexize(internal,internal,internal,internal)
(1 row)
dim=# begin; create schema dummy; set local search_path to 'dummy'; select
pg_describe_object('pg_proc'::regclass, 16602, 0); rollback;
BEGIN
CREATE SCHEMA
SET
pg_describe_object
---------------------------------------------------------------------
function utils.unaccent_lexize(internal,internal,internal,internal)
(1 row)
ROLLBACK
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
