| From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> | 
|---|---|
| To: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> | 
| Subject: | Re: Does export operation cancel SQLs? | 
| Date: | 2025-02-19 15:42:54 | 
| Message-ID: | CANzqJaAYzSi6zW_fGF8pO_r4Cc5DL8qEvQnBRreTV1KhjY65DQ@mail.gmail.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-admin | 
On Wed, Feb 19, 2025 at 10:00 AM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
wrote:
> On Wed, 2025-02-19 at 06:54 -0700, David G. Johnston wrote:
> > > We have PostgreSQL 16 running in GCP cloud SQL. When export job runs
> we are noticing these messages excessively:
> > >
> > > db=postgres,user=postgres ERROR:  canceling statement due to user
> request
> > >
> > > Does Export cancel the SQLs? If not, why are we noticing these
> messages excessively during the export operation? The load on the instance
> is minimal
> >
> > It says “user request”.  I’d advise figuring out what was cancelled and
> what “user” did so.
> > Probably DDL commands failing to get exclusive locks.
>
> 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”.  Had to search
through /var/log/messages to see that oomkiller was the culprit.
-- 
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Álvaro Herrera | 2025-02-19 15:54:03 | Re: In-place upgrade with streaming replicas | 
| Previous Message | Laurenz Albe | 2025-02-19 15:00:26 | Re: Does export operation cancel SQLs? |