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 662109DC9A0 for ; Mon, 23 Jan 2006 11:57:34 -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 73587-03 for ; Mon, 23 Jan 2006 11:57:39 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from tigger.fuhr.org (tigger.fuhr.org [63.214.45.158]) by postgresql.org (Postfix) with ESMTP id BD9FB9DC97A for ; Mon, 23 Jan 2006 11:57:30 -0400 (AST) Received: from winnie.fuhr.org (winnie.fuhr.org [10.1.0.1]) by tigger.fuhr.org (8.13.3/8.13.3) with ESMTP id k0NFvUYG025712 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 23 Jan 2006 08:57:32 -0700 (MST) (envelope-from mfuhr@winnie.fuhr.org) Received: from winnie.fuhr.org (localhost [127.0.0.1]) by winnie.fuhr.org (8.13.4/8.13.4) with ESMTP id k0NFvTMa024183; Mon, 23 Jan 2006 08:57:29 -0700 (MST) (envelope-from mfuhr@winnie.fuhr.org) Received: (from mfuhr@localhost) by winnie.fuhr.org (8.13.4/8.13.4/Submit) id k0NFvTqK024182; Mon, 23 Jan 2006 08:57:29 -0700 (MST) (envelope-from mfuhr) Date: Mon, 23 Jan 2006 08:57:29 -0700 From: Michael Fuhr To: Ciprian Hodorogea Cc: Tom Lane , pgsql-admin@postgresql.org Subject: Re: pg_dump - txt sql vs binary Message-ID: <20060123155729.GA23544@winnie.fuhr.org> References: <20060122204132.9567D14DB13@mail07.powweb.com> <22930.1137973880@sss.pgh.pa.us> <43D4E9A8.8050005@bitsp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43D4E9A8.8050005@bitsp.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.107 required=5 tests=[AWL=0.107] X-Spam-Score: 0.107 X-Spam-Level: X-Archive-Number: 200601/267 X-Sequence-Number: 20355 On Mon, Jan 23, 2006 at 04:35:20PM +0200, Ciprian Hodorogea wrote: > >> 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? > > Is there a way to differentiate postgres internal functions from > user-defined functions? (other but making up a list of those functions > names) What "internal" functions are you talking about? What's the exact command you're running and what's the exact error message or unexpected behavior you're seeing? -- Michael Fuhr