From: | Luca Ferrari <fluca1978(at)gmail(dot)com> |
---|---|
To: | Arni <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 12:46:26 |
Message-ID: | CAKoxK+5aAp9OEKbjRuaMQP65xwtg5rOpYgBYj-JLsuhLsXNfiA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Thu, Aug 8, 2019 at 2:21 PM Arni <Arni(dot)Kromic(at)bios-ict(dot)hr> wrote:
> This works! I get:
> oid | nspname
> -------+--------------------
> 16385 | HR16101766338-2018
> (1 row)
>
> I get the same thing if I try with '%HR16101766338-2018'. So it seems as
> if there were some characters prepended to the name... I've checked for
> spaces, but there are none. What could this mean?
>
Can you inspect output of
SELECT oid, nspname, quote_ident( nspname ) FROM pg_namespace WHERE
nspname = '%HR1610%'
and see if there's a character provoking this (could it need to be
redirect to a file and inspect with an editor).
I suspect this is the problem why your schema cannot be "named" as it is.
On a desperate approach, I would try to update pg_namespace to force
the naming of such schema, but I don't tend to work against the
catalog in production...and since you don't seem to have a backup I
would do a few more experiments first.
Luca
From | Date | Subject | |
---|---|---|---|
Next Message | Arni | 2019-08-08 14:08:38 | Re: Problem with schemas, possibly oids? |
Previous Message | Ron | 2019-08-08 12:41:50 | Re: Problem with schemas, possibly oids? |