Re: thread-safety: gmtime_r(), localtime_r()

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Stepan Neretin <sncfmgg(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: thread-safety: gmtime_r(), localtime_r()
Date: 2024-06-27 06:09:22
Message-ID: 12611bd0-1620-4aa8-8068-27c0632f434f@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 27.06.24 06:47, Stepan Neretin wrote:
> Hi! Looks good to me.
> But why you don`t change localtime function at all places?
> For example:
> src/bin/pg_controldata/pg_controldata.c
> src/bin/pg_dump/pg_backup_archiver.c
> src/bin/initdb/findtimezone.c

At the moment, I am focusing on the components that are already meant to
be thread-safe (libpq, ecpg libs) and the ones we are actively looking
at maybe converting (backend). I don't intend at this point to convert
all other code to use only thread-safe APIs.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2024-06-27 06:12:20 Re: Adminpack removal
Previous Message Michael Paquier 2024-06-27 05:43:54 Re: walsender.c comment with no context is hard to understand