Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
Subject: Re: BUG #17630: pg_dump error
From: Christophe Pettus <xof@thebuild.com>
In-Reply-To: <17630-0947c0a5aa573243@postgresql.org>
Date: Sun, 9 Oct 2022 15:20:40 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <3B75DF91-FB87-4580-88CD-AF6B78ABFA80@thebuild.com>
References: <17630-0947c0a5aa573243@postgresql.org>
To: killerwzb@163.com,
 PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Archived-At: 
 <https://www.postgresql.org/message-id/3B75DF91-FB87-4580-88CD-AF6B78ABFA80%40thebuild.com>
Precedence: bulk


> 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 =
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:

xof=3D# create table "TABLE2" (i integer);
CREATE TABLE
xof=3D#=20
\q
xof$ pg_dump --dbname=3Dxof --table "TABLE2" > /dev/null
pg_dump: error: no matching tables were found
xof$ pg_dump --dbname=3Dxof --table "\"TABLE2\"" > /dev/null
xof$=20