Re: [HACKERS] Improving overflow checks when adding tuple to PGresultRe: [GENERAL] Retrieving query results

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: [HACKERS] Improving overflow checks when adding tuple to PGresultRe: [GENERAL] Retrieving query results
Дата
Msg-id CAB7nPqSqU9dg0-FZoKm9kGZmU2bRFeDg3BzZCF0bLvXiQ0HgBw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] Improving overflow checks when adding tuple to PGresult Re: [GENERAL] Retrieving query results  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On Wed, Aug 30, 2017 at 4:24 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Michael Paquier <michael.paquier@gmail.com> writes:
>> On Mon, Aug 28, 2017 at 3:05 PM, Michael Paquier
>> <michael.paquier@gmail.com> wrote:
>>> Attached are two patches:
>>> 1) 0001 refactors the code around pqAddTuple to be able to handle
>>> error messages and assign them in PQsetvalue particularly.
>>> 2) 0002 adds sanity checks in pqAddTuple for overflows, maximizing the
>>> size of what is allocated to INT_MAX but now more.
>
> I've pushed these (as one commit) with some adjustments.

Thanks!

> Mainly,
> I changed PQsetvalue to report failure messages with PQinternalNotice,
> which is what already happens inside check_field_number() for the case
> of an out-of-range field number.  It's possible that storing the
> message into the PGresult in addition would be worth doing, but I'm
> unconvinced about that --- we certainly haven't had any field requests
> for it.

OK, fine for me.
-- 
Michael



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

Предыдущее
От: Peter Geoghegan
Дата:
Сообщение: Re: [HACKERS] A design for amcheck heapam verification
Следующее
От: Robert Haas
Дата:
Сообщение: Re: [HACKERS] Proposal: Improve bitmap costing for lossy pages