Skip site navigation (1) Skip section navigation (2)

Re: extending relations more efficiently

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Jeroen Vermeulen <jtv(at)xs4all(dot)nl>
Cc: Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: extending relations more efficiently
Date: 2012-05-02 12:14:36
Message-ID: CA+TgmoaEGAqTTcEQX2QDz4VTOd7_X9ScuYNHre1krZCUPQE8gw@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Wed, May 2, 2012 at 7:16 AM, Jeroen Vermeulen <jtv(at)xs4all(dot)nl> wrote:
> On 2012-05-01 22:06, Robert Haas wrote:
>> It might also be interesting to provide a mechanism to pre-extend a
>> relation to a certain number of blocks, though if we did that we'd
>> have to make sure that autovac got the memo not to truncate those
>> pages away again.
>
> Good point.  And just to check before skipping over it, do we know that
> autovacuum not leaving enough slack space is not a significant cause of the
> bottlenecks in the first place?

I'm not sure exactly what you mean by this: autovacuum doesn't need
any slack space.  Regular DML operations can certainly benefit from
slack space, both within each page and overall within the relation.
But there's no evidence that vacuum is doing too good a job cleaning
up the mess, forcing the relation to be re-extended.  Rather, the
usual (and frequent) complaint is that vacuum is leaving way too much
slack space - i.e. bloat.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

pgsql-hackers by date

Next:From: Robert HaasDate: 2012-05-02 12:41:02
Subject: Re: index-only scans vs. Hot Standby, round two
Previous:From: Peter GeogheganDate: 2012-05-02 11:47:01
Subject: Re: Have we out-grown Flex?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group