Re: COPY .... WITH (FORMAT binary) causes syntax error at or near "binary" - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: COPY .... WITH (FORMAT binary) causes syntax error at or near "binary"
Date
Msg-id 1309878337-sup-685@alvh.no-ip.org
Whole thread Raw
In response to COPY .... WITH (FORMAT binary) causes syntax error at or near "binary"  (Pavel Golub <pavel@microolap.com>)
Responses Re: COPY .... WITH (FORMAT binary) causes syntax error at or near "binary"
Re: [BUGS] COPY .... WITH (FORMAT binary) causes syntax error at or near "binary"
List 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@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [COMMITTERS] pgsql: Move Trigger and TriggerDesc structs out of rel.h into a new rel
Next
From: Robert Haas
Date:
Subject: Re: Small SSI issues