X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 5A9029DC89E for ; Sun, 22 Jan 2006 19:51:22 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 75284-06 for ; Sun, 22 Jan 2006 19:51:24 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id F07729DC86D for ; Sun, 22 Jan 2006 19:51:19 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id k0MNpKLa022931; Sun, 22 Jan 2006 18:51:20 -0500 (EST) To: ciprian.hodorogea@bitsp.com cc: pgsql-admin@postgresql.org Subject: Re: pg_dump - txt sql vs binary In-reply-to: <20060122204132.9567D14DB13@mail07.powweb.com> References: <20060122204132.9567D14DB13@mail07.powweb.com> Comments: In-reply-to "Ciprian Hodorogea" message dated "Sun, 22 Jan 2006 22:41:27 +0200" Date: Sun, 22 Jan 2006 18:51:20 -0500 Message-ID: <22930.1137973880@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.096 required=5 tests=[AWL=0.096] X-Spam-Score: 0.096 X-Spam-Level: X-Archive-Number: 200601/259 X-Sequence-Number: 20347 "Ciprian Hodorogea" writes: > 1. I noticed that binary dumps created with Postgres 8.0.3 can not be > imported with Postgres 8.1.x, so this is not a good backup idea. If you mean a filesystem dump, no. > 2. All dumps generated with pg_dump seem to contain internal functions > also, which then raise problems when trying to import. Can these be somehow > excluded from the generated SQL backup? Details please? regards, tom lane