Re: Problem with schemas, possibly oids?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Arni Kromić <Arni(dot)Kromic(at)Bios-ICT(dot)hr>
Cc: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: Problem with schemas, possibly oids?
Date: 2019-08-08 14:25:02
Message-ID: 19010.1565274302@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

=?UTF-8?Q?Arni_Kromi=c4=87?= <Arni(dot)Kromic(at)Bios-ICT(dot)hr> writes:
> We're using the clone_schema function from a postgres mailing list
> (converted to a procedure now) to create new schemas from a template,
> and so far we have created about 170 schemas that way. Now we have
> encountered a problem which prevents us from creating new schemas:

> CALL clone_schema('klijent_tpl', 'test-2019')
> Although this has worked perfectly until now, the call results in this
> error:
>> ERROR: relation "test-2019.bc_mob_pr_pnd" does not exist

> Moreover, trying to clone some of the existing schemas also fails:
> call clone_schema ('HR16101766338-2018', 'test')
>> NOTICE: source schema HR16101766338-2018 does not exist!
> The source schema DOES exist.

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.

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Luca Ferrari 2019-08-08 14:38:40 Re: Problem with schemas, possibly oids?
Previous Message Arni 2019-08-08 14:08:38 Re: Problem with schemas, possibly oids?