Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping a partition table

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>
Cc: Amit Langote <amitlangote09(at)gmail(dot)com>, jianingy(dot)yang(at)gmail(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping a partition table
Date: 2019-03-27 02:56:20
Message-ID: 20190327025620.GX2558@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Wed, Mar 27, 2019 at 11:40:12AM +0900, Amit Langote wrote:
> I'm thinking of adding this to open items under Older Bugs. Attached the
> patch that I had posted on -bugs, but it's only a rough sketch as
> described above, not a full fix.

Adding it to the section for older bugs sounds fine to me. Thanks for
doing so.
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Lars Vonk 2019-03-27 07:22:39 Re: BUG #15715: UPDATE using "in (subquery for update limit 1)" does not respect the limit in subquery
Previous Message Amit Langote 2019-03-27 02:40:12 Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping a partition table

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2019-03-27 03:04:14 Re: pg_malloc0() instead of pg_malloc()+memset()
Previous Message Amit Langote 2019-03-27 02:40:12 Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping a partition table