Added to TODO:
* Have pg_dump -C dump database location and encoding
information
> 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 Buttafu
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 provi
will do.
> 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
> se
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 Eisent
All,
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?
Thanks
Jim
Example:
datname | datdba | encoding | datistemplate | datallowconn |
datlastsysoid | datpath | idxpath
--
All,
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?
Thanks
Jim
Example:
datname | datdba | encoding | datistemplate | datallowconn |
datlastsysoid | datpath | idxpath
-
