Talk About Network

Google




Play Stock Market Games
Fantasy Stock Picking Contest

Data Bases > Pgsql Admin > pg_dump 8.3 cha...
Latest [ Topics | Posts ] Archive Post A New Topic Post a Reply
<< Topic < Post Post 1 of 2 Topic 4976 of 5167
Post > Topic >>

pg_dump 8.3 changes from 8.2

by denisonwright@[EMAIL PROTECTED] ("Denison Wright") May 11, 2008 at 02:12 PM

------=_Part_592_16180235.1210529538284
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

 <pgsql-admin@[EMAIL PROTECTED]
>
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 do***entation
online.
If something changed, what is the appropriate parameter sequence to make
that work?

Thanks,

Denison

------=_Part_592_16180235.1210529538284
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<a href="mailto:pgsql-admin@[EMAIL PROTECTED]
"></a><br>Hi,<br><br>I had a
command that I used with Postgresql 8.2 that stopped working once I
upgraded to 8.3.<br>I am running Postgresql 8.3 on Windows Vista with the
following basic configuration:<br>
<ul><li>database: mydb</li><li>user: mydbuser</li><li>password:
mydbpassword</li><li>schema:myschema</li><li>table:
mytable<br></li></ul>When I run the following commands:<br><br>&gt;set
PGPASSWORD=mydbpassword<br>&gt;pg_dump mydb -U mydbuser -a -f backup.sql
-F plain -t &#39;myschema.mytable&#39;<br>
<br>I get the following error now: &quot;pg_dump: too many command-line
arguments&quot;<br><br>Then, I tried the following to see what would
happen:<br><br>&gt;set PGPASSWORD=mydbpassword<br>&gt;set PGDATABASE=mydb
<br>&gt;pg_dump --username=mydbuser --format=p
--table=&#39;myschema.mytable&#39; --verbose --data-only
--file=backup.sql<br>
<br>Error:<br>dump: No matching tables were found<br>dump: *** aborted
because of error<br><br><br>Does anyone know if there were changes from
8.2 to 8.3 that would cause the above command to stop working? I
couldn&#39;t tell from the 8.3 do***entation online.<br>
If something changed, what is the appropriate parameter sequence to make
that work?<br><br>Thanks,<br><br>Denison<br>

------=_Part_592_16180235.1210529538284--
 




 2 Posts in Topic:
pg_dump 8.3 changes from 8.2
denisonwright@[EMAIL PROT  2008-05-11 14:12:18 
Re: pg_dump 8.3 changes from 8.2
milen@[EMAIL PROTECTED]   2008-05-12 14:46:41 

Post A Reply:
  Go here to Signup

AddThis Feed Button


About - Advertising - Contact - Frequently Asked Questions - Privacy Policy - Terms of Use - Signup

Contact
tan13V112 Fri Aug 8 13:20:58 CDT 2008.