From: Denison Wright <denisonwright@gmail.com>
To: pgsql-admin@postgresql.org
Subject: pg_dump 8.3 changes from 8.2
Date: Sun, 11 May 2008 14:12:18 -0400
Message-ID: <8b3ae1cc0805111112h53156be3nbb5d6ce1cb8bc433@mail.gmail.com> (raw)
<pgsql-admin@postgresql.org>
Hi,
I had a command that I used with Postgresql 8.2 that stopped working once I
upgraded to 8.3.
I am running Postgresql 8.3 on Windows Vista with the following basic
configuration:
- database: mydb
- user: mydbuser
- password: mydbpassword
- schema:myschema
- table: mytable
When I run the following commands:
>set PGPASSWORD=mydbpassword
>pg_dump mydb -U mydbuser -a -f backup.sql -F plain -t 'myschema.mytable'
I get the following error now: "pg_dump: too many command-line arguments"
Then, I tried the following to see what would happen:
>set PGPASSWORD=mydbpassword
>set PGDATABASE=mydb
>pg_dump --username=mydbuser --format=p --table='myschema.mytable' --verbose
--data-only --file=backup.sql
Error:
dump: No matching tables were found
dump: *** aborted because of error
Does anyone know if there were changes from 8.2 to 8.3 that would cause the
above command to stop working? I couldn't tell from the 8.3 documentation
online.
If something changed, what is the appropriate parameter sequence to make
that work?
Thanks,
Denison
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: denisonwright@gmail.com
Subject: Re: pg_dump 8.3 changes from 8.2
In-Reply-To: <8b3ae1cc0805111112h53156be3nbb5d6ce1cb8bc433@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox