Re: Logical tape pause/resume - Mailing list pgsql-hackers

From Claudio Freire
Subject Re: Logical tape pause/resume
Date
Msg-id CAGTBQpYz7c1N+W1ggbJ_VBmwSvM28pHFEqn3VipL0QdTeiwT8A@mail.gmail.com
Whole thread Raw
In response to Logical tape pause/resume  (Heikki Linnakangas <hlinnaka@iki.fi>)
Responses Re: Logical tape pause/resume  (Heikki Linnakangas <hlinnaka@iki.fi>)
List pgsql-hackers
On Tue, Oct 4, 2016 at 7:47 AM, Heikki Linnakangas <hlinnaka@iki.fi> wrote:
> 1. The first patch changes the way we store the logical tapes on disk.
> Instead of using indirect blocks, HFS style, the blocks form a linked list.
> Each block has a trailer, with the block numbers of the previous and next
> block of the tape. That eliminates the indirect blocks, which simplifies the
> code quite a bit, and makes it simpler to implement the pause/resume
> functionality in the second patch. It also immediately reduces the memory
> needed for the buffers, from 3 to 1 block per tape, as we don't need to hold
> the indirect blocks in memory.

Doesn't that make prefetching more than a buffer ahead harder?



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Misidentification of Python shared library
Next
From: Alvaro Herrera
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Extend framework from commit 53be0b1ad to report latch waits.