Re: BUG #16039: PANIC when activating replication slots in Postgres12.0 64bit under Windows

Поиск
Список
Период
Сортировка
От Andres Freund
Тема Re: BUG #16039: PANIC when activating replication slots in Postgres12.0 64bit under Windows
Дата
Msg-id 20191010152515.q5uo3pg6ai7ppvd2@alap3.anarazel.de
обсуждение исходный текст
Ответ на Re: BUG #16039: PANIC when activating replication slots in Postgres12.0 64bit under Windows  (Michael Paquier <michael@paquier.xyz>)
Ответы Re: BUG #16039: PANIC when activating replication slots in Postgres12.0 64bit under Windows  (Michael Paquier <michael@paquier.xyz>)
Список pgsql-bugs
Hi,

On 2019-10-09 13:42:07 +0900, Michael Paquier wrote:
> > Yuck :(. Luckily that's a pretty narrow case to hit.  We really need
> > windows coverage for this stuff. And also just general buildfarm
> > coverage, it's not like we're immune from bugs on unixoid OSs etiher.
> 
> test_decoding hits that easily for me, and we test that on Windows for
> some time now as there is a buildfarm module.  That's a bit depressing.

Well, that's because it intentionally tries to hit that case ;)

But yea, it's not good.

I think we really ought to remove the -F from pg_regress.c, and leave
that up to the caller. Right now it's just about impossible to
configure without patching the source, unless I miss something.


> >> Andres, others, any thoughts about this issue?  Are there any
> >> objections if I just fix it?
> > 
> > Not here.
> 
> Done this one.

Thanks.

Greetings,

Andres Freund



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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12
Следующее
От: Tomas Vondra
Дата:
Сообщение: Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12