pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim C. Nasby <jnasby@pervasive.com>
To: Tomeh, Husam <htomeh@firstam.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Pre-allocate space in advance
Date: Mon, 31 Oct 2005 18:40:48 -0600
Message-ID: <20051101004048.GS20349@pervasive.com> (raw)
In-Reply-To: <C45835824D00A844BBD0F032D5CDED9202D55554@pisgana01sxch01.ana.firstamdata.com>
References: <C45835824D00A844BBD0F032D5CDED9202D55554@pisgana01sxch01.ana.firstamdata.com>

There was recently discussion about changing how allocation happens in
the future. I'm pretty sure it was started by Bruce Momjian on -hackers,
but I can't find it in the archives now...

On Mon, Oct 31, 2005 at 03:14:13PM -0800, Tomeh, Husam wrote:
> I apologize for the wrong subject in a previous post. Here it is again:
>  
>  
>   My understanding that the current release of Postgres does not allow
> the DBA to pre-allocated space for the data files or tablespace in
> advance (as Oracle or SQL Server does). Am I correct on that ? If that's
> still the case, is this item on the TODO list or the white board?
> Pre-allocating space will prevent extending the datafile during loading
> massive data (batch processing) and would improve the overall batch
> write performance. 
>  
> Thanks in advance.
> 
> -- 
>  Husam 
> 
> ---------------------------(end of broadcast)---------------------------
> 
> TIP 2: Don't 'kill -9' the postmaster
> 
> 
> 
> 
> 
> **********************************************************************
> This message contains confidential information intended only for the 
> use of the addressee(s) named above and may contain information that 
> is legally privileged.  If you are not the addressee, or the person 
> responsible for delivering it to the addressee, you are hereby 
> notified that reading, disseminating, distributing or copying this 
> message is strictly prohibited.  If you have received this message by 
> mistake, please immediately notify us by replying to the message and 
> delete the original message immediately thereafter.
> 
> Thank you.                                       FADLD Tag
> **********************************************************************

-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461



view thread (8+ messages)  latest in thread

Message-ID: <20051101004048.GS20349@pervasive.com>
Permalink:  ../20051101004048.GS20349@pervasive.com/
Also on:    postgresql.org/message-id/20051101004048.GS20349@pervasive.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: jnasby@pervasive.com, htomeh@firstam.com
  Subject: Re: Pre-allocate space in advance
  In-Reply-To: <20051101004048.GS20349@pervasive.com>
  References: <C45835824D00A844BBD0F032D5CDED9202D55554@pisgana01sxch01.ana.firstamdata.com> <20051101004048.GS20349@pervasive.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox