| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Regina Obe <lr(at)pcorp(dot)us>, "'Heikki Linnakangas'" <hlinnaka(at)iki(dot)fi>, "'Juan José Santamaría Flecha'" <juanjo(dot)santamaria(at)gmail(dot)com>, "'PostgreSQL mailing lists'" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #16920: Can't compile PostGIS with MingW64 against PostgreSQL 14 head |
| Date: | 2021-03-20 00:37:17 |
| Message-ID: | 362.1616200637@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2021-03-15 12:12:59 -0400, Tom Lane wrote:
>> Although I remain worried about this being an ABI break, I don't think
>> we are locked into it until we get to beta, or maybe even RC stage.
> Could it make sense to define sigjmp_buf as a union over the potentially
> needed implementations? That'd allow us to switch back without an ABI
> break if we discover a problem with the gcc approach.
No, it'd still be an ABI break, because the setjmp and the longjmp calls
have to use the same implementation. Ain't gonna work if elog.c tries
to throw via mingw's longjmp() while some extension contains a PG_TRY
that uses __builtin_setjmp(). Nor vice versa.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vlad G | 2021-03-20 09:19:27 | Re: BUG #16932: Database Crash with : ERROR: cache lookup failed for type 0 |
| Previous Message | Michael Paquier | 2021-03-20 00:31:07 | Re: BUG #16927: Postgres can`t access WAL files |