BUG #17530: pg_dump comment on triggers is "off" by comparison to all of the other objects...

Поиск
Список
Период
Сортировка
От PG Bug reporting form
Тема BUG #17530: pg_dump comment on triggers is "off" by comparison to all of the other objects...
Дата
Msg-id 17530-a13411896e59c64a@postgresql.org
обсуждение исходный текст
Ответы Re: BUG #17530: pg_dump comment on triggers is "off" by comparison to all of the other objects...  ("David G. Johnston" <david.g.johnston@gmail.com>)
Re: BUG #17530: pg_dump comment on triggers is "off" by comparison to all of the other objects...  (Julien Rouhaud <rjuju123@gmail.com>)
Список pgsql-bugs
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"();


В списке pgsql-bugs по дате отправления:

Предыдущее
От: Kevin Wolf
Дата:
Сообщение: Re: BUG #17529: SQL Error [57P01]: FATAL: terminating connection due to administrator command
Следующее
От: Masahiko Sawada
Дата:
Сообщение: Re: Postgres do not allow to create many tables with more than 63-symbols prefix