Re: pg_dump - txt sql vs binary

From: Michael Fuhr <mike(at)fuhr(dot)org>
To: Ciprian Hodorogea <ciprian(dot)hodorogea(at)bitsp(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-admin(at)postgresql(dot)org
Subject: Re: pg_dump - txt sql vs binary
Date: 2006-01-23 15:57:29
Message-ID: 20060123155729.GA23544@winnie.fuhr.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Michael Fuhr 2006-01-23 16:44:21 Re: Full Text Indexing Using Tsearch2-Module
Previous Message Tom Lane 2006-01-23 15:56:40 Re: pg_dump - txt sql vs binary