Re: Fix last unitialized memory warning

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: Fix last unitialized memory warning
Дата
Msg-id a88b0adf-9e26-fbbc-805e-6e0da5ae64bf@eisentraut.org
обсуждение исходный текст
Ответ на Re: Fix last unitialized memory warning  ("Tristan Partin" <tristan@neon.tech>)
Ответы Re: Fix last unitialized memory warning  (Peter Eisentraut <peter@eisentraut.org>)
Список pgsql-hackers
Дерево обсуждения 
On 08.08.23 17:14, Tristan Partin wrote:
>> I was able to reproduce the warning now on Fedora.  I agree with the 
>> patch
>>
>> -       PgBenchValue vargs[MAX_FARGS];
>> +       PgBenchValue vargs[MAX_FARGS] = { 0 };
>>
>> I suggest to also do
>>
>>   typedef enum
>>   {
>> -       PGBT_NO_VALUE,
>> +       PGBT_NO_VALUE = 0,
>>
>> to make clear that the initialization value is meant to be invalid.
>>
>> I also got the plpgsql warning that you showed earlier, but I couldn't 
>> think of a reasonable way to fix that.
> 
> Applied in v2.

committed

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

Предыдущее
От: Kyotaro Horiguchi
Дата:
Сообщение: Re: Incorrect handling of OOM in WAL replay leading to data loss
Следующее
От: Yuya Watari
Дата:
Сообщение: Re: [PoC] Reducing planning time when tables have many partitions