Re: fallocate / posix_fallocate for new WAL file creation (etc...)

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Greg Smith <greg(at)2ndQuadrant(dot)com>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, Andres Freund <andres(at)2ndquadrant(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Jon Nelson <jnelson+pgsql(at)jamponi(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: fallocate / posix_fallocate for new WAL file creation (etc...)
Date: 2013-05-30 15:21:26
Message-ID: 20130530152126.GE2548@eldon.alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Greg Smith escribió:

> The messy part of extending relations in larger chunks
> is how to communicate that back into the buffer manager usefully.
> The extension path causing trouble is RelationGetBufferForTuple
> calling ReadBufferBI. All of that is passing a single buffer
> around. There's no simple way I can see to rewrite it to handle
> more than one at a time.

No, but we can have it create several pages and insert them into the
FSM. So they aren't returned to the original caller but are available
to future users.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Smith 2013-05-30 15:45:31 Re: fallocate / posix_fallocate for new WAL file creation (etc...)
Previous Message Dimitri Fontaine 2013-05-30 15:11:12 Re: pg_dump with postgis extension dumps rules separately