pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
So what happens at 2GB?
6+ messages / 4 participants
[nested] [flat]

* So what happens at 2GB?
@ 1999-03-12 23:35  Tim Perdue <perdue@raccoon.com>
  0 siblings, 1 reply; 6+ messages in thread

From: Tim Perdue @ 1999-03-12 23:35 UTC (permalink / raw)
  To: pgsql-sql@hub.org

I'm told that my postgres table will automagically split when it hits 2GB,
but I understand that code is not well tested.

Do I need to worry at all when I hit 2GB?

Thanks,

Tim
geocrawler




^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: [SQL] So what happens at 2GB?
@ 1999-03-12 23:56  Karl Denninger <karl@Denninger.Net>
  parent: Tim Perdue <perdue@raccoon.com>
  0 siblings, 1 reply; 6+ messages in thread

From: Karl Denninger @ 1999-03-12 23:56 UTC (permalink / raw)
  To: Tim Perdue <perdue@raccoon.com>; pgsql-sql@hub.org

No.  It works properly.  I have had tables exceeding 10GB.

--
-- 
Karl Denninger (karl@denninger.net) http://www.mcs.net/~karl
I ain't even *authorized* to speak for anyone other than myself, so give
up now on trying to associate my words with any particular organization.


On Fri, Mar 12, 1999 at 05:35:17PM -0600, Tim Perdue wrote:
> I'm told that my postgres table will automagically split when it hits 2GB,
> but I understand that code is not well tested.
> 
> Do I need to worry at all when I hit 2GB?
> 
> Thanks,
> 
> Tim
> geocrawler
> 
> 



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: [SQL] So what happens at 2GB?
@ 1999-03-13 18:11  Brett W. McCoy <bmccoy@lan2wan.com>
  parent: Karl Denninger <karl@Denninger.Net>
  0 siblings, 1 reply; 6+ messages in thread

From: Brett W. McCoy @ 1999-03-13 18:11 UTC (permalink / raw)
  To: Karl Denninger <karl@Denninger.Net>; +Cc: Tim Perdue <perdue@raccoon.com>; pgsql-sql@hub.org

On Fri, 12 Mar 1999, Karl Denninger wrote:

> No.  It works properly.  I have had tables exceeding 10GB.

How does it get past an operating system limitation on file size?

Brett W. McCoy           
                                        http://www.lan2wan.com/~bmccoy/
-----------------------------------------------------------------------
If you float on instinct alone, how can you calculate the buoyancy for
the computed load?
		-- Christopher Hodder-Williams

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GAT dpu s:-- a C++++ UL++++$ P+ L+++ E W++ N+ o K- w--- O@ M@ !V PS+++
PE Y+ PGP- t++ 5- X+ R+@ tv b+++ DI+++ D+ G++ e>++ h+(---) r++ y++++
------END GEEK CODE BLOCK------




^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: [SQL] So what happens at 2GB?
@ 1999-03-13 20:17  Karl Denninger <karl@Denninger.Net>
  parent: Brett W. McCoy <bmccoy@lan2wan.com>
  0 siblings, 1 reply; 6+ messages in thread

From: Karl Denninger @ 1999-03-13 20:17 UTC (permalink / raw)
  To: Brett W. McCoy <bmccoy@lan2wan.com>; +Cc: Tim Perdue <perdue@raccoon.com>; pgsql-sql@hub.org

On Sat, Mar 13, 1999 at 01:11:23PM -0500, Brett W. McCoy wrote:
> On Fri, 12 Mar 1999, Karl Denninger wrote:
> 
> > No.  It works properly.  I have had tables exceeding 10GB.
> 
> How does it get past an operating system limitation on file size?
> 
> Brett W. McCoy           
>                                         http://www.lan2wan.com/~bmccoy/

There isn't one on FreeBSD, but Postgres doesn't seem to know that.
Instead, it breaks the table up into 2G-sized file chunks.

--
-- 
Karl Denninger (karl@denninger.net) http://www.mcs.net/~karl
I ain't even *authorized* to speak for anyone other than myself, so give
up now on trying to associate my words with any particular organization.



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: [SQL] So what happens at 2GB?
@ 1999-03-13 20:30  Brett W. McCoy <bmccoy@lan2wan.com>
  parent: Karl Denninger <karl@Denninger.Net>
  0 siblings, 0 replies; 6+ messages in thread

From: Brett W. McCoy @ 1999-03-13 20:30 UTC (permalink / raw)
  To: Karl Denninger <karl@Denninger.Net>; +Cc: Tim Perdue <perdue@raccoon.com>; pgsql-sql@hub.org

On Sat, 13 Mar 1999, Karl Denninger wrote:

> > > No.  It works properly.  I have had tables exceeding 10GB.
> > 
> > How does it get past an operating system limitation on file size?
> > 
> > Brett W. McCoy           
> >                                         http://www.lan2wan.com/~bmccoy/
> 
> There isn't one on FreeBSD, but Postgres doesn't seem to know that.
> Instead, it breaks the table up into 2G-sized file chunks.

It may do that for performance reasons, I would guess, or for
compatibility with other operating systems that have the limitation (like
Linux).

Brett W. McCoy           
                                        http://www.lan2wan.com/~bmccoy/
-----------------------------------------------------------------------
We are what we pretend to be.
		-- Kurt Vonnegut, Jr.

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GAT dpu s:-- a C++++ UL++++$ P+ L+++ E W++ N+ o K- w--- O@ M@ !V PS+++
PE Y+ PGP- t++ 5- X+ R+@ tv b+++ DI+++ D+ G++ e>++ h+(---) r++ y++++
------END GEEK CODE BLOCK------




^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: [SQL] So what happens at 2GB?
@ 1999-03-14 17:48  Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 6+ messages in thread

From: Tom Lane @ 1999-03-14 17:48 UTC (permalink / raw)
  To: pgsql-sql@hub.org

: "Brett W. McCoy" <bmccoy@lan2wan.com>
> On Sat, 13 Mar 1999, Karl Denninger wrote:
>>>>>> No.  It works properly.  I have had tables exceeding 10GB.
>>>> 
>>>> How does it get past an operating system limitation on file size?
>> 
>> There isn't one on FreeBSD, but Postgres doesn't seem to know that.
>> Instead, it breaks the table up into 2G-sized file chunks.
>
> It may do that for performance reasons, I would guess, or for
> compatibility with other operating systems that have the limitation

Precisely.

There was in fact a bug report against 6.4, that the feature failed to
work correctly on some OS's because the split point was *exactly* 2Gb;
apparently what works on these platforms is files less than 2Gb, not
files less-than-or-equal-to 2Gb.

6.5 will break tables into chunks a tad smaller than 2Gb in order to
avoid this problem; you might want to alter the RELSEG_SIZE constant
in /users/postgres/pgsql/src/backend/storage/smgr/md.c to do the same
in 6.4.

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 6+ messages in thread


end of thread, other threads:[~1999-03-14 17:48 UTC | newest]

Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1999-03-12 23:35 So what happens at 2GB? Tim Perdue <perdue@raccoon.com>
1999-03-12 23:56 ` Karl Denninger <karl@Denninger.Net>
1999-03-13 18:11   ` Brett W. McCoy <bmccoy@lan2wan.com>
1999-03-13 20:17     ` Karl Denninger <karl@Denninger.Net>
1999-03-13 20:30       ` Brett W. McCoy <bmccoy@lan2wan.com>
1999-03-14 17:48 Re: [SQL] So what happens at 2GB? Tom Lane <tgl@sss.pgh.pa.us>

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