| From: | Pavel Golub <pavel(at)microolap(dot)com> |
|---|---|
| To: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #5765: pg_dump fail to find upper case table name |
| Date: | 2010-11-24 15:24:40 |
| Message-ID: | 1585841013.20101124172440@gf.microolap.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hello, Kevin.
You wrote:
KG> Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
KG>
>> 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
KG>
KG> Perhaps some of that should be moved up to the definition of the -t
KG> switch? It wouldn't seem too out of place to me to put it somewhere
KG> near this sentence:
KG>
KG> | When using wildcards, be careful to quote the pattern if needed to
KG> | prevent the shell from expanding the wildcards.
+100
KG>
KG> While examples are useful, information which is only provided there
KG> is easily missed when someone goes to read up on a particular
KG> switch.
KG>
KG> -Kevin
--
With best wishes,
Pavel mailto:pavel(at)gf(dot)microolap(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2010-11-24 15:30:36 | Re: BUG #5764: installation error (incomplete process) |
| Previous Message | Kevin Grittner | 2010-11-24 15:04:48 | Re: BUG #5765: pg_dump fail to find upper case table name |