From: Tom Lane <tgl@sss.pgh.pa.us>
To: ciprian.hodorogea@bitsp.com
Cc: pgsql-admin@postgresql.org
Subject: Re: pg_dump - txt sql vs binary
Date: Mon, 23 Jan 2006 10:56:40 -0500
Message-ID: <5773.1138031800@sss.pgh.pa.us> (raw)
In-Reply-To: <43D4E9A8.8050005@bitsp.com>
References: <20060122204132.9567D14DB13@mail07.powweb.com>
<22930.1137973880@sss.pgh.pa.us>
<43D4E9A8.8050005@bitsp.com>
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
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: tgl@sss.pgh.pa.us, ciprian.hodorogea@bitsp.com
Subject: Re: pg_dump - txt sql vs binary
In-Reply-To: <5773.1138031800@sss.pgh.pa.us>
References: <20060122204132.9567D14DB13@mail07.powweb.com> <22930.1137973880@sss.pgh.pa.us> <43D4E9A8.8050005@bitsp.com> <5773.1138031800@sss.pgh.pa.us>
* 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