Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock
Дата
Msg-id 28311.1560526116@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Ответы Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-committers
Дерево обсуждения 
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> On 2019-Jun-14, Tom Lane wrote:
>> I'm now getting
>> heapam.c: In function 'heap_lock_tuple':
>> heapam.c:4041: warning: 'skip_tuple_lock' may be used uninitialized in this function

> Hm, I don't get that warning.  Does this patch silence it, please?

Uh, no patch attached?  But initializing the variable where it's
declared would certainly silence it.

            regards, tom lane

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: pgsql: Attempt to identify system timezone by reading /etc/localtimesy
Следующее
От: Tom Lane
Дата:
Сообщение: Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock