Re: Add jsonlog log_destination for JSON server logs - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Add jsonlog log_destination for JSON server logs
Date
Msg-id YVPJIuSeUujhhHsb@paquier.xyz
Whole thread Raw
In response to Re: Add jsonlog log_destination for JSON server logs  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Add jsonlog log_destination for JSON server logs  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On Tue, Sep 28, 2021 at 12:30:10PM +0900, Michael Paquier wrote:
> 0001 is in a rather commitable shape, and I have made the code
> consistent with HEAD.  However, I think that its handling of
> _get_osfhandle() is clunky for 64-bit compilations as long is 32b in
> WIN32 but intptr_t is platform-dependent as it could be 32b or 64b, so
> atoi() would overflow if the handle is larger than INT_MAX for 64b
> builds:
> https://docs.microsoft.com/en-us/cpp/c-runtime-library/standard-types
> This problem deserves a different thread.

This happens to not be a problem as only 32 bits are significant for
handles for both Win32 and Win64.  This also means that we should be
able to remove the use for "long" in this code, making the routines
more symmetric.  I have done more tests with Win32 and Win64, and
applied it.  I don't have MinGW environments at hand, but looking at
the upstream code that should not matter.  The buildfarm will let
us know soon enough if there is a problem thanks to the TAP tests of
pg_ctl.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: katouknl
Date:
Subject: [PATCH] Added TRANSFORM FOR for COMMENT tab completion
Next
From: Thomas Munro
Date:
Subject: Re: Make relfile tombstone files conditional on WAL level