From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Does export operation cancel SQLs? |
Date: | 2025-02-19 16:03:41 |
Message-ID: | 2018443.1739981021@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Ron Johnson <ronljohnsonjr(at)gmail(dot)com> writes:
> On Wed, Feb 19, 2025 at 10:00 AM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
> wrote:
>> No, that message is from a cancel request, like when you interrupt your
>> currently running query with Ctrl+C in "psql" or invoke
>> pg_cancel_backend().
>> PostgreSQL doesn't do that by itself.
> The Linux oom killer? I don't remember the exact error message that PG
> gives to the user, but ISTR that it's "user request”.
No, the OOM killer does "kill -9", which stops the PG process in
its tracks. So no message at all will be issued. You'll get
some kind of "connection lost" message from the connected client,
but for sure that is not going to claim it was a "user request".
I do seem to recall that there are some edge cases where we can't
really tell the source of a SIGINT signal, but there's no reason
to think that any of those cases are in play here. The OP should
be looking first at the other moving parts in his installation
to see what might be issuing a query cancel.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2025-02-19 16:07:43 | Re: Does export operation cancel SQLs? |
Previous Message | Álvaro Herrera | 2025-02-19 15:54:03 | Re: In-place upgrade with streaming replicas |