Re: BUG #4957: search_path and pg_dump -T switch - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #4957: search_path and pg_dump -T switch
Date
Msg-id 18556.1249048783@sss.pgh.pa.us
Whole thread Raw
In response to BUG #4957: search_path and pg_dump -T switch  ("Maxim.Boguk" <maxim.boguk@gmail.com>)
List pgsql-bugs
"Maxim.Boguk" <maxim.boguk@gmail.com> writes:
> Now we have table test1 with one row outside of search_path and table test2
> with one row inside of search path.

> Now
> pg_dump -F p -D -T test1 -a test_db | grep test1
> will out:
> INSERT INTO test1 (id) VALUES (1);

> And
> pg_dump -F p -D -T test2 -a test_db | grep test2
> will out empty.

> First result is wrong.

No, I don't believe it is.  The switch means "don't dump the table named
test1 as found in your search path".  So in this case it doesn't do
anything.  You could do "-T test.test1" or "-T *.test1" if you want to
suppress that table.

We could have pg_dump throw an error if -t or -T doesn't seem to refer
to any actual table, but I'm not sure that would make it more useful.
Particularly not with wild-card-pattern switches.

            regards, tom lane

pgsql-bugs by date:

Previous
From: "Maxim.Boguk"
Date:
Subject: BUG #4957: search_path and pg_dump -T switch
Next
From: Tom Lane
Date:
Subject: Re: BUG #4956: Array Construct array() returning blank result