Re: New Object Access Type hooks - Mailing list pgsql-hackers

From Tom Lane
Subject Re: New Object Access Type hooks
Date
Msg-id 1925660.1649095626@sss.pgh.pa.us
Whole thread Raw
In response to Re: New Object Access Type hooks  (Mark Dilger <mark.dilger@enterprisedb.com>)
Responses Re: New Object Access Type hooks
List pgsql-hackers
Mark Dilger <mark.dilger@enterprisedb.com> writes:
> The test logs are attached.

Server log looks as-expected:

2022-04-04 09:11:51.087 PDT [2084] 013_crash_restart.pl LOG:  statement: SELECT pg_sleep(3600);
2022-04-04 09:11:51.094 PDT [2083] 013_crash_restart.pl WARNING:  terminating connection because of unexpected SIGQUIT
signal
2022-04-04 09:11:51.095 PDT [2070] LOG:  server process (PID 2083) exited with exit code 2
2022-04-04 09:11:51.095 PDT [2070] DETAIL:  Failed process was running: INSERT INTO alive
VALUES($$in-progress-before-sigquit$$)RETURNING status; 
2022-04-04 09:11:51.095 PDT [2070] LOG:  terminating any other active server processes

I was hoping to see regress_log_013_crash_restart, though.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Mark Dilger
Date:
Subject: Re: New Object Access Type hooks
Next
From: Mark Dilger
Date:
Subject: Re: New Object Access Type hooks