|From:||PG Bug reporting form <noreply(at)postgresql(dot)org>|
|Subject:||BUG #15440: pg_dump does not preserve quoted identifiers for statement-level trigger transition table names|
|Views:||Raw Message | Whole Thread | Download mbox|
The following bug has been logged on the website:
Bug reference: 15440
Logged by: Karl Czajkowski
Email address: karlcz(at)isi(dot)edu
PostgreSQL version: 10.5
Operating system: Linux
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
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
|Next Message||Amit Langote||2018-10-19 03:45:33||Re: BUG #15437: Segfault during insert into declarative partitioned table with a trigger creating partition|
|Previous Message||Tom Lane||2018-10-19 02:52:51||Re: BUG #15437: Segfault during insert into declarative partitioned table with a trigger creating partition|