| From: | Vik Fearing <vik(dot)fearing(at)2ndquadrant(dot)com> |
|---|---|
| To: | SQLpro <sqlpro(at)sqlspot(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Primary key error in INFORMATION_SCHEMA views |
| Date: | 2018-05-25 21:45:58 |
| Message-ID: | 7febd786-dccc-0681-36fa-6bdbd00f29ba@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2018-05-28 00:30:21 | BUG #15212: Default values in partition tables don't work as expected and allow NOT NULL violation |
| Previous Message | Sve@r | 2018-05-25 20:51:11 | Re: Primary key error in INFORMATION_SCHEMA views |