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

From Amit Langote
Subject Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping apartition table
Date
Msg-id CA+HiwqHz2AbSoZb8v6NzkPuwuoJF1Kzmq_A65aDoMxe3egJOkQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping apartition table  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-bugs
On Thu, Apr 25, 2019 at 10:46 PM Alvaro Herrera
<alvherre@2ndquadrant.com> wrote:
> 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.

Oops, will do.  Thanks.

Regards,
Amit



pgsql-bugs by date:

Previous
From: Sergei Kornilov
Date:
Subject: Re: BUG #15781: subselect on foreign table (postgres_fdw) can crash (segfault)
Next
From: Tom Lane
Date:
Subject: Re: BUG #15781: subselect on foreign table (postgres_fdw) can crash (segfault)