Re: BUG #5765: pg_dump fail to find upper case table name
От
Kevin Grittner
Тема
Re: BUG #5765: pg_dump fail to find upper case table
name
Дата
Msg-id
4CECD5300200002500037DF0@gw.wicourts.gov
Ответ на
Re: BUG #5765: pg_dump fail to find upper case table name (Heikki Linnakangas)
Список
Дерево обсуждения
BUG #5765: pg_dump fail to find upper case table name "Cristiano" <sumariva@gmail.com>
Re: BUG #5765: pg_dump fail to find upper case table name Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Re: BUG #5765: pg_dump fail to find upper case table
name "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: BUG #5765: pg_dump fail to find upper case table name Pavel Golub <pavel@microolap.com>
Re: BUG #5765: pg_dump fail to find upper case table
name Bruce Momjian <bruce@momjian.us>
Heikki Linnakangas 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. -Kevin
В списке pgsql-bugs по дате отправления
От: Kevin Grittner
Дата: