Re: Making C function declaration parameter names consistent with corresponding definition names - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Making C function declaration parameter names consistent with corresponding definition names
Date
Msg-id CAH2-WznupXdh8hZ4cjr7nVVHHPLP3w46AcKb2QXYWsPUp6LQ_A@mail.gmail.com
Whole thread Raw
In response to Re: Making C function declaration parameter names consistent with corresponding definition names  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: Making C function declaration parameter names consistent with corresponding definition names
List pgsql-hackers
On Tue, Sep 20, 2022 at 1:51 PM Peter Geoghegan <pg@bowt.ie> wrote:
> I pushed much of this just now. All that remains to bring the entire
> codebase into compliance is the ecpg patch and the pg_dump patch.
> Those two areas are relatively tricky. But it's now unlikely that I'll
> need to push a commit that makes relatively many CF patches stop
> applying against HEAD -- that part is over.

Attached revision shows where I'm at with this. Would be nice to get
it all out of the way before too long.

Turns out that we'll need a new patch for contrib, which was missed
before now due to an issue with how I build a compilation database
using bear [1]. The new patch for contrib isn't very different to the
other patches, though. The most notable changes are in pgcrypto and
oid2name. Fairly minor stuff, overall.

[1] https://github.com/rizsotto/Bear
-- 
Peter Geoghegan

Attachment

pgsql-hackers by date:

Previous
From: Bharath Rupireddy
Date:
Subject: Re: pg_receivewal fail to streams when the partial file to write is not fully initialized present in the wal receiver directory
Next
From: Amit Kapila
Date:
Subject: Re: why can't a table be part of the same publication as its schema