Re: pg_restore - added documentation

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Harald Armin Massa <ghum(at)gmx(dot)net>, pgsql-patches(at)postgresql(dot)org
Subject: Re: pg_restore - added documentation
Date: 2004-10-13 00:42:42
Message-ID: 200410130042.i9D0ggI04428@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Peter Eisentraut wrote:
> Harald Armin Massa wrote:
> > ----------------------------------------------
> > Usage:
> > pg_restore [OPTION]... [FILE]
> >
> > General options:
> > -d, --dbname=NAME output database name (to restore into a psql
> > database)
> > -f, --file=FILENAME output file name (to convert custom/tar to
> > plain SQL)
> > -F, --format=c|t specify backup file format (custom or tar,
> > plain text is not possible)
> > ----------------------------------------------
>
> These lines are too long for help output. Also, there is no such thing
> as a "psql database".

Agreed.

However, I wonder if "output database" is the proper name for -d? Isn't
it more "restore database" or "target database"? Output makes me think
of pg_dump.

pg_restore manual page has for -d:

--dbname=dbname
Connect to database dbname and restore directly
into the database.

No mention of "output" there.

I have updated some of the help wording for pg_restore which should clarify
things.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

Attachment Content-Type Size
unknown_filename text/plain 3.1 KB

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2004-10-13 00:53:04 Re: [HACKERS] PGPASSWORD and client tools
Previous Message Noreen Jaster 2004-10-12 23:50:59 Re: Static build of libpq fails