Re: Don't use the deprecated and insecure PQcancel in our frontend tools anymore

From: "Jelte Fennema-Nio" <postgres(at)jeltef(dot)nl>
To: "PostgreSQL Hackers" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "Alvaro Herrera" <alvherre(at)alvh(dot)no-ip(dot)org>, "Jacob Champion" <jacob(dot)champion(at)enterprisedb(dot)com>
Subject: Re: Don't use the deprecated and insecure PQcancel in our frontend tools anymore
Date: 2026-01-02 15:14:54
Message-ID: DFE79YWE1WMQ.3PW5S3JWD0LU1@jeltef.nl
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun Dec 14, 2025 at 3:40 PM CET, Jelte Fennema-Nio wrote:
> A bunch of frontend tools, including psql, still used PQcancel to send
> cancel requests to the server. That function is insecure, because it
> does not use encryption to send the cancel request. This starts using
> the new cancellation APIs (introduced in 61461a300) for all these
> frontend tools.

Fixed conflict after Copyright update.

Attachment Content-Type Size
v2-0001-Move-Windows-pthread-compatibility-functions-to-s.patch text/x-patch 2.9 KB
v2-0002-Don-t-use-the-deprecated-and-insecure-PQcancel-in.patch text/x-patch 33.2 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2026-01-02 15:21:41 Re: lsyscache: free IndexAmRoutine objects returned by GetIndexAmRoutineByAmId()
Previous Message zengman 2026-01-02 14:46:24 Re: [PATCH] aio: Refactor to deduplicate shared and local completion callbacks