From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Pavel Golub <pavel(at)gf(dot)microolap(dot)com> |
Cc: | pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] COPY .... WITH (FORMAT binary) causes syntax error at or near "binary" |
Date: | 2011-07-05 15:06:42 |
Message-ID: | 1309878337-sup-685@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
Excerpts from Pavel Golub's message of mar jul 05 10:52:06 -0400 2011:
> Hello.
>
> System: PostgreSQL v9.0 Windows XP SP3
> SQL: COPY "tablename" TO STDOUT WITH (FORMAT binary)
> ERROR: syntax error at or near "binary"
> LINE 1: ...OPY "tablename" TO STDOUT WITH (FORMAT binary)
> ^
>
> ********** Error **********
>
> ERROR: syntax error at or near "binary"
> SQL state: 42601
> Character: 55
>
> But if I use 'FORMAT text' or 'FORMAT csv' all is OK.
>
> Suppose this happens because BINARY is not listed in
> "unreserved_keyword" neither in "col_name_keyword parser" parser rules, but
> listed in "type_func_name_keyword" instead.
That seems pretty unfortunate. Of course, it works if you quote it:
COPY "tablename" TO STDOUT WITH (FORMAT "binary")
I assume it's not in unreserved_keyword because it would cause a
shift/reduce conflict elsewhere.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Golub | 2011-07-05 15:13:21 | Re: [HACKERS] COPY .... WITH (FORMAT binary) causes syntax error at or near "binary" |
Previous Message | Pavel Golub | 2011-07-05 14:52:06 | COPY .... WITH (FORMAT binary) causes syntax error at or near "binary" |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2011-07-05 15:07:53 | Re: Small SSI issues |
Previous Message | Robert Haas | 2011-07-05 15:03:44 | Re: [v9.2] SECURITY LABEL on shared database object |