Re: [HACKERS] "CANNOT EXTEND" -

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: peter(at)retep(dot)org(dot)uk (Peter T Mount)
Cc: perdue(at)raccoon(dot)com, pgsql-hackers(at)hub(dot)org
Subject: Re: [HACKERS] "CANNOT EXTEND" -
Date: 1999-03-17 23:23:18
Message-ID: 199903172323.SAA21180@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> > pg_dump only dumps a flat unix file. That can be any size your OS
> > supports. It does not segment. However, a 2gig table will dump to a
> > much smaller version than 2gig because of the overhead for every record.
>
> Hmmm, I think that, as some people are now using >2Gig tables, we should
> think of adding segmentation to pg_dump as an option, otherwise this is
> going to become a real issue at some point.

So the OS doesn't get a table over 2 gigs. Does anyone have a table
that dumps a flat file over 2gig's, whose OS can't support files over 2
gigs. Never heard of a complaint.

>
> Also, I think we could do with having some standard way of dumping and
> restoring large objects.

I need to add a separate large object type.
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Clark Evans 1999-03-17 23:43:30 OID vs SERIAL? (Was: Re: [HACKERS] Sequences....)
Previous Message Peter T Mount 1999-03-17 23:17:11 Re: [HACKERS] "CANNOT EXTEND" -