Re: Revert back to standard AC_STRUCT_TIMEZONE Autoconf macro

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Revert back to standard AC_STRUCT_TIMEZONE Autoconf macro
Date: 2019-09-30 19:36:11
Message-ID: 23927.1569872171@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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. If we could get
rid of that configure macro altogether, we could remove some dubious
junk like plpython.h's "#undef HAVE_TZNAME".

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2019-09-30 19:54:28 Re: Connections hang indefinitely while taking a gin index's LWLock buffer_content lock(PG10.7)
Previous Message Peter Geoghegan 2019-09-30 19:25:02 Re: Connections hang indefinitely while taking a gin index's LWLock buffer_content lock(PG10.7)