Horton

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

Alvaro Herrera <alvherre@2ndquadrant.com>

View thread View on postgr.es
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Amit Langote <amitlangote09@gmail.com>, Michael Paquier <michael@paquier.xyz>, jianingy.yang@gmail.com, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2019-04-25T13:46:23Z
Lists: pgsql-bugs, pgsql-hackers 
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

Commits

  1. Apply stopgap fix for bug #15672.