Subject: Re: Problem with schemas, possibly oids?
To: pgsql-admin@lists.postgresql.org
References: <3cabefc3-0713-7f5d-27c5-c0dab55cd8c6@Bios-ICT.hr>
 <edfcd4d6-2db5-1ee2-f995-f6ac927b3100@gmail.com>
 <39dd43b7-8c8a-53c4-5a0b-545e66c10bad@Bios-ICT.hr>
 <66506893-a4c9-ea43-24a5-e9c1decff93a@gmail.com>
 <0bc785cb-3849-3fcf-50c2-19baff549fcf@Bios-ICT.hr>
From: Ron <ronljohnsonjr@gmail.com>
Message-ID: <380adff2-071b-96af-ed75-57da4145de89@gmail.com>
Date: Thu, 8 Aug 2019 07:41:50 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <0bc785cb-3849-3fcf-50c2-19baff549fcf@Bios-ICT.hr>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Precedence: bulk

On 8/8/19 7:39 AM, Arni wrote:
> On 08/08/2019 14.33, Ron wrote:
>> On 8/8/19 7:30 AM, Arni wrote:
>>> Thank you for the response.
>>>
>>> On 08/08/2019 14.14, Ron wrote:
>>>> On 8/8/19 4:04 AM, Arni Kromić wrote:
>>>>> ...snip...
>>>> Maybe there's a bug in clone_schema or it's wants some assumptions
>>>> that you aren't fulfilling.
>>> I'm not sure, but clone_schema has been successfully used to create
>>> about 170 new schemas before this...
>> I also mentioned "or it's wants some assumptions that you aren't
>> fulfilling" (which can also be considered a bug).
>>
> So far I can't identify anything like that. Also considering that it has
> worked flawlessly until now and that some other quirks (like PGAdmin's
> message) have occured, I believe the culprit might be somewhere else in
> the database...

Which is why I suggested, "What if you manually execute the contents 
ofclone_schema to generate DDL and then run that DDL?"  Then you might find 
where the problem is.


-- 
Angular momentum makes the world go 'round.