Re: ON CONFLICT (and manual row locks) cause xmax of updated tupleto unnecessarily be set

Поиск
Список
Период
Сортировка
От Andres Freund
Тема Re: ON CONFLICT (and manual row locks) cause xmax of updated tupleto unnecessarily be set
Дата
Msg-id 20190725221000.i7oryd5m5z22fnir@alap3.anarazel.de
обсуждение исходный текст
Ответ на Re: ON CONFLICT (and manual row locks) cause xmax of updated tuple tounnecessarily be set  (Peter Geoghegan <pg@bowt.ie>)
Ответы Re: ON CONFLICT (and manual row locks) cause xmax of updated tuple tounnecessarily be set  (Peter Geoghegan <pg@bowt.ie>)
Список pgsql-hackers
Hi,

On 2019-07-24 17:14:39 -0700, Peter Geoghegan wrote:
> On Wed, Jul 24, 2019 at 4:24 PM Andres Freund <andres@anarazel.de> wrote:
> > but we really don't need to do any of that in this case - the only
> > locker is the current backend, after all.
> >
> > I think this isn't great, because it'll later will cause unnecessary
> > hint bit writes (although ones somewhat likely combined with setting
> > XMIN_COMMITTED), and even extra work for freezing.
> >
> > Based on a quick look this wasn't the case before the finer grained
> > tuple locking - which makes sense, there was no cases where locks would
> > need to be carried forward.
> 
> I agree that this is unfortunate. Are you planning on working on it?

Not at the moment, no. Are you planning / hoping to take a stab at it?

Greetings,

Andres Freund



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

Предыдущее
От: Stephen Frost
Дата:
Сообщение: Re: [Proposal] Table-level Transparent Data Encryption (TDE) and KeyManagement Service (KMS)
Следующее
От: Thomas Munro
Дата:
Сообщение: Re: On the stability of TAP tests for LDAP