Re: BUG #15299: relation does not exist errors - Mailing list pgsql-bugs

From Jeff Frost
Subject Re: BUG #15299: relation does not exist errors
Date
Msg-id 039A9034-96E6-4FF3-AB82-9E24C2F89B32@pgexperts.com
Whole thread Raw
In response to Re: BUG #15299: relation does not exist errors  (Andres Freund <andres@anarazel.de>)
Responses Re: BUG #15299: relation does not exist errors  (Jeff Frost <jeff@pgexperts.com>)
List pgsql-bugs
On Jul 26, 2018, at 1:23 PM, Andres Freund <andres@anarazel.de> wrote:
>
> On 2018-07-26 13:18:33 -0700, Jeff Frost wrote:
>> Oh, I see what you're saying. Don't the autovacuum processes connect to their own backends which then exit after
they'recomplete though? 
>
> Yes, that's right.  Creating an extension or calling a function that
> internally does a SET search_path seem like a more likely cause.

I grepped our code and didn't find anywhere that we set search_path, though it's possible some ruby gem we use could be
doingit. I'll go spelunking there next! 

pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #15301: Scanning all partition when more than 100 items in "whereid in ()" clause
Next
From: Tom Lane
Date:
Subject: Re: BUG #15300: "do you want the application "postgres" to accept incoming network connections" dialog box madness