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

From Kevin Neufeld
Subject BUG #3377: pg_dump: No matching tables were found
Date
Msg-id 200706081659.l58Gx1IU000683@wwwmaster.postgresql.org
Whole thread Raw
Responses Re: BUG #3377: pg_dump: No matching tables were found  (Alvaro Herrera <alvherre@commandprompt.com>)
Re: BUG #3377: pg_dump: No matching tables were found  (Christian Gonzalez <christian.gonzalez@sigis.com.ve>)
List pgsql-bugs
The following bug has been logged online:

Bug reference:      3377
Logged by:          Kevin Neufeld
Email address:      kneufeld@refractions.net
PostgreSQL version: 8.2.4
Operating system:   Linux Fedora Core 3
Description:        pg_dump: No matching tables were found
Details:

pg_dump does not seem to use -n to qualify a table dump.

$ psql -U postgres -c "create schema test" postgres
CREATE SCHEMA

$ psql -U postgres -c "create table test.mytable()" postgres
CREATE TABLE

$ 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

$ psql -U postgres -c "alter user postgres set search_path to test, public"
postgres
ALTER ROLE

$ pg_dump -U postgres -n test -t mytable postgres | less
--
-- PostgreSQL database dump
--

SET client_encoding = 'UTF8';
SET ...

pgsql-bugs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: BUG #3326: Invalid lower bound of autovacuum_cost_limit
Next
From: Alvaro Herrera
Date:
Subject: Re: BUG #3377: pg_dump: No matching tables were found