Re: BUG #14408: Schema not found error when 2 or more indices declared on temporary table

Good suggestion David. Tried that to no resolve. I am getting a successful first execution, but something is improper on subsequent executions.

> On Nov 1, 2016, at 5:00 PM, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
>> On Tue, Nov 1, 2016 at 12:26 PM, <vcolborn(at)gmail(dot)com> wrote:
>
>> The following bug has been logged on the website:
>>
>> Bug reference: 14408
>> Logged by: Victor Colborn
>> Email address: vcolborn(at)gmail(dot)com
>> PostgreSQL version: 9.6.1
>> Operating system: (Red Hat 4.4.7-16), 64-bit
>> Description:
>>
>> I'm finding that this rather simple postgresql 9.6.1 function
>> ​[...]
>>
>> is resulting in a schema "" does not exist error. The exact error is:
>>
>> ​[...]
>>
>> and occurs reliably on the second and subsequent executions. Cut/Pasting the
>> above SQL chunk reproduces the error...for me. Quite interested if that's
>> not the case elsewhere. I have the following clues:
> ​[...]​
>> It indicates the name of the not found schema to be "" or "0MA{Start of
>> Text} " or some similar variant with non-visible character values.
>
> ​My gut reaction here is to type, by hand, the CREATE FUNCTION code into a newly created text file and send it through psql. Your comment about copy/paste and "non-visible characters" leads me to suspect that whatever source you are copying from has been "poisoned" by a control character​ that you can't see and that is causing a problem.
>
> David J.
>
>