Search Postgresql Archives

Re: information_schema.referential_constraints broken?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Igor Neyman <ineyman@xxxxxxxxxxxxxx> writes:
> Answering my own question.
> Replacing original definition of _pg_keysequal (in information_schema):

> CREATE FUNCTION _pg_keysequal(smallint[], smallint[]) RETURNS boolean
>     LANGUAGE sql IMMUTABLE  -- intentionally not STRICT, to allow inlining
>     AS 'select $1 <@ $2 and $2 <@ $1';

> with this one:

> CREATE FUNCTION _pg_keysequal(smallint[], smallint[]) RETURNS boolean
>     LANGUAGE sql IMMUTABLE  -- intentionally not STRICT, to allow inlining
>     AS 'select $1 operator(pg_catalog.<@) $2 and $2 operator(pg_catalog.<@) $1';

> makes queries like:
> select * from information_schema.referential_constraints;
> against information_schema.referential_constraints work without errors.

This is known to happen pre-9.0 if you have contrib/intarray installed.

			regards, tom lane

-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux