Pg_dump behaviour - Mailing list pgsql-admin

From Hélder M. Vieira
Subject Pg_dump behaviour
Date
Msg-id 002c01c7389a$cba58590$6200a8c0@hmv02
Whole thread Raw
Responses Re: Pg_dump behaviour  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-admin
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:
When trying to backup a table contained in a specific schema, pg_dump can't
find the table.


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


Pg_dump then raises the following error:

pg_dump: No matching tables were found


I tried some alternatives from the command line, but pg_dump only seems to
make the single-table backup when the table name is qualified, as in:

pg_dump.exe -i -h localhost -p 5432 -U postgres -F c -v -f "c:\tefh" -t
art.tefh mdg


At this point, I'd say that the command generated by pgadmin should work, as
it seems to be consistent with pg_dump documentation. Any hints ?

Thank you.


Hélder M. Vieira


pgsql-admin by date:

Previous
From: "Shoaib Mir"
Date:
Subject: Re: Can not connect to database in Workgroup-Net on Windows-XP
Next
From: "Negandhi, Nishith"
Date:
Subject: Re: Database Create Date