Re: libpq async duplicate error results

Поиск
Список
Период
Сортировка
Искать
От
Andres Freund
Тема
Re: libpq async duplicate error results
Дата
Msg-id
20220217011109.edkms5f2iqr3ofmv@alap3.anarazel.de
Ответ на
Список
Дерево обсуждения
libpq async duplicate error results Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: libpq async duplicate error results Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: libpq async duplicate error results Tom Lane <tgl@sss.pgh.pa.us>
Re: libpq async duplicate error results Fabien COELHO <coelho@cri.ensmp.fr>
Re: libpq async duplicate error results Tom Lane <tgl@sss.pgh.pa.us>
Re: libpq async duplicate error results Alvaro Herrera <alvherre@alvh.no-ip.org>
Re: libpq async duplicate error results Tom Lane <tgl@sss.pgh.pa.us>
Re: libpq async duplicate error results Tom Lane <tgl@sss.pgh.pa.us>
Re: libpq async duplicate error results Tom Lane <tgl@sss.pgh.pa.us>
Re: libpq async duplicate error results Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: libpq async duplicate error results Tom Lane <tgl@sss.pgh.pa.us>
Re: libpq async duplicate error results Tom Lane <tgl@sss.pgh.pa.us>
Re: libpq async duplicate error results Tom Lane <tgl@sss.pgh.pa.us>
Re: libpq async duplicate error results Andres Freund <andres@anarazel.de>
Re: libpq async duplicate error results Tom Lane <tgl@sss.pgh.pa.us>
Re: libpq async duplicate error results Andres Freund <andres@anarazel.de>
Re: libpq async duplicate error results Tom Lane <tgl@sss.pgh.pa.us>
Re: libpq async duplicate error results Fabien COELHO <coelho@cri.ensmp.fr>
Re: libpq async duplicate error results Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Hi,

On 2022-02-16 18:51:37 -0500, Tom Lane wrote:
> This seems workable, and you'll notice it fixes the duplicated text
> in the test case Andres was worried about.

Cool.

I find it mildly scary that we didn't have any other tests verifying the libpq
side of connection termination. Seems like we we maybe should add a few more?
Some simple cases we can do via isolationtester. But some others would
probably require a C test program to be robust...


> +	/* Also, do nothing if the argument is OOM_result */
> +	if (res == unconstify(PGresult *, &OOM_result))
> +		return;

Wouldn't it make more sense to make res const, rather than unconstifying
&OOM_result?


Greetings,

Andres Freund


В списке pgsql-hackers по дате отправления
От: Nathan Bossart
Дата:
От: Peter Geoghegan
Дата:
FAQ