Re: Revert back to standard AC_STRUCT_TIMEZONE Autoconf macro

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Revert back to standard AC_STRUCT_TIMEZONE Autoconf macro
Date: 2019-10-02 05:30:43
Message-ID: 9039c68e-98e1-6dbd-d70e-591e46e49d37@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2019-09-30 21:36, Tom Lane wrote:
> Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
>> Instead of AC_STRUCT_TIMEZONE we use our own variant called
>> PGAC_STRUCT_TIMEZONE that checks for tzname even if other variants were
>> found first. But since 63bd0db12199c5df043e1dea0f2b574f622b3a4c we
>> don't use tzname anymore, so we don't need this anymore.
>
> Hmm. I wonder if we need AC_STRUCT_TIMEZONE either? Seems like
> we should only be using our own struct pg_tm.

There are a few places that seem to need it, such as initdb/findtimezone.c.

> If we could get
> rid of that configure macro altogether, we could remove some dubious
> junk like plpython.h's "#undef HAVE_TZNAME".

We could keep just the part of AC_STRUCT_TIMEZONE that we need, namely
the check for tm_zone, and remove the part about tzname.

New patch attached.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Attachment Content-Type Size
v2-0001-Remove-use-of-deprecated-Autoconf-define.patch text/plain 2.8 KB
v2-0002-Simplify-PGAC_STRUCT_TIMEZONE-Autoconf-macro.patch text/plain 7.0 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Yuya Watari 2019-10-02 06:56:07 Re: Keep compiler silence (clang 10, implicit conversion from 'long' to 'double' )
Previous Message higuchi.daisuke@fujitsu.com 2019-10-02 04:10:43 [Bug fix] ECPG: ECPG preprocessor outputs "unsupported feature will be passed to server" even if the command is supported