Re: BUG #15350: Getting invalid cache ID: 11 Errors

From: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Kieran McCusker <kieran(dot)mccusker(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #15350: Getting invalid cache ID: 11 Errors
Date: 2018-09-20 02:25:36
Message-ID: CAEepm=0wOMxr-X9V-OH62ea0kZ810CkaVYnf-bbGUAdiR7Xgzg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Sep 19, 2018 at 6:10 PM Thomas Munro
<thomas(dot)munro(at)enterprisedb(dot)com> wrote:
> I would like to close this case, so unless anyone objects, tomorrow
> I'm going to push the reordering patch (0002 in my earlier email) so
> that we stop getting bug reports about extensions that crash in
> parallel workers (even though we consider those extensions to be
> operating out of contract). If someone wants to do a patch that will
> display warnings when extensions break that rule (something like the
> 0003 patch I sketched), that can be done separately.

Done.

--
Thomas Munro
http://www.enterprisedb.com

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message pcsuccess 2018-09-20 07:35:02 Getting "invalid cache ID: 42" in pg10.5
Previous Message Tom Lane 2018-09-19 20:18:38 Re: BUG #15383: Join Filter cost estimation problem in 10.5