| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "brandon(dot)m(dot)simmons(at)gmail(dot)com" <brandon(dot)m(dot)simmons(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #16912: pg_dump 11 does not respect --quote-all-identifiers within function bodies |
| Date: | 2021-03-04 15:01:46 |
| Message-ID: | CAKFQuwZ0hZXQGTYUJZTG7Lxp5SEgBOZ=iUD+8EnSfuJswKY8fg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wednesday, March 3, 2021, PG Bug reporting form <noreply(at)postgresql(dot)org>
wrote:
> The following bug has been logged on the website:
>
> Bug reference: 16912
> Logged by: Brandon Simmons
> Email address: brandon(dot)m(dot)simmons(at)gmail(dot)com
> PostgreSQL version: 11.11
> Operating system: Linux
> Description:
>
> I'm using regex to rewrite identifiers in a SQL dump and rely on the
> double-quotes.
> Within plpgsql `CREATE FUNCTION` statements in the resulting dump,
> identifiers are not quoted as I would expect.
>
PostgreSQL will not do anything to the text values in your database. A
function body is just plain text - that is why it gets surrounded with
single quotes or, more commonly, dollar-quoting, when written. It only has
meaning when interpreted during its execution.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brandon Simmons | 2021-03-04 15:14:35 | Re: BUG #16912: pg_dump 11 does not respect --quote-all-identifiers within function bodies |
| Previous Message | Vik Fearing | 2021-03-04 14:22:55 | Re: BUG #16913: GENERATED AS IDENTITY column nullability is affected by order of column properties |