| From: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
|---|---|
| To: | Dave Cramer <davecramer(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: function for testing that causes the backend to terminate |
| Date: | 2021-05-01 05:58:16 |
| Message-ID: | CALj2ACWm3_O-FXDpwrv047AgY=+TtP_mKiTExH=QbwxNK1OBeg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Apr 29, 2021 at 4:36 PM Bharath Rupireddy
<bharath(dot)rupireddyforpostgres(at)gmail(dot)com> wrote:
>
> On Thu, Apr 29, 2021 at 4:27 PM Dave Cramer <davecramer(at)gmail(dot)com> wrote:
> > For testing unusual situations I'd like to be able to cause a backend to terminate due to something like a segfault. Do we currently have this in testing ?
>
> Well, you could use pg_terminate_backend which sends SIGTERM to the
> backend. However, we don't have a function that sends SIGSEGV yet, you
> could signal the backend with SIGSEGV directly, if possible.
And, I came across an extension called pg_crash [1], see if that helps.
[1] https://www.cybertec-postgresql.com/en/pg_crash-crashing-postgresql-automatically/
With Regards,
Bharath Rupireddy.
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | vignesh C | 2021-05-01 07:19:42 | Re: Identify missing publications from publisher while create/alter subscription. |
| Previous Message | Dilip Kumar | 2021-05-01 05:17:25 | Re: Enhanced error message to include hint messages for redundant options error |