Postgres Pro
Downloads
Home   >   mailing lists

Re: Revert back to standard AC_STRUCT_TIMEZONE Autoconf macro - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Revert back to standard AC_STRUCT_TIMEZONE Autoconf macro
Date
Msg-id 23927.1569872171@sss.pgh.pa.us
Whole thread Raw
In response to Revert back to standard AC_STRUCT_TIMEZONE Autoconf macro  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: Revert back to standard AC_STRUCT_TIMEZONE Autoconf macro
List pgsql-hackers
Tree view 
Peter Eisentraut <peter.eisentraut@2ndquadrant.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

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Connections hang indefinitely while taking a gin index's LWLockbuffer_content lock(PG10.7)
Next
From: Peter Geoghegan
Date:
Subject: Re: Connections hang indefinitely while taking a gin index's LWLockbuffer_content lock(PG10.7)