Re: BUG #17630: pg_dump error

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Christophe Pettus <xof(at)thebuild(dot)com>
Cc: killerwzb(at)163(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #17630: pg_dump error
Date: 2022-10-09 22:53:50
Message-ID: 3953507.1665356030@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Christophe Pettus <xof(at)thebuild(dot)com> writes:
>> On Oct 9, 2022, at 02:22, PG Bug reporting form <noreply(at)postgresql(dot)org> wrote:
>> I create table with a upper name ,it is "TABLE2" .I use pg_dump to dump
>> the table to a custom file,but i get some error.

> It's not a bug, but it's kind of an annoying situation. The double quotes on the command line just delimit the name of the table, but the shell strips them off (as you would expect), so pg_dump just gets the bare name. You have to add separate, escaped double-quotes, since the table name requires them:

Another way with slightly fewer keystrokes is

pg_dump ... --table '"TABLE2"'

Of course, if you're also in the habit of putting single-quotes in
your table names, that'll still need some work. The main point is
that there are two layers of quoting that you have to deal with:
the shell's, and then SQL's.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Erwin Brandstetter 2022-10-09 23:45:01 Default framing option RANGE adds cost for no gain to some window functions
Previous Message Christophe Pettus 2022-10-09 22:20:40 Re: BUG #17630: pg_dump error