From: PG Doc comments form <noreply@postgresql.org>
To: pgsql-docs@lists.postgresql.org
Cc: jgiaco@fanatics.com
Subject: Reference tables in triggers are supported in 10
Date: Fri, 06 Sep 2019 14:47:39 +0000
Message-ID: <156778125989.1118.105251422157993558@wrigleys.postgresql.org> (raw)
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/10/infoschema-triggers.html
Description:
The documentation states the following:
action_reference_old_table sql_identifier Applies to a feature not available
in PostgreSQL
action_reference_new_table sql_identifier Applies to a feature not available
in PostgreSQL
action_reference_old_row sql_identifier Applies to a feature not available
in PostgreSQL
action_reference_new_row sql_identifier Applies to a feature not available
in PostgreSQL
...but REFERENCING OLD/NEW TABLE AS is valid in postgres 10. Why does the
infoschema not store this information. I believe this is causing issues in
3rd party tools (DataGrip specifically) that probably rely on
information_schema to generate triggers and omit this key information. I
dont think this is a documention bug as much as a bug in postgres not
storing the information in information_schema.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: noreply@postgresql.org, pgsql-docs@lists.postgresql.org, jgiaco@fanatics.com
Subject: Re: Reference tables in triggers are supported in 10
In-Reply-To: <156778125989.1118.105251422157993558@wrigleys.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox