From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Kevin Neufeld <kneufeld(at)refractions(dot)net> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #3377: pg_dump: No matching tables were found |
Date: | 2007-06-08 18:13:04 |
Message-ID: | 20070608181304.GN9071@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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)
From | Date | Subject | |
---|---|---|---|
Next Message | Christian Gonzalez | 2007-06-08 19:34:03 | Re: BUG #3377: pg_dump: No matching tables were found |
Previous Message | Kevin Neufeld | 2007-06-08 16:59:01 | BUG #3377: pg_dump: No matching tables were found |