Re: Weird failures on lorikeet

On 6/25/20 12:52 PM, Alvaro Herrera wrote:
> Is there something going on with lorikeet again?  I see this:
>
> 2020-06-25 01:55:13.380 EDT [5ef43c40.21e0:85] pg_regress/typed_table LOG:  statement: SELECT
c.oid::pg_catalog.regclass
>     FROM pg_catalog.pg_class c, pg_catalog.pg_inherits i
>     WHERE c.oid = i.inhparent AND i.inhrelid = '21420'
>       AND c.relkind != 'p' AND c.relkind != 'I'
>     ORDER BY inhseqno;
> *** starting debugger for pid 4456, tid 2644
> 2020-06-25 01:55:13.393 EDT [5ef43c40.21e0:86] pg_regress/typed_table LOG:  statement: SELECT
c.oid::pg_catalog.regclass,c.relkind, pg_catalog.pg_get_expr(c.relpartbound, c.oid)
 
>     FROM pg_catalog.pg_class c, pg_catalog.pg_inherits i
>     WHERE c.oid = i.inhrelid AND i.inhparent = '21420'
>     ORDER BY pg_catalog.pg_get_expr(c.relpartbound, c.oid) = 'DEFAULT', c.oid::pg_catalog.regclass::pg_catalog.text;
>       1 [main] postgres 4456 try_to_debug: Failed to start debugger, Win32 error 2
> 2020-06-25 01:55:13.455 EDT [5ef43c40.21e0:87] pg_regress/typed_table LOG:  statement: CREATE TABLE persons3 OF
person_type(
 
>         PRIMARY KEY (id),
>         name NOT NULL DEFAULT ''
>     );
> *** continuing pid 4456 from debugger call (0)
> *** starting debugger for pid 4456, tid 2644
>   48849 [main] postgres 4456 try_to_debug: Failed to start debugger, Win32 error 2
> *** continuing pid 4456 from debugger call (0)
> 2020-06-25 01:55:18.181 EDT [5ef43bd6.2824:4] LOG:  server process (PID 4456) was terminated by signal 11:
Segmentationfault
 
> 2020-06-25 01:55:18.181 EDT [5ef43bd6.2824:5] DETAIL:  Failed process was running: drop table some_tab cascade;
>


I don't know what that's about. I'll reboot the machine presently and
see if it persists.


cheers


andrew


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