agora inbox for pgsql-admin@postgresql.org
help / color / mirror / Atom feedFrom: shammat@gmx.net
To: pgsql-admin@lists.postgresql.org
Subject: Re: Does export operation cancel SQLs?
Date: Wed, 19 Feb 2025 12:10:13 +0100
Message-ID: <40fe637f-d3a1-4af5-b100-2e7fedca72bd@gmx.net> (raw)
In-Reply-To: <33a7cbf8b9a5bd90aa2797a1fca3f12e421639cd.camel@cybertec.at>
References: <CAC5iy62t+KuBZJGLjDQ54w6QyELZZyPisacuKvW+KT_+UomPfw@mail.gmail.com>
<33a7cbf8b9a5bd90aa2797a1fca3f12e421639cd.camel@cybertec.at>
Laurenz Albe schrieb am 19.02.2025 um 09:43:
>> 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.
>
> I am not sure what exactly you mean by "export". A pg_dump?
> But I am not aware of any operation that would cancel statements in other
> sessions. Perhaps someone or something in your application sends cancel
> requests when a statement is running too long, and the concurrent export
> slows down the system.
What if the "export" is done on a read-only replica?
Could this be a "canceling statement due to conflict with recovery" in disguise?
view thread (17+ messages) latest in thread
Message-ID: <40fe637f-d3a1-4af5-b100-2e7fedca72bd@gmx.net>
Permalink: ../40fe637f-d3a1-4af5-b100-2e7fedca72bd@gmx.net/
Also on: postgresql.org/message-id/40fe637f-d3a1-4af5-b100-2e7fedca72bd@gmx.net
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: shammat@gmx.net, pgsql-admin@lists.postgresql.org
Subject: Re: Does export operation cancel SQLs?
In-Reply-To: <40fe637f-d3a1-4af5-b100-2e7fedca72bd@gmx.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox