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

From Tom Lane
Subject Re: pg_dump - txt sql vs binary
Date
Msg-id 5773.1138031800@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_dump - txt sql vs binary  (Ciprian Hodorogea <ciprian.hodorogea@bitsp.com>)
List pgsql-admin
Ciprian Hodorogea <ciprian.hodorogea@bitsp.com> 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

pgsql-admin by date:

Previous
From: Ciprian Hodorogea
Date:
Subject: Re: pg_dump - txt sql vs binary
Next
From: Michael Fuhr
Date:
Subject: Re: pg_dump - txt sql vs binary