aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/jsonfuncs.c
diff options
context:
space:
mode:
authorAndres Freund <andres@anarazel.de>2021-09-07 11:56:13 -0700
committerAndres Freund <andres@anarazel.de>2021-09-07 11:56:13 -0700
commit76e38b37a5f179d4c9d2865ff31b79130407530b (patch)
treef9a1c893952550fcf4aa8e612ecd5569a87f3c92 /src/backend/utils/adt/jsonfuncs.c
parent6ac763f19a6556c43933c5252065a5c81cde094d (diff)
downloadpostgresql-76e38b37a5f179d4c9d2865ff31b79130407530b.tar.gz
postgresql-76e38b37a5f179d4c9d2865ff31b79130407530b.zip
windows: Only consider us to be running as service if stderr is invalid.
Previously pgwin32_is_service() would falsely return true when postgres is started from somewhere within a service, but not as a service. That is e.g. always the case with windows docker containers, which some CI services use to run windows tests in. When postgres falsely thinks its running as a service, no messages are writting to stdout / stderr. That can be very confusing and causes a few tests to fail. To fix additionally check if stderr is invalid in pgwin32_is_service(). For that to work in backend processes, pg_ctl is changed to pass down handles so that postgres can do the same check (otherwise "default" handles are created). While this problem exists in all branches, there have been no reports by users, the prospective CI usage currently is only for master, and I am not a windows expert. So doing the change in only master for now seems the sanest approach. Author: Andres Freund <andres@anarazel.de> Reviewed-By: Magnus Hagander <magnus@hagander.net> Discussion: https://postgr.es/m/20210305185752.3up5eq2eanb7ofmb@alap3.anarazel.de
Diffstat (limited to 'src/backend/utils/adt/jsonfuncs.c')
0 files changed, 0 insertions, 0 deletions