diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2021-03-15 12:34:17 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2021-03-15 12:34:17 -0400 |
| commit | 146cb3889c3ccb3fce198fe7464a1296a9e107c3 (patch) | |
| tree | 47c436adf7839e52a50f1535f7964ef3bbd4ee94 /src/backend/tcop/postgres.c | |
| parent | eeb60e45d82d5840b713a8741ae552238d57e8b9 (diff) | |
| download | postgresql-146cb3889c3ccb3fce198fe7464a1296a9e107c3.tar.gz postgresql-146cb3889c3ccb3fce198fe7464a1296a9e107c3.zip | |
Work around issues in MinGW-64's setjmp/longjmp support.
It's hard to avoid the conclusion that there is something wrong with
setjmp/longjmp on MinGW-64, as we have seen failures come and go after
entirely-unrelated-looking changes in our own code. Other projects
such as Ruby have given up and started using gcc's setjmp/longjmp
builtins on that platform; this patch just follows that lead.
Note that this is a pretty fundamental ABI break for functions
containining either setjmp or longjmp, so we can't really consider
a back-patch.
Per reports from Regina Obe and Heath Lord, as well as recent failures
on buildfarm member walleye, and less-recent failures on fairywren.
Juan José SantamarÃa Flecha
Discussion: https://postgr.es/m/000401d716a0$1ed0fc70$5c72f550$@pcorp.us
Discussion: https://postgr.es/m/CA+BEBhvHhM-Bn628pf-LsjqRh3Ang7qCSBG0Ga+7KwhGqrNUPw@mail.gmail.com
Discussion: https://postgr.es/m/f1caef93-9640-022e-9211-bbe8755a56b0@2ndQuadrant.com
Diffstat (limited to 'src/backend/tcop/postgres.c')
0 files changed, 0 insertions, 0 deletions