On Wednesday 13 December 2000 20:43, rob wrote:
> Why is pg_dump not correct? You need to elaborate on the parameters of the
> situation.
It's fine. It might be nice if it had an option to dump functions into a
separate file. Something like
pg_dump -l mydb > mydb.tables.sql
Just TABLE and SEQUENCE definitions.
pg_dump -a mydb > mydb.data.sql
Just the data.
pg_dump -f mydb > mydb.functions.sql
Everything else that a pg_dump -s gives
after the last TABLE is dumped.
Those three files would be everything needed to restore: first the tables,
then the data, then the functions etc. Like if, you wanted, you could cat
the files together to get a complete dump file. Maybe it's a bad idea?
>
> --rob
>
>
> ----- Original Message -----
> From: <pgsql-general-owner@postgresql.org>
> To: <pgsql-general@postgresql.org>
> Sent: Wednesday, December 13, 2000 6:26 PM
> Subject: Daily Digest V1 #108
>
> > Daily Digest (mime) - Volume 1 : Issue 108
> >
> > Today's Topics:
> > RE: Postgres failover implementation
> > ERD on the cheap?
> > Re: ERD on the cheap?
> > Re: ERD on the cheap?
> > Re: TOAST & performance with lots of big columns in a table
> > docs
> > RI and restoring dumps
> > Re: RI and restoring dumps
> > Re: RI and restoring dumps
> > Re: Help!Can't connect Postgresql JDBC driver
> > How to import/export data from/to an ASCII file?
> > Re: RI and restoring dumps
> > Re: Help!Can't connect Postgresql JDBC driver
--
-------- Robert B. Easter reaster@comptechnews.com ---------
- CompTechNews Message Board http://www.comptechnews.com/ -
- CompTechServ Tech Services http://www.comptechserv.com/ -
---------- http://www.comptechnews.com/~reaster/ ------------