Re: pg_dump -t option doesn't take schema-qualified table

From: Curt Sampson <cjs(at)cynic(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: pg_dump -t option doesn't take schema-qualified table
Date: 2003-07-02 02:52:49
Message-ID: Pine.NEB.4.51.0307021150170.415@angelic-vtfw.cvpn.cynic.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, 1 Jul 2003, Tom Lane wrote:

> Curt Sampson <cjs(at)cynic(dot)net> writes:
> > It appears that the command "pgsql -t foo.bar" will not dump the table
> > bar in the schema foo. I saw a patch a while back to add schema support
> > to pg_dump (with the --namespace option), but I did not see a fix for
> > this.
>
> IMO that's not a bug; you should spell it pg_dump -n foo -t bar.
> The other way is ambiguous with a table named "foo.bar".

Oh, I didn't realize that dots are allowed in table names. But is there
an unambiguous way to specify a specific table in a database if you
don't know your search path? Would that be "foo"."bar" (table bar in
schema foo) as opposed to "foo.bar" (table foo.bar in current schema, if
extant)? If so, then pg_dump -t '"foo"."bar"' would do the right thing,
I'd hope.

If there's no way to unambiguously specify a table name, that rather
worries me....

cjs
--
Curt Sampson <cjs(at)cynic(dot)net> +81 90 7737 2974 http://www.netbsd.org
Don't you know, in this new Dark Age, we're all light. --XTC

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2003-07-02 04:20:52 Re: pg_dump -t option doesn't take schema-qualified table names
Previous Message Jean-Christian Imbeault 2003-07-02 02:45:56 Bug in japanese charset mappings?