Re: CURL_IGNORE_DEPRECATION

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
Cc: Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
Subject: Re: CURL_IGNORE_DEPRECATION
Date: 2025-11-11 14:04:12
Message-ID: E192D0D3-D454-452F-BA83-6B92D6DF6B3B@yesql.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 11 Nov 2025, at 12:41, Álvaro Herrera <alvherre(at)kurilemu(dot)de> wrote:

> Given that we use that macro in a single place,
> what do you think about removing that and making a more surgical
> intervention to fix pgindent problem with it? I propose the attached.

This proposal is a better solution than what was committed, +1.

> Of course, there's nothing we can do with
> CURL_IGNORE_DEPRECATION() itself, given that it's upstream from us.

Yup, sorry about that.

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Florin Irion 2025-11-11 14:10:27 Re: minor error message enhance: print RLS policy name when only one permissive policy exists
Previous Message Boris Mironov 2025-11-11 13:33:16 Idea to enhance pgbench by more modes to generate data (multi-TXNs, UNNEST, COPY BINARY)