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

From: Victor Colborn <vcolborn(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14408: Schema not found error when 2 or more indices declared on temporary table
Date: 2016-11-01 23:06:10
Message-ID: CAM6VyYMPH9W8jVxSJG-OdCra2oHUUqK+65BgNiYFgkfCsY-gSQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

I'm able to reproduce on 9.5.3 as well.

Could it possibly related to a configuration setting (or some other common
attribute) I can review/alter?

Very much appreciate your time Tom.

On Tue, Nov 1, 2016 at 3:46 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> vcolborn(at)gmail(dot)com writes:
> > 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:
>
> Hm. The described symptoms sound quite a bit like an uninitialized-memory
> problem. However, I can't reproduce the problem here (using up-to-date
> RHEL6), nor does valgrind complain about this example for me.
>
> regards, tom lane
>

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David G. Johnston 2016-11-01 23:41:42 Re: BUG #14399: Order by id DESC causing bad query plan
Previous Message Tom Lane 2016-11-01 22:46:08 Re: BUG #14408: Schema not found error when 2 or more indices declared on temporary table