Sorry! Meant pg_dump to dump and cat myfile.txt | psql mydatabase to restore. I have dumped just the offending table out as a separate file but this makes no odds. I seem to recall that last time I tried pg_dump in compressed format under 7.1.3 it wouldn't restore so I haven't tried that.
I can dump without any problem in 7.1.3 eg pg_dump -t bigtable -d mydb -f mybigtable.txt and, as I said, this file restores OK on the 7.1.3 version running under RH Linux 6.2 using cat mybigtable | psql newdatabase but I can't load it on my new 7.4 installation under RH Linux 9 with the same script - I get the memory problem. I guess I'll have to split the output file into chunks but I was hoping not to have to do that. Hilary At 14:27 07/07/2004 -0400, Michael Adler wrote: >On Wed, Jul 07, 2004 at 04:28:53PM +0100, Hilary Forbes wrote: > >> ... when I run pg_dump to restore the data, one table with approx >> 5.5 million records gives me >> >> ERROR: invalid memory alloc request size 1073741824 > >What do you mean "pg_dump to restore the data"? One would normally use >psql or pg_restore to actually "restore" the data. > >In the past, that error message indicated some corrupted data that >prevents a reading one or more rows in a table (and therefore prevents >a pg_dump). But you seem to be saying that you can regularly dump that >table without any problems. > >When can you dump the table? And when can you not dump the table? > >-Mike > > >---------------------------(end of broadcast)--------------------------- >TIP 3: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to [EMAIL PROTECTED] so that your > message can get through to the mailing list cleanly Hilary Forbes The DMR Information and Technology Group (www.dmr.co.uk) Direct tel 01689 889950 Fax 01689 860330 DMR is a UK registered trade mark of DMR Limited ********************************************************** ---------------------------(end of broadcast)--------------------------- TIP 8: explain analyze is your friend
