pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: wolakk@gmail.com
Subject: BUG #17530: pg_dump comment on triggers is "off" by comparison to all of the other objects...
Date: Wed, 22 Jun 2022 23:05:45 +0000
Message-ID: <17530-a13411896e59c64a@postgresql.org> (raw)

The following bug has been logged on the website:

Bug reference:      17530
Logged by:          Kirk Wolak
Email address:      wolakk@gmail.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"();



view thread (5+ messages)  latest in thread

Message-ID: <17530-a13411896e59c64a@postgresql.org>
Permalink:  ../17530-a13411896e59c64a@postgresql.org/
Also on:    postgresql.org/message-id/17530-a13411896e59c64a@postgresql.org

 · 

reply

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-bugs@postgresql.org
  Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, wolakk@gmail.com
  Subject: Re: BUG #17530: pg_dump comment on triggers is "off" by comparison to all of the other objects...
  In-Reply-To: <17530-a13411896e59c64a@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