Re: WALInsertLock tuning

Поиск
Список
Период
Сортировка
От Simon Riggs
Тема Re: WALInsertLock tuning
Дата
Msg-id BANLkTi=-v1qTQaTP2yFr=ttWs72-kCC1FA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: WALInsertLock tuning  (Jeff Janes <jeff.janes@gmail.com>)
Ответы Re: WALInsertLock tuning  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers
On Mon, Jun 6, 2011 at 10:09 PM, Jeff Janes <jeff.janes@gmail.com> wrote:
> On Mon, Jun 6, 2011 at 11:27 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
>>
>> But that even assumes we write the unzeroed data at the end of the
>> buffer. We don't. We only write data up to the end of the WAL record
>> on the current page, unless we do a continuation record,
>
> I see no codepath in XLogWrite which writes anything other than full
> buffer pages.

Second line, boolean variable called "ispartialpage".

As I mentioned, even if spare bytes at the end of page were written,
they aren't ever read except in corner case bugs that would be trapped
by other logic put there to protect us.

We're safe. If I didn't believe it and hadn't tested it, I wouldn't speak.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


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

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: Postmaster holding unlinked files for pg_largeobject table
Следующее
От: Simon Riggs
Дата:
Сообщение: Re: reducing the overhead of frequent table locks - now, with WIP patch