Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping apartition table - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping apartition table
Date
Msg-id 20190425134623.GA26586@alvherre.pgsql
Whole thread Raw
In response to Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping apartition table  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Responses Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping apartition table  (Amit Langote <amitlangote09@gmail.com>)
Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping apartition table  (Amit Langote <amitlangote09@gmail.com>)
List pgsql-bugs
Haven't read the patch, but I tried applying it on top of my tablespace
fixing patch ... and my first report is that this query in regress fails
(three times):

 select conname, obj_description(oid, 'pg_constraint') from pg_constraint where conname = 'c_chk' order by 1, 2;
  conname |            obj_description            
 ---------+---------------------------------------
+ c_chk   | alttype_cleanup_idx check constraint
  c_chk   | alttype_cleanup_idx1 check constraint
  c_chk   | alttype_cleanup_idx2 check constraint
- c_chk   | alttype_cleanup_idx check constraint
 (3 rows)

I think you should use 'ORDER BY 2 COLLATE "C"' to avoid the problem.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #15781: subselect on foreign table (postgres_fdw) can crash (segfault)
Next
From: Tom Lane
Date:
Subject: Re: CREATE SUBSCRIPTION fails with long passwords