Re: pg_dump - txt sql vs binary - Mailing list pgsql-admin

From Michael Fuhr
Subject Re: pg_dump - txt sql vs binary
Date
Msg-id 20060123155729.GA23544@winnie.fuhr.org
Whole thread Raw
In response to Re: pg_dump - txt sql vs binary  (Ciprian Hodorogea <ciprian.hodorogea@bitsp.com>)
Responses Re: pg_dump - txt sql vs binary  (Ciprian Hodorogea <ciprian.hodorogea@bitsp.com>)
List pgsql-admin
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

pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_dump - txt sql vs binary
Next
From: Michael Fuhr
Date:
Subject: Re: Full Text Indexing Using Tsearch2-Module