Re: Reducing ClogControlLock contention

Поиск
Список
Период
Сортировка
Искать
От
Simon Riggs
Тема
Re: Reducing ClogControlLock contention
Дата
Msg-id
CANP8+jKUfWNz3FQS_2o19bV7vESO+v_WmBqkVrRoHPr1pTs5Kw@mail.gmail.com
Ответ на
Список
Дерево обсуждения
Reducing ClogControlLock contention Simon Riggs <simon@2ndQuadrant.com>
Re: Reducing ClogControlLock contention Andres Freund <andres@anarazel.de>
Re: Reducing ClogControlLock contention Simon Riggs <simon@2ndQuadrant.com>
Re: Reducing ClogControlLock contention Simon Riggs <simon@2ndQuadrant.com>
Re: Reducing ClogControlLock contention Amit Kapila <amit.kapila16@gmail.com>
Re: Reducing ClogControlLock contention Simon Riggs <simon@2ndQuadrant.com>
Re: Reducing ClogControlLock contention Amit Kapila <amit.kapila16@gmail.com>
Re: Reducing ClogControlLock contention Jesper Pedersen <jesper.pedersen@redhat.com>
Re: Reducing ClogControlLock contention Amit Kapila <amit.kapila16@gmail.com>
Re: Reducing ClogControlLock contention Amit Kapila <amit.kapila16@gmail.com>
Re: Reducing ClogControlLock contention Simon Riggs <simon@2ndQuadrant.com>
Re: Reducing ClogControlLock contention Andres Freund <andres@anarazel.de>
Re: Reducing ClogControlLock contention Simon Riggs <simon@2ndQuadrant.com>
Re: Reducing ClogControlLock contention Andres Freund <andres@anarazel.de>
Re: Reducing ClogControlLock contention Robert Haas <robertmhaas@gmail.com>
Re: Reducing ClogControlLock contention Amit Kapila <amit.kapila16@gmail.com>
Re: Reducing ClogControlLock contention Simon Riggs <simon@2ndQuadrant.com>
Re: Reducing ClogControlLock contention Amit Kapila <amit.kapila16@gmail.com>
Re: Reducing ClogControlLock contention Amit Kapila <amit.kapila16@gmail.com>
Re: Reducing ClogControlLock contention Simon Riggs <simon@2ndQuadrant.com>
Re: Reducing ClogControlLock contention Amit Kapila <amit.kapila16@gmail.com>
Re: Reducing ClogControlLock contention Simon Riggs <simon@2ndQuadrant.com>
Re: Reducing ClogControlLock contention Simon Riggs <simon@2ndQuadrant.com>
Re: Reducing ClogControlLock contention Amit Kapila <amit.kapila16@gmail.com>
Re: Reducing ClogControlLock contention Amit Kapila <amit.kapila16@gmail.com>
Re: Reducing ClogControlLock contention Simon Riggs <simon@2ndQuadrant.com>
Re: Reducing ClogControlLock contention Michael Paquier <michael.paquier@gmail.com>
Re: Reducing ClogControlLock contention Simon Riggs <simon@2ndQuadrant.com>
Re: Reducing ClogControlLock contention Amit Kapila <amit.kapila16@gmail.com>
Re: Reducing ClogControlLock contention Simon Riggs <simon@2ndQuadrant.com>
On 22 August 2015 at 15:14, Andres Freund <andres@anarazel.de> wrote:
 
TransactionIdSetPageStatus() calls TransactionIdSetStatusBit(), which
writes an 8 byte variable (the lsn). That's not safe.

This point was the main sticking point here.

It turns out that we don't need to store the LSN (8 bytes). 

WAL is fsynced every time we finish writing a file, so we only actually need to store the byte position within each file, so no more than 16MB. That fits within a 4 byte value, so can be written atomically. 

So I have a valid way forward for this approach. Cool.

--
Simon Riggs                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления
От: Robert Haas
Дата:
От: David Rowley
Дата:
FAQ