From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | Juan José Santamaría Flecha <juanjo(dot)santamaria(at)gmail(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Using AF_UNIX sockets always for tests on Windows |
Date: | 2023-03-22 04:28:12 |
Message-ID: | CA+hUKGJkBm0kKLrZax_SSMPYBzZtaeU5CsiUj4NUm9LBp4YnfA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thanks Tom, Andres, Juan José, Andrew for your feedback. I agree that
it's a better "OS harmonisation" outcome if we can choose both ways on
both OSes. I will leave the 0003 patch aside for now due to lack of
time, but here's a rebase of the first two patches. Since this is
really just more cleanup-obsolete-stuff background work, I'm going to
move it to the next CF.
0001 -- Teach mkdtemp() to care about permissions on Windows.
Reviewed by Juan José, who confirmed my blind-coded understanding and
showed an alternative version but didn't suggest doing it that way.
It's a little confusing that NULL "attributes" means something
different from NULL "descriptor", so I figured I should highlight that
difference more clearly with some new comments. I guess one question
is "why should we expect the calling process to have the default
access token?"
0002 -- Use AF_UNIX for pg_regress. This one removes a couple of
hundred Windows-only lines that set up SSPI stuff, and some comments
about a signal handling hazard that -- as far as I can tell by reading
manuals -- was never really true.
0003 -- TAP testing adjustments needs some more work based on feedback
already given, not included in this revision.
Attachment | Content-Type | Size |
---|---|---|
v3-0001-Make-mkdtemp-more-secure-on-Windows.patch | text/x-patch | 2.1 KB |
v3-0002-Always-use-AF_UNIX-sockets-in-pg_regress-on-Windo.patch | text/x-patch | 10.9 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2023-03-22 04:45:12 | Re: Reconcile stats in find_tabstat_entry() and get rid of PgStat_BackendFunctionEntry |
Previous Message | Greg Stark | 2023-03-22 04:05:38 | Re: Commitfest 2023-03 starting tomorrow! |