Re: pg_dump -C option

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Jim Buttafuoco <jim(at)buttafuoco(dot)net>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_dump -C option
Date: 2001-09-11 14:40:25
Message-ID: Pine.LNX.4.30.0109111639480.680-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jim Buttafuoco writes:

> will do.

While you're at it, at least the encoding parameter should be saved as
well. Take a peek at what pg_dumpall saves.

>
>
>
> > Jim Buttafuoco writes:
> >
> > > I am working a some patches to the code and I noticed that "pg_dump
> -C
> > > database" doesn't provide the database location information in the
> dump
> > > file. Is this correct?
> >
> > Your observation is correct, but the behaviour is not. Feel free to
> > send a patch.
> >
> > --
> > Peter Eisentraut peter_e(at)gmx(dot)net http://funkturm.homeip.net/~peter
> >
> >
> > ---------------------------(end of
> broadcast)---------------------------
> > TIP 1: subscribe and unsubscribe commands go to
> majordomo(at)postgresql(dot)org
> >
> >
>
>
>

--
Peter Eisentraut peter_e(at)gmx(dot)net http://funkturm.homeip.net/~peter

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2001-09-11 14:41:09 Re: COMMENT ON
Previous Message Florian Weimer 2001-09-11 14:22:55 Re: Escaping strings for inclusion into SQL queries