Re: BUG #3377: pg_dump: No matching tables were found - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: BUG #3377: pg_dump: No matching tables were found
Date
Msg-id 20070608181304.GN9071@alvh.no-ip.org
Whole thread Raw
In response to BUG #3377: pg_dump: No matching tables were found  ("Kevin Neufeld" <kneufeld@refractions.net>)
List pgsql-bugs
Kevin Neufeld wrote:

> $ pg_dump -U postgres -t mytable postgres | less
> pg_dump: No matching tables were found
>
> $ pg_dump -U postgres -n test -t mytable postgres | less
> pg_dump: No matching tables were found

Try pg_dump -t test.mytable

Then check the docs of the new version, which state

: Note:  The behavior of the -t switch is not entirely upward compatible
: with pre-8.2 PostgreSQL versions. Formerly, writing -t tab would dump
: all tables named tab, but now it just dumps whichever one is visible in
: your default search path. To get the old behavior you can write -t
: '*.tab'. Also, you must write something like -t sch.tab to select a
: table in a particular schema, rather than the old locution of -n sch -t
: tab.

http://www.postgresql.org/docs/8.2/static/app-pgdump.html

--
Alvaro Herrera                         http://www.flickr.com/photos/alvherre/
"Nunca confiaré en un traidor.  Ni siquiera si el traidor lo he creado yo"
(Barón Vladimir Harkonnen)

pgsql-bugs by date:

Previous
From: "Kevin Neufeld"
Date:
Subject: BUG #3377: pg_dump: No matching tables were found
Next
From: Christian Gonzalez
Date:
Subject: Re: BUG #3377: pg_dump: No matching tables were found