Re: [GENERAL] pg_dump and quoted identifiers

Von: pgsql-general-ow...@postgresql.org [pgsql-general-ow...@postgresql.org] im Auftrag von Thomas Kellerer [spam_ea...@gmx.net] Gesendet: Donnerstag, 15. Dezember 2016 17:15 An: pgsql-general@postgresql.org Betreff: Re: [GENERAL] pg_dump and quoted

Re: [GENERAL] pg_dump and quoted identifiers

Thomas Kellerer writes: > Tom Lane schrieb am 15.12.2016 um 16:20: >> 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" > Same here: >

Re: [GENERAL] pg_dump and quoted identifiers

On Thursday, December 15, 2016 5:15:44 PM EST Thomas Kellerer wrote: > Tom Lane schrieb am 15.12.2016 um 16:20: > >> Still doesn't work: > >> -bash-4.1$ pg_dump -d postgres -t "\"Statuses\"" > >> pg_dump: no matching tables were found > > > > Hmm. It might shed some light if you put "echo"

Re: [GENERAL] pg_dump and quoted identifiers

Tom Lane schrieb am 15.12.2016 um 16:20: >> Still doesn't work: >> -bash-4.1$ pg_dump -d postgres -t "\"Statuses\"" >> pg_dump: no matching tables were found > > 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

Re: [GENERAL] pg_dump and quoted identifiers

On Thu, Dec 15, 2016 at 4:20 PM, Tom Lane 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

Re: [GENERAL] pg_dump and quoted identifiers

Thomas Kellerer writes: > Adrian Klaver schrieb am 14.12.2016 um 15:32: >> So have you tried the answer from the SO question?: > Still doesn't work: > -bash-4.1$ pg_dump -d postgres -t "\"Statuses\"" > pg_dump: no matching tables were found Hmm. It might shed some light

Re: [GENERAL] pg_dump and quoted identifiers

On 12/14/2016 11:37 PM, Thomas Kellerer wrote: Adrian Klaver schrieb am 14.12.2016 um 15:32: I'm suspicious that you're not actually typing plain-ASCII single and double quotes, but some fancy curly quote character. Definitely not. I typed this manually on the command line using Putty So

Re: [GENERAL] pg_dump and quoted identifiers

Adrian Klaver schrieb am 14.12.2016 um 15:32: >>> I'm suspicious that you're not actually typing plain-ASCII single and >>> double quotes, but some fancy curly quote character. >> >> Definitely not. I typed this manually on the command line using Putty > > So you are reaching the Bash shell via

Re: [GENERAL] pg_dump and quoted identifiers

On 12/13/2016 11:18 PM, Thomas Kellerer wrote: Tom Lane schrieb am 13.12.2016 um 19:35: These cases work for me. Maybe your shell is doing something weird with the quotes? Hmm, that's the default bash from CentOS 6 (don't know the exact version) I'm using bash from current RHEL6, should

Re: [GENERAL] pg_dump and quoted identifiers

Tom Lane schrieb am 13.12.2016 um 19:35: >>> These cases work for me. Maybe your shell is doing something weird >>> with the quotes? > >> Hmm, that's the default bash from CentOS 6 (don't know the exact version) > > I'm using bash from current RHEL6, should be the same. > > I'm suspicious that

Re: [GENERAL] pg_dump and quoted identifiers

Thomas Kellerer writes: > Tom Lane schrieb am 13.12.2016 um 18:02: >> These cases work for me. Maybe your shell is doing something weird >> with the quotes? > Hmm, that's the default bash from CentOS 6 (don't know the exact version) I'm using bash from current RHEL6, should

Re: [GENERAL] pg_dump and quoted identifiers

On Tue, Dec 13, 2016 at 11:24 AM, Thomas Kellerer wrote: > David G. Johnston schrieb am 13.12.2016 um 18:05: > >> On Tue, Dec 13, 2016 at 9:43 AM, Pavel Stehule > >wrote: >> >> >> pg_dump -t '"Statuses"' postgres

Re: [GENERAL] pg_dump and quoted identifiers

Tom Lane schrieb am 13.12.2016 um 18:02: -bash-4.1$ pg_dump -d postgres -t '"Statuses"' pg_dump: no matching tables were found -bash-4.1$ pg_dump -d postgres -t 'public."Statuses"' pg_dump: no matching tables were found These cases work for me. Maybe your shell is doing

Re: [GENERAL] pg_dump and quoted identifiers

David G. Johnston schrieb am 13.12.2016 um 18:05: On Tue, Dec 13, 2016 at 9:43 AM, Pavel Stehule >wrote: pg_dump -t '"Statuses"' postgres ​To elaborate - your shell was removing the double-quotes. You need make it so after shell

Re: [GENERAL] pg_dump and quoted identifiers

On Tue, Dec 13, 2016 at 9:43 AM, Pavel Stehule wrote: > >> pg_dump -t '"Statuses"' postgres > > ​To elaborate - your shell was removing the double-quotes. You need make it so after shell processing the double-quotes remain. Wrapping the double-quote string in

Re: [GENERAL] pg_dump and quoted identifiers

Thomas Kellerer writes: > postgres=# create table "Statuses" (id integer); > CREATE TABLE > -bash-4.1$ pg_dump -d postgres -t "Statuses" > pg_dump: no matching tables were found This is expected since those quotes are eaten by the shell. > -bash-4.1$

Re: [GENERAL] pg_dump and quoted identifiers

2016-12-13 17:38 GMT+01:00 Thomas Kellerer : > Inspired by this question: > >http://dba.stackexchange.com/q/158044/1822 > > I tried that for myself, and it seems that pg_dump indeed can not parse > quoted identifiers: > > psql (9.6.1) > Type "help" for help. > >

[GENERAL] pg_dump and quoted identifiers

Inspired by this question: http://dba.stackexchange.com/q/158044/1822 I tried that for myself, and it seems that pg_dump indeed can not parse quoted identifiers: psql (9.6.1) Type "help" for help. postgres=# create table "Statuses" (id integer); CREATE TABLE postgres=#