Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Troubles dumping a very large table.
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: Ted Allen <tallen(at)blackducksoftware(dot)com>
- Cc: "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
- Subject: Re: Troubles dumping a very large table.
- Date: Fri, 26 Dec 2008 12:38:38 -0500
- Message-id: <13141.1230313118@sss.pgh.pa.us> <text/plain>
Ted Allen <tallen(at)blackducksoftware(dot)com> writes: > 600mb measured by get_octet_length on data. If there is a better way to measure the row/cell size, please let me know because we thought it was the >1Gb problem too. We thought we were being conservative by getting rid of the larger rows but I guess we need to get rid of even more. Yeah, the average expansion of bytea data in COPY format is about 3X :-( So you need to get the max row length down to around 300mb. I'm curious how you got the data in to start with --- were the values assembled on the server side? regards, tom lane
- Follow-Ups:
- Re: Troubles dumping a very large table.
- From: Merlin Moncure
- Re: Troubles dumping a very large table.
- References:
- Troubles dumping a very large table.
- From: Ted Allen
- Re: Troubles dumping a very large table.
- From: Tom Lane
- Re: Troubles dumping a very large table.
- From: Ted Allen
- Troubles dumping a very large table.
- Prev by Date: Re: Troubles dumping a very large table.
- Next by Date: Re: Troubles dumping a very large table.
- Previous by thread: Re: Troubles dumping a very large table.
- Next by thread: Re: Troubles dumping a very large table.
- Indexes: