From: | Peter T Mount <peter(at)retep(dot)org(dot)uk> |
---|---|
To: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | perdue(at)raccoon(dot)com, pgsql-hackers(at)hub(dot)org |
Subject: | Re: [HACKERS] "CANNOT EXTEND" - |
Date: | 1999-03-17 23:17:11 |
Message-ID: | Pine.LNX.4.04.9903172312050.16622-100000@maidast.retep.org.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 15 Mar 1999, Bruce Momjian wrote:
> [Charset iso-8859-1 unsupported, filtering to ASCII...]
> > Thanks Bruce.
> >
> > Do you have any idea what happens with pg_dump when it hits 2GB??? Is it set
> > up to segment the files on linux? If not, I may have hit a brick wall here,
> > and have no way to back this baby up.
> >
>
> 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.
Also, I think we could do with having some standard way of dumping and
restoring large objects.
--
Peter T Mount peter(at)retep(dot)org(dot)uk
Main Homepage: http://www.retep.org.uk
PostgreSQL JDBC Faq: http://www.retep.org.uk/postgres
Java PDF Generator: http://www.retep.org.uk/pdf
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1999-03-17 23:23:18 | Re: [HACKERS] "CANNOT EXTEND" - |
Previous Message | Bruce Momjian | 1999-03-17 23:09:03 | Re: [HACKERS] New postgres -O option for system tables |