pg_stat_statements vs. SELECT FOR UPDATE

Поиск
Список
Период
Сортировка
От Andrew Gierth
Тема pg_stat_statements vs. SELECT FOR UPDATE
Дата
Msg-id 87h8e4hfwv.fsf@news-spur.riddles.org.uk
обсуждение исходный текст
Ответы Re: pg_stat_statements vs. SELECT FOR UPDATE  (Vik Fearing <vik.fearing@2ndquadrant.com>)
Re: pg_stat_statements vs. SELECT FOR UPDATE  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
pg_stat_statements considers a plain select and a select for update to
be equivalent, which seems quite wrong to me as they will have very
different performance characteristics due to locking.

The only comment about it in the code is:

    /* we ignore rowMarks */

I propose that it should not ignore rowMarks, per the attached patch or
something similar.

(thanks to Vik Fearing for preliminary testing)

-- 
Andrew (irc:RhodiumToad)


Вложения

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

Предыдущее
От: Andrew Gierth
Дата:
Сообщение: Re: Ryu floating point output patch
Следующее
От: "Daniel Verite"
Дата:
Сообщение: Re: Alternative to \copy in psql modelled after \g