From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
---|---|
To: | wolakk(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #17530: pg_dump comment on triggers is "off" by comparison to all of the other objects... |
Date: | 2022-06-23 04:11:01 |
Message-ID: | 20220623041101.yuhz6euhtekectkt@jrouhaud |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Hi,
On Wed, Jun 22, 2022 at 11:05:45PM +0000, PG Bug reporting form wrote:
> 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"
That's expected, the name in the comment has a qualifier when the object name
itself isn't guaranteed to be unique, with the format
"$table_name $trigger_name"
This is done similarly for all object types that don't have a guarantee of
unique name (policies, rules...).
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2022-06-23 04:27:25 | Re: BUG #17530: pg_dump comment on triggers is "off" by comparison to all of the other objects... |
Previous Message | David G. Johnston | 2022-06-23 04:02:01 | Re: BUG #17530: pg_dump comment on triggers is "off" by comparison to all of the other objects... |