Re: Make query cancellation keys longer

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Cc: Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, Robert Haas <robertmhaas(at)gmail(dot)com>, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Subject: Re: Make query cancellation keys longer
Date: 2025-04-03 11:29:21
Message-ID: 70145721-6949-4ABF-BB54-63F866488DF8@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 2 Apr 2025, at 15:48, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:

> And committed, with minor a bunch more little cleanups.

0001 in commit 09be39112654 seems to have missed (omitted?) adding the HAVE_
macros to pg_config.h.in, which doesn't matter as of now since they're not used
but it will be in the way for anyone running autoheader. Any objection to me
pushing the attached?

--
Daniel Gustafsson

Attachment Content-Type Size
timingsafe.diff application/octet-stream 795 bytes

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2025-04-03 11:30:08 Re: two occurrences of assign print_notnull within pg_dump.c
Previous Message Ashutosh Bapat 2025-04-03 11:22:08 Re: two occurrences of assign print_notnull within pg_dump.c