Re: [HACKERS] "CANNOT EXTEND" -
От | Tim Perdue |
---|---|
Тема | Re: [HACKERS] "CANNOT EXTEND" - |
Дата | |
Msg-id | 001901be70d8$3f2b1ef0$0b8c5aa5@timnt.weather.net обсуждение исходный текст |
Ответы |
Re: [HACKERS] "CANNOT EXTEND" -
|
Список | pgsql-hackers |
It won't be long for me until that happens. Not long at all. Considering I've amassed 2.2 GB in just 3-4 weeks.... I'm really surprised to see that Linux has such a lame file limitation. I think even the macintosh can handle single files in the terabyte range now. Tim -----Original Message----- From: Bruce Momjian <maillist@candle.pha.pa.us> To: Peter T Mount <peter@retep.org.uk> Cc: perdue@raccoon.com <perdue@raccoon.com>; pgsql-hackers@hub.org <pgsql-hackers@hub.org> Date: Wednesday, March 17, 1999 5:29 PM Subject: Re: [HACKERS] "CANNOT EXTEND" - >> > 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@candle.pha.pa.us | (610) 853-3000 > + If your life is a hard drive, | 830 Blythe Avenue > + Christ can be your backup. | Drexel Hill, Pennsylvania 19026
В списке pgsql-hackers по дате отправления: