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 9DD159DC806 for ; Mon, 23 Jan 2006 10:35:21 -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 59177-01 for ; Mon, 23 Jan 2006 10:35:25 -0400 (AST) X-Greylist: delayed 17:53:49.286311 by SQLgrey- Received: from mail07.powweb.com (mail07.powweb.com [66.152.97.40]) by postgresql.org (Postfix) with ESMTP id 399349DC809 for ; Mon, 23 Jan 2006 10:35:16 -0400 (AST) Received: from [10.1.0.10] (unknown [82.76.86.38]) by mail07.powweb.com (Postfix) with ESMTP id DCF4E14DBE3; Mon, 23 Jan 2006 06:35:18 -0800 (PST) Message-ID: <43D4E9A8.8050005@bitsp.com> Date: Mon, 23 Jan 2006 16:35:20 +0200 From: Ciprian Hodorogea Reply-To: ciprian.hodorogea@bitsp.com Organization: IntelliSoft SRL User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Lane CC: pgsql-admin@postgresql.org Subject: Re: pg_dump - txt sql vs binary References: <20060122204132.9567D14DB13@mail07.powweb.com> <22930.1137973880@sss.pgh.pa.us> In-Reply-To: <22930.1137973880@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0 required=5 tests=[none] X-Spam-Score: 0 X-Spam-Level: X-Archive-Number: 200601/265 X-Sequence-Number: 20353 >> 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) Regards, Ciprian