From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Cristiano <sumariva(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #5765: pg_dump fail to find upper case table name |
Date: | 2011-03-11 00:40:28 |
Message-ID: | 201103110040.p2B0eS906095@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Kevin Grittner wrote:
> Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
>
> > Manual says (at the bottom of
> > http://www.postgresql.org/docs/8.4/static/app-pgdump.html)
> >
> >> To specify an upper-case or mixed-case name in -t and related
> >> switches, you need to double-quote the name; else it will be
> >> folded to lower case (see Patterns). But double quotes are
> >> special to the shell, so in turn they must be quoted. Thus, to
> >> dump a single table with a mixed-case name, you need something
> >> like
> >>
> >> $ pg_dump -t '"MixedCaseName"' mydb > mytab.sql
>
> Perhaps some of that should be moved up to the definition of the -t
> switch? It wouldn't seem too out of place to me to put it somewhere
> near this sentence:
>
> | When using wildcards, be careful to quote the pattern if needed to
> | prevent the shell from expanding the wildcards.
>
> While examples are useful, information which is only provided there
> is easily missed when someone goes to read up on a particular
> switch.
I have applied the attached doc patch to reference the example section
from the specific pg_dump options sections.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
Attachment | Content-Type | Size |
---|---|---|
/rtmp/pg_dump.diff | text/x-diff | 2.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2011-03-11 03:30:51 | Re: Problem with ALTER TABLE - occasional "tuple concurrently updated" |
Previous Message | Bruce Momjian | 2011-03-10 23:50:56 | Re: Documentation bug: Chapter 35.4, paragraph 4 |