From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | ciprian(dot)hodorogea(at)bitsp(dot)com |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: pg_dump - txt sql vs binary |
Date: | 2006-01-23 15:56:40 |
Message-ID: | 5773.1138031800@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Ciprian Hodorogea <ciprian(dot)hodorogea(at)bitsp(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Fuhr | 2006-01-23 15:57:29 | Re: pg_dump - txt sql vs binary |
Previous Message | Karthi Kannan | 2006-01-23 15:51:13 | Importing data into postgres through PGADMIN |