=?UTF-8?Q?Arni_Kromi=c4=87?= <Arni.Kromic@xxxxxxxxxxx> 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