| From: | Jeff Frost <jeff(at)pgexperts(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15299: relation does not exist errors |
| Date: | 2018-07-26 20:53:00 |
| Message-ID: | 039A9034-96E6-4FF3-AB82-9E24C2F89B32@pgexperts.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Jul 26, 2018, at 1:23 PM, Andres Freund <andres(at)anarazel(dot)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're complete 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 doing it. I'll go spelunking there next!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-07-26 21:04:26 | Re: BUG #15300: "do you want the application "postgres" to accept incoming network connections" dialog box madness |
| Previous Message | PG Bug reporting form | 2018-07-26 20:42:35 | BUG #15301: Scanning all partition when more than 100 items in "where id in ()" clause |