Collected from the PG bugs email list.
|Reported by||Karl Czajkowski|
Body of first available message related to this bug follows.
The following bug has been logged on the website: Bug reference: 15440 Logged by: Karl Czajkowski Email address: (redacted) PostgreSQL version: 10.5 Operating system: Linux Description: If I create a statement-level trigger using quoted identifiers with the new transition table feature in pg10 and dump the database with pg_dump, the dumped CREATE TRIGGER statements lack quotes on the identifier. This prevents the database from properly round-tripping through dump and restore. The restored triggers will bind the unquoted identifier as the transition table names, and my trigger function will encounter errors when it uses an unknown relation. Using a simple "sed" filter to rewrite my dump file repairs the dump, since pg_dump did dump the proper mixed-case spelling of an identifier and only omitted the wrapping double-quotation marks. As an example, consider a create trigger clause like: ... REFERENCING OLD TABLE AS "_myapp_oldtuples_Mixed_Case" ... It appears in the dumped SQL as: ... REFERENCING OLD TABLE AS _myapp_oldtuples_Mixed_Case ...
|2018-10-19 03:16:52+00||=?utf-8?q?PG_Bug_reporting_form?=||BUG #15440: pg_dump does not preserve quoted identifiers for statement-level trigger transition table names|
|2018-10-19 04:35:01+00||Tom Lane||Re: BUG #15440: pg_dump does not preserve quoted identifiers for statement-level trigger transition table names|