From: Tom Lane <tgl@sss.pgh.pa.us>
To: Christophe Pettus <xof@thebuild.com>
cc: killerwzb@163.com,
        PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #17630: pg_dump error
In-reply-to: <3B75DF91-FB87-4580-88CD-AF6B78ABFA80@thebuild.com>
References: <17630-0947c0a5aa573243@postgresql.org>
 <3B75DF91-FB87-4580-88CD-AF6B78ABFA80@thebuild.com>
Comments: In-reply-to Christophe Pettus <xof@thebuild.com>
	message dated "Sun, 09 Oct 2022 15:20:40 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3953506.1665356030.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sun, 09 Oct 2022 18:53:50 -0400
Message-ID: <3953507.1665356030@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3953507.1665356030%40sss.pgh.pa.us>
Precedence: bulk

Christophe Pettus <xof@thebuild.com> writes:
>> On Oct 9, 2022, at 02:22, PG Bug reporting form <noreply@postgresql.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 quot=
es on the command line just delimit the name of the table, but the shell s=
trips 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 req=
uires 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