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 C75829DC998 for ; Sun, 22 Jan 2006 16:41:35 -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 47970-04 for ; Sun, 22 Jan 2006 16:41:35 -0400 (AST) Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 959D09DC9CA for ; Sun, 22 Jan 2006 16:41:32 -0400 (AST) Received: from mail07.powweb.com (mail07.powweb.com [66.152.97.40]) by svr4.postgresql.org (Postfix) with ESMTP id 87AE65AF83A for ; Sun, 22 Jan 2006 20:41:34 +0000 (GMT) Received: from hodoman (home-307494.b.astral.ro [193.231.126.246]) by mail07.powweb.com (Postfix) with ESMTP id 9567D14DB13 for ; Sun, 22 Jan 2006 12:41:32 -0800 (PST) Reply-To: From: "Ciprian Hodorogea" To: Subject: pg_dump - txt sql vs binary Date: Sun, 22 Jan 2006 22:41:27 +0200 Organization: IntelliSoft SRL MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0028_01C61FA4.FCA383F0" X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: AcYflDewaAMLez3yQ6ucWNsP/jb6dA== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Message-Id: <20060122204132.9567D14DB13@mail07.powweb.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.001 required=5 tests=[HTML_MESSAGE=0.001] X-Spam-Score: 0.001 X-Spam-Level: X-Archive-Number: 200601/258 X-Sequence-Number: 20346 This is a multi-part message in MIME format. ------=_NextPart_000_0028_01C61FA4.FCA383F0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi All, 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. 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? All I want is to obtain a valid SQL file that I can then import within any upcoming version of Postgres. Does anyone have any suggestion please? Best regards, Ciprian Hodorogea IntelliSoft SRL http://www.bitsp.com/ ------=_NextPart_000_0028_01C61FA4.FCA383F0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi All,

 

  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.

 

  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? =

 

  All I want is to obtain a valid SQL file = that I can then import within any upcoming version of Postgres.  Does anyone = have any suggestion please?

 

Best regards,

 

Ciprian Hodorogea

IntelliSoft = SRL

http://www.bitsp.com/

 

------=_NextPart_000_0028_01C61FA4.FCA383F0--