Thread: Re: Daily Digest V1 #108

Re: Daily Digest V1 #108

From
"rob"
Date:
Why is pg_dump not correct?  You need to elaborate on the parameters of the
situation.

--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
>


Re: Re: Daily Digest V1 #108

From
"Robert B. Easter"
Date:
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/ ------------

Re: Re: Daily Digest V1 #108

From
"rob"
Date:
It has (most) of those options.

  -a, --data-only          dump out only the data, not the schema
  -c, --clean              clean (drop) schema prior to create
  -d, --inserts            dump data as INSERT, rather than COPY, commands
  -D, --attribute-inserts  dump data as INSERT commands with attribute names
  -h, --host <hostname>    server host name
  -i, --ignore-version     proceed when database version != pg_dump version
  -n, --no-quotes          suppress most quotes around identifiers
  -N, --quotes             enable most quotes around identifiers
  -o, --oids               dump object ids (oids)
  -p, --port <port>        server port number
  -s, --schema-only        dump out only the schema, no data
  -t, --table <table>      dump for this table only
  -u, --password           use password authentication
  -v, --verbose            verbose
  -x, --no-acl             do not dump ACL's (grant/revoke)



--rob

----- Original Message -----
From: "Robert B. Easter" <reaster@comptechnews.com>
To: "rob" <rob@cabrion.com>; <pgsql-general-owner@postgresql.org>;
<pgsql-general@postgresql.org>
Sent: Wednesday, December 13, 2000 11:32 PM
Subject: Re: [GENERAL] Re: Daily Digest V1 #108


> 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/ ------------
>