Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 529199F9F7B for ; Fri, 1 Dec 2006 21:36:20 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024) with ESMTP id 12248-07 for ; Fri, 1 Dec 2006 21:36:19 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by postgresql.org (Postfix) with ESMTP id A0DA29FA0CC for ; Fri, 1 Dec 2006 21:36:19 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.13.8/8.13.8) with ESMTP id kB21aJP5014918 for ; Fri, 1 Dec 2006 21:36:19 -0400 (AST) (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.13.8/8.13.8/Submit) id kB21ID8x010057 for pgsql-admin@postgresql.org; Fri, 1 Dec 2006 21:18:13 -0400 (AST) (envelope-from news) From: Peter Wilson X-Newsgroups: pgsql.admin Subject: Re: Problem restoring with pg_dump Date: Sat, 02 Dec 2006 01:18:09 +0000 Organization: Hub.Org Networking Services Lines: 39 Message-ID: <4570D451.1070907@yellowhawk.co.uk> References: <6113.1164728816@sss.pgh.pa.us> <1693.1165001565@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@news.hub.org To: Tom Lane User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) In-Reply-To: <1693.1165001565@sss.pgh.pa.us> X-Enigmail-Version: 0.94.0.0 X-Antivirus: avast! (VPS 0652-6, 01/12/2006), Outbound message X-Antivirus-Status: Clean To: pgsql-admin@postgresql.org X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200612/17 X-Sequence-Number: 23809 Tom Lane wrote: > Peter Wilson writes: >> Tom Lane wrote: >>> Could you show us the unmodified output from pg_restore -l, as well as >>> the edits you made to produce the -L script? > >> Raw output from pg_restore -l is as follows: > > Hm, this shows only data entries. Was the original pg_dump made with -a, > or did you use -a in the pg_restore -l command? If the latter, could we > see the full -l output? I didn't have any luck trying to reproduce this > behavior, so I'm supposing it depends on something you haven't shown us... I may end up duplicating myself here - seem to be having lots of problems with the Postgres new server so apologies. The data file is from a live server and has been steadily growing. It's 1.2Gbytes(ish) in size. It was built with --compress=9. Does Postgres uncompress this to something bigger than 2Gbytes before processing and busting what can be referenced in a 32 bit seek value? What happens (in Linux) when you try to open a file that is bigger than 2Gbytes - do you loose the ability to seek? I've just taken apart the schema def. from pg_dump --schema-only and inserted the data-restore after the tables are created but before indices/constraints/rules are replied. in this case I don't have to re-order the tables. Restore doesn't seem to be having problems in this case - although the restore will take a good while to complete. This is with the same dump file that failed before. Pete > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 1: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly >