Re: BUG #16920: Can't compile PostGIS with MingW64 against PostgreSQL 14 head

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: BUG #16920: Can't compile PostGIS with MingW64 against PostgreSQL 14 head
Дата
Msg-id 362.1616200637@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: BUG #16920: Can't compile PostGIS with MingW64 against PostgreSQL 14 head  (Andres Freund <andres@anarazel.de>)
Ответы Re: BUG #16920: Can't compile PostGIS with MingW64 against PostgreSQL 14 head  (Andres Freund <andres@anarazel.de>)
Список pgsql-bugs
Andres Freund <andres@anarazel.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



В списке pgsql-bugs по дате отправления:

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: BUG #16927: Postgres can`t access WAL files
Следующее
От: Vlad G
Дата:
Сообщение: Re: BUG #16932: Database Crash with : ERROR: cache lookup failed for type 0