Re: Server crash (FailedAssertion) due to catcache refcount mis-handling

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jeevan Chalke <jeevan(dot)chalke(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Server crash (FailedAssertion) due to catcache refcount mis-handling
Date: 2017-08-09 02:02:52
Message-ID: CA+TgmobhEYpK97hQuWs8v9Ypgvc=Pjoawk4C4Ue9QLt0zNKzxw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Aug 8, 2017 at 4:34 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> In the meantime, I think my vote would be to remove AtEOXact_CatCache.

In all supported branches?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2017-08-09 02:23:56 Re: Small code improvement for btree
Previous Message Peter Geoghegan 2017-08-09 01:33:07 Re: Possible issue with expanded object infrastructure on Postgres 9.6.1