From: Michael Fuhr <mike@fuhr.org>
To: Ciprian Hodorogea <ciprian.hodorogea@bitsp.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: pg_dump - txt sql vs binary
Date: Mon, 23 Jan 2006 08:57:29 -0700
Message-ID: <20060123155729.GA23544@winnie.fuhr.org> (raw)
In-Reply-To: <43D4E9A8.8050005@bitsp.com>
References: <20060122204132.9567D14DB13@mail07.powweb.com>
<22930.1137973880@sss.pgh.pa.us>
<43D4E9A8.8050005@bitsp.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: mike@fuhr.org, ciprian.hodorogea@bitsp.com, tgl@sss.pgh.pa.us
Subject: Re: pg_dump - txt sql vs binary
In-Reply-To: <20060123155729.GA23544@winnie.fuhr.org>
References: <20060122204132.9567D14DB13@mail07.powweb.com> <22930.1137973880@sss.pgh.pa.us> <43D4E9A8.8050005@bitsp.com> <20060123155729.GA23544@winnie.fuhr.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox