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

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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:17:48
Message-ID: 20210320001748.n5zkqsafuiwk7txp@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

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. And it might
even allow to backpatch this, if we cared enough, since I assume the
mingw jmp_buf is larger than intptr_t[5].

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2021-03-20 00:31:07 Re: BUG #16927: Postgres can`t access WAL files
Previous Message Tom Lane 2021-03-20 00:08:24 Re: BUG #16927: Postgres can`t access WAL files