Re: BUG #15684: Server crash on DROP partitioned table

Hi,

On Sun, Mar 10, 2019 at 7:55 PM PG Bug reporting form
<noreply@postgresql.org> wrote:
>
> The following query:
> create table at_partitioned (a int, b text) partition by range (a);
> create table at_part_1 partition of at_partitioned for values from (0) to
> (1000);
> create table at_part_2 partition of at_partitioned for values from (1000) to
> (2000);
> create index on at_partitioned (b);
> alter table at_partitioned alter column b type numeric using b::numeric;
> alter table at_partitioned alter column b type numeric using b::numeric;
> drop table at_partitioned cascade;
>
> crashes server (on REL_11_2 and REL_11_STABLE) with the error messages:
> psql:query.sql:7: WARNING:  AbortTransaction while in COMMIT state
> psql:query.sql:7: ERROR:  SMgrRelation hashtable corrupted
> PANIC:  cannot abort transaction 575, it was already committed
> server closed the connection unexpectedly
>         This probably means the server terminated abnormally
>         before or while processing the request.
> psql:query.sql:7: connection to server was lost
>
> and the following stack trace:
> [...]

It seems to be the same bug as described in bug #15672
(https://www.postgresql.org/message-id/15672-b9fa7db32698269f@postgresql.org).
I'm Cc-ing Amit just in case.