Skip site navigation (1) Skip section navigation (2)

BUG #3377: pg_dump: No matching tables were found

From: "Kevin Neufeld" <kneufeld(at)refractions(dot)net>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #3377: pg_dump: No matching tables were found
Date: 2007-06-08 16:59:01
Message-ID: 200706081659.l58Gx1IU000683@wwwmaster.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-bugs
The following bug has been logged online:

Bug reference:      3377
Logged by:          Kevin Neufeld
Email address:      kneufeld(at)refractions(dot)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 ...

Responses

pgsql-bugs by date

Next:From: Alvaro HerreraDate: 2007-06-08 18:13:04
Subject: Re: BUG #3377: pg_dump: No matching tables were found
Previous:From: Alvaro HerreraDate: 2007-06-08 15:00:50
Subject: Re: BUG #3326: Invalid lower bound of autovacuum_cost_limit

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group