pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedSection 40.1 Overview of Event Trigger Behavior, and Table 40.1 missing needed details
2+ messages / 2 participants
[nested] [flat]
* Section 40.1 Overview of Event Trigger Behavior, and Table 40.1 missing needed details
@ 2022-08-27 18:56 PG Doc comments form <noreply@postgresql.org>
0 siblings, 1 reply; 2+ messages in thread
From: PG Doc comments form @ 2022-08-27 18:56 UTC (permalink / raw)
To: pgsql-docs@lists.postgresql.org; +Cc: postgresql@nowisit.net
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/14/event-trigger-matrix.html
Description:
RE: https://www.postgresql.org/docs/current/event-trigger-matrix.html
Section 40.1. Overview of Event Trigger Behavior says:
"The table_rewrite event occurs just before a table is rewritten by some
actions of the commands ALTER TABLE and ALTER TYPE."
Issue: Neither the section nor the table describe which actions of ALTER
TABLE. If all actions fire the event trigger then section 40.1 should be
reworded to not suggest that some actions of ALTER table do not fire the
event trigger.
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: Section 40.1 Overview of Event Trigger Behavior, and Table 40.1 missing needed details
@ 2022-08-28 15:44 Alvaro Herrera <alvherre@alvh.no-ip.org>
parent: PG Doc comments form <noreply@postgresql.org>
0 siblings, 0 replies; 2+ messages in thread
From: Alvaro Herrera @ 2022-08-28 15:44 UTC (permalink / raw)
To: postgresql@nowisit.net; pgsql-docs@lists.postgresql.org
On 2022-Aug-27, PG Doc comments form wrote:
> Section 40.1. Overview of Event Trigger Behavior says:
> "The table_rewrite event occurs just before a table is rewritten by some
> actions of the commands ALTER TABLE and ALTER TYPE."
> Issue: Neither the section nor the table describe which actions of ALTER
> TABLE. If all actions fire the event trigger then section 40.1 should be
> reworded to not suggest that some actions of ALTER table do not fire the
> event trigger.
I don't follow. Not all actions fire that event trigger. Precisely the
point of that event trigger type is to allow you to programmatically
discover which actions do rewrite the table, without having to document
them exactly. Partly, the reason for this is that some actions can
avoid firing it under specific circumstances -- an example is SET DATA
TYPE, which most of the time does fire it, but it can be skipped in some
cases (say changing varchar(20) to varchar(40)).
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"Ellos andaban todos desnudos como su madre los parió, y también las mujeres,
aunque no vi más que una, harto moza, y todos los que yo vi eran todos
mancebos, que ninguno vi de edad de más de XXX años" (Cristóbal Colón)
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2022-08-28 15:44 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-08-27 18:56 Section 40.1 Overview of Event Trigger Behavior, and Table 40.1 missing needed details PG Doc comments form <noreply@postgresql.org>
2022-08-28 15:44 ` Alvaro Herrera <alvherre@alvh.no-ip.org>
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