Chris Ruprecht writes:
> I was wondering if there is a way to pre-allocate tablespace on disk
> before adding data and indexes.
As others have already said, it's not clear there's a point in doing
that with PostgreSQL. Now, you can achieve it and see for yourself by
relying on OS tools, such as L
Not only that, but if your "disk" is really a bunch of disks behind
a hardware RAID controller, or SAN, or iSCSI or NFS server - what is
contiguous for the OS may not be contiguous on the physical drives
(and vice versa).
Which is why performance can (but may not) impro
* Chris Ruprecht:
> Other database that I have worked with before and that I'm still
> working with, allow you to pre-allocate disk space so you get huge
> chunks of contiguous space at one, which has major impacts on
> database performance.
PostgreSQL's write patterns do not trigger significant
On 11/15/10 11:42 AM, Chris Ruprecht wrote:
I was wondering if there is a way to pre-allocate tablespace on disk before
adding data and indexes.
My understanding is:
PG writes data into files sequentially. If more space is needed, disk space
is requested from the OS and if there is space, the OS
Le 15/11/2010 20:42, Chris Ruprecht a écrit :
> Hello,
>
> I was wondering if there is a way to pre-allocate tablespace on disk before
> adding data and indexes.
> My understanding is:
> PG writes data into files sequentially. If more space is needed, disk space
> is requested from the OS and if
Hello,
I was wondering if there is a way to pre-allocate tablespace on disk before
adding data and indexes.
My understanding is:
PG writes data into files sequentially. If more space is needed, disk space is
requested from the OS and if there is space, the OS will give PG a file system
block an
