Re: update on global temporary and unlogged tables

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Rob Wultsch <wultsch(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: update on global temporary and unlogged tables
Date: 2010-09-14 02:37:11
Message-ID: AANLkTinOEVCzT_-YPoarm-YXvJq_F3BDgxLcyMDWSTFB@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Sep 13, 2010 at 9:06 PM, Rob Wultsch <wultsch(at)gmail(dot)com> wrote:
> On Mon, Sep 6, 2010 at 7:55 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>>
>> 3. With respect to unlogged tables, the major obstacle seems to be
>> figuring out a way for these to get automatically truncated at startup
>> time.
>
> (please forgive what is probably a stupid question)
> By truncate do mean reduce the table to a very small number (or zero) number
> of pages? Is there a case to be made for instead somehow marking all pages
> as available for reuse? Deallocating and reallocating space can be
> expensive.

I think it's probably actually cheaper to truncate them, but since it
only happens at startup time it's probably not worth worrying
about....

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2010-09-14 02:37:21 Re: Report: removing the inconsistencies in our CVS->git conversion
Previous Message Andrew Dunstan 2010-09-14 02:06:37 Re: patch: Add JSON datatype to PostgreSQL (GSoC, WIP)