From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
---|---|
To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Cc: | wolakk(at)gmail(dot)com |
Subject: | BUG #17530: pg_dump comment on triggers is "off" by comparison to all of the other objects... |
Date: | 2022-06-22 23:05:45 |
Message-ID: | 17530-a13411896e59c64a@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 17530
Logged by: Kirk Wolak
Email address: wolakk(at)gmail(dot)com
PostgreSQL version: 14.3
Operating system: Windows
Description:
I've been parsing through the file for our own system, and discovered the
Name: <value>
for the trigger is not quite the name of the trigger. I've included an
example of FUNCTIon for reference.
It's "change_log"<space>"id_change_log"; but the actual trigger name is
"id_change_log" on the table "change_log"
I would have EXPECTED $ as the function has, but that's part of it's "name"
in the function case.
PSQL Output Line:
Triggers:
id_change_log BEFORE INSERT ON logspc.change_log FOR EACH ROW WHEN
(new.id IS NULL) EXECUTE FUNCTION logspc."id_change_log$change_log"()
finally, it also "feels" like the 2 values are reversed, based on the PSQL
\d output line...
Basically, it's not the correct name. It should simply be "id_change_log"
(IMO, to be consistent with every other comment I've seen)
Thanks in advance...
--
-- Name: pkg_dilp_log_fix$do_log(text); Type: PROCEDURE; Schema: logspc;
Owner: postgres
--
CREATE PROCEDURE logspc."pkg_dilp_log_fix$do_log"(IN ijobtype text) ... ;
########### Issue is here:
--
-- Name: change_log id_change_log; Type: TRIGGER; Schema: logspc; Owner:
postgres
--
CREATE TRIGGER id_change_log BEFORE INSERT ON logspc.change_log FOR EACH ROW
WHEN ((new.id IS NULL)) EXECUTE FUNCTION
logspc."id_change_log$change_log"();
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Pryzby | 2022-06-22 23:58:45 | Re: pg_upgrade (12->14) fails on aggregate |
Previous Message | Kevin Wolf | 2022-06-22 20:46:09 | Re: BUG #17529: SQL Error [57P01]: FATAL: terminating connection due to administrator command |