From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Making C function declaration parameter names consistent with corresponding definition names |
Date: | 2022-09-17 18:36:48 |
Message-ID: | CAH2-WzkgcxqbudmwwCREpkapnOt_svG8M+HWTPkUTv-VMmNsXQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Sep 17, 2022 at 11:26 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Yeah, bringing the regex code into line with our standards is fine.
> I don't really see a reason not to do it with the timezone code
> either, as long as there aren't too many changes there. We are
> carrying a pretty large number of diffs from upstream already.
I'd be surprised if this created more than 3 minutes of extra work for
you when updating the timezone code.
There are a few places where I had to apply a certain amount of
subjective judgement (rather than just mechanically normalizing the
declarations), but the timezone code wasn't one of those places. Plus
there just isn't that many affected timezone related function
declarations, and they're concentrated in only 3 distinct areas.
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2022-09-17 18:37:01 | Re: missing indexes in indexlist with partitioned tables |
Previous Message | Tom Lane | 2022-09-17 18:26:25 | Re: Making C function declaration parameter names consistent with corresponding definition names |