Re: Primary key error in INFORMATION_SCHEMA views - Mailing list pgsql-bugs

From Vik Fearing
Subject Re: Primary key error in INFORMATION_SCHEMA views
Date
Msg-id 7febd786-dccc-0681-36fa-6bdbd00f29ba@2ndquadrant.com
Whole thread Raw
In response to Re: Primary key error in INFORMATION_SCHEMA views  (SQLpro <sqlpro@sqlspot.com>)
List pgsql-bugs
On 24/05/18 10:01, SQLpro wrote:
> Hi Tom,
> 
> For a DBMS which loudly proclaims to be the most respectful of the SQL
> standard, not being able to use the INFORMATION_SCHEMA views because of such
> an error seems to me to go against its philosophy.
> 
> Can not you change that by adding a configuration parameter, for a future
> version, that would allow you to apply these views more strictly?

No, we cannot.  Table inheritance matches constraints based on name, and
inherited tables are often in the same schema as the parent.
-- 
Vik Fearing                                          +33 6 46 75 15 36
http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support


pgsql-bugs by date:

Previous
From: "Sve@r"
Date:
Subject: Re: Primary key error in INFORMATION_SCHEMA views
Next
From: PG Bug reporting form
Date:
Subject: BUG #15212: Default values in partition tables don't work as expectedand allow NOT NULL violation