| From: | Francisco Olarte <folarte(at)peoplecall(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Thomas Kellerer <spam_eater(at)gmx(dot)net>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: pg_dump and quoted identifiers |
| Date: | 2016-12-15 15:46:59 |
| Message-ID: | CA+bJJbx1pebcybtiRLt-U=z-Z6QGVRAg__BpJd+hyHfUPveVXQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Dec 15, 2016 at 4:20 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
...
> Hmm. It might shed some light if you put "echo" in front of that
> to see what gets printed:
>
> $ echo pg_dump -d postgres -t "\"Statuses\""
> pg_dump -d postgres -t "Statuses"
Also, when having strange issues, I've found the combo
echo <original command> | od -tx1 -tc
very useful, this help rule out potential fancy quotes pointed previously
Francisco Olarte.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom DalPozzo | 2016-12-15 15:48:57 | Re: tuple data size and compression |
| Previous Message | Adrian Klaver | 2016-12-15 15:23:28 | Re: tuple data size and compression |