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

Large tables being split at 1GB boundary

From: Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net>
To: PgSQL Novice ML <pgsql-novice(at)postgresql(dot)org>
Subject: Large tables being split at 1GB boundary
Date: 2002-05-21 20:20:13
Message-ID: 1022012413.16477.41.camel@rebel (view raw or flat)
Thread:
Lists: pgsql-novice
Hi.

I have a table whose pg_class.relfilenode is, as you can
tell, 619703, and I see that pg 7.2.1 automagically splits
the makes a new container file at the exact 1GiB mark.

$ ls -aFl 619703*
-rw------- 1 postgres postgres 1073741824 May 21 13:38 619703
-rw------- 1 postgres postgres 1073741824 May 21 02:05 619703.1
-rw------- 1 postgres postgres 1073741824 May 21 13:39 619703.2
-rw------- 1 postgres postgres 1073741824 May 21 14:19 619703.3
-rw------- 1 postgres postgres 234250240 May 21 15:09 619703.4

Apart from allowing me to spread large tables across multiple
drives using symlinks (that _is_ the preferred method, correct?),
what is the reason for splitting filenodes at the 1GB mark?
Why not 2GB (2^31).

Thanks,
Ron
-- 
+---------------------------------------------------------+
| Ron Johnson, Jr.        Home: ron(dot)l(dot)johnson(at)cox(dot)net     |
| Jefferson, LA  USA      http://ronandheather.dhs.org:81 |
|                                                         |
| "I have created a government of whirled peas..."        |
|   Maharishi Mahesh Yogi, 12-May-2002,                   |
!   CNN, Larry King Live                                  |
+---------------------------------------------------------+


Responses

pgsql-novice by date

Next:From: Kevin SternerDate: 2002-05-21 20:33:03
Subject: Undead record haunts my database, need exorcism
Previous:From: Joel BurtonDate: 2002-05-21 13:38:38
Subject: Re: [NOVICE] Problem with inserting: attribute 'extended_reason'

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