From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Hélder M(dot) Vieira <hmv(at)mail(dot)telepac(dot)pt> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Pg_dump behaviour |
Date: | 2007-01-15 15:39:18 |
Message-ID: | 15638.1168875558@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
"=?iso-8859-1?Q?H=E9lder_M._Vieira?=" <hmv(at)mail(dot)telepac(dot)pt> writes:
> I often perform single-table backups using pgadmin.
> Recently, a problem occurred while doing that kind of backup using pgadmin
> 1.6.2 and PostgreSQL 8.2.1 on a Windows server:
> For instance, I have a database named 'mdg', containing a schema named
> 'art', in turn containing a table named 'tefh'.
> When I try to backup this table to the root directory with pgadmin, it
> generates and executes the following command:
> pg_dump.exe -i -h localhost -p 5432 -U postgres -F c -v -f "c:\tefh" -t
> tefh -n art mdg
That was the pre-8.2 way to do it; now the right thing would be
-t art.tefh
Sounds like pgadmin needs an update. While they're at it, they should
definitely lose the -i switch ... using that by default is extremely
stupid/dangerous.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Donald Fraser | 2007-01-15 17:13:45 | PL/pgSQL Return statements |
Previous Message | Negandhi, Nishith | 2007-01-15 14:36:16 | Re: Database Create Date |