From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Mario Duhanic <duhanic(at)gmail(dot)com> |
Cc: | pgsql-docs(at)postgreSQL(dot)org |
Subject: | Re: Underscorces in copy-documentation (9.0 and higher) |
Date: | 2013-03-20 14:53:10 |
Message-ID: | 2772.1363791190@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Mario Duhanic <duhanic(at)gmail(dot)com> writes:
> 2013/3/20 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>> Huh? The references to FORCE_QUOTE look correct to me. The syntax
>> doesn't support multi-word option names, so it has to be like that
>> (or else run the words together, which doesn't sound like an
>> improvement).
> Thanks, Tom, for your quick response.
> Maybe this is just a miscommunication, sorry for that then (i.e. I
> misunderstood the documentation here).
> (Stupid) example for the problem:
> "COPY (SELECT aggfnoid, aggtransfn from pg_aggregate) TO STDOUT WITH
> FORCE QUOTE * DELIMITER ',' CSV HEADER;"
> will run, a FORCE_QUOTE or FORCEQUOTE won't
As Ian notes, that's the old syntax with a hard-wired option set.
The lack of parentheses after WITH is the difference.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Mario Duhanic | 2013-03-20 15:01:04 | Re: Underscorces in copy-documentation (9.0 and higher) |
Previous Message | Mario Duhanic | 2013-03-20 14:50:05 | Fwd: Underscorces in copy-documentation (9.0 and higher) |