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 f=
irst execution, but something is improper on subsequent executions.=20

> On Nov 1, 2016, at 5:00 PM, David G. Johnston <david.g.johnston@gmail.com>=
 wrote:
>=20
>> On Tue, Nov 1, 2016 at 12:26 PM, <vcolborn@gmail.com> wrote:
>=20
>> The following bug has been logged on the website:
>>=20
>> Bug reference:      14408
>> Logged by:          Victor Colborn
>> Email address:      vcolborn@gmail.com
>> PostgreSQL version: 9.6.1
>> Operating system:   (Red Hat 4.4.7-16), 64-bit
>> Description:
>>=20
>> I'm finding that this rather simple postgresql 9.6.1 function
>> =E2=80=8B[...]
>>=20
>> is resulting in a schema "" does not exist error. The exact error is:
>>=20
>> =E2=80=8B[...]
>>=20
>> and occurs reliably on the second and subsequent executions. Cut/Pasting t=
he
>> above SQL chunk reproduces the error...for me. Quite interested if that's=

>> not the case elsewhere. I have the following clues:
> =E2=80=8B[...]=E2=80=8B=20
>> 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.
>=20
> =E2=80=8BMy gut reaction here is to type, by hand, the CREATE FUNCTION cod=
e into a newly created text file and send it through psql.  Your comment abo=
ut copy/paste and "non-visible characters" leads me to suspect that whatever=
 source you are copying from has been "poisoned" by a control character=E2=80=
=8B that you can't see and that is causing a problem.
>=20
> David J.
>=20
>=20