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 DBEB59DC8A2 for ; Mon, 23 Jan 2006 11:56:42 -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 72796-07 for ; Mon, 23 Jan 2006 11:56:44 -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 3ADE59DC813 for ; Mon, 23 Jan 2006 11:56:37 -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 k0NFueUo005774; Mon, 23 Jan 2006 10:56:41 -0500 (EST) To: ciprian.hodorogea@bitsp.com cc: pgsql-admin@postgresql.org Subject: Re: pg_dump - txt sql vs binary In-reply-to: <43D4E9A8.8050005@bitsp.com> References: <20060122204132.9567D14DB13@mail07.powweb.com> <22930.1137973880@sss.pgh.pa.us> <43D4E9A8.8050005@bitsp.com> Comments: In-reply-to Ciprian Hodorogea message dated "Mon, 23 Jan 2006 16:35:20 +0200" Date: Mon, 23 Jan 2006 10:56:40 -0500 Message-ID: <5773.1138031800@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/266 X-Sequence-Number: 20354 Ciprian Hodorogea writes: > 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) I can think of several possibilities, but it's not clear what you need to accomplish. Would you show us details of the problem you're having, rather than jumping to conclusions about how to fix it? Bear in mind that the rest of the world has found no need to do any such thing while using pg_dump. regards, tom lane