| From: | Luca Ferrari <fluca1978(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Arni Kromić <Arni(dot)Kromic(at)bios-ict(dot)hr>, pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Problem with schemas, possibly oids? |
| Date: | 2019-08-08 14:38:40 |
| Message-ID: | CAKoxK+7XXr4rSNV8NRzPpj+pHMdfwTtzjMRRBBK+HWkKArTPxA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Thu, Aug 8, 2019 at 4:25 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Given that both of these troublesome schemas have dashes in their
> names, the most obvious theory is that clone_schema() has some
> oversight about double-quoting schema names everywhere necessary.
According to this implementation
<https://www.postgresql.org/message-id/CANu8FiyJtt-0q%3DbkUxyra66tHi6FFzgU8TqVR2aahseCBDDntA%40mail.gmail.com>
the first query is performed with quote_ident and that's the initial
failure. However, the original post claimed it has been converted from
a function to a procedure, so it could be the quote_ident part has
been removed.
What is the source of clone_schema?
Luca
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Arni | 2019-08-09 08:20:40 | Re: Problem with schemas, possibly oids? |
| Previous Message | Tom Lane | 2019-08-08 14:25:02 | Re: Problem with schemas, possibly oids? |