| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Bryn Llewellyn <bryn(at)yugabyte(dot)com>, Pg Docs <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: COPY statement: no list of the allowed values for "format_name" |
| Date: | 2020-10-29 22:29:15 |
| Message-ID: | CAKFQuwbn1YG7kGHnwC0j8qTyrD7VDJXOm3HDSmAo1oz+rHE4sA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Thu, Oct 29, 2020 at 3:24 PM PG Doc comments form <noreply(at)postgresql(dot)org>
wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/11/sql-copy.html
> Description:
>
> Look at the account of the COPY statement, here:
>
> https://www.postgresql.org/docs/11/sql-copy.html
>
>
> But there was no list of the allowed values.
>
Keep reading...
"""
FORMAT
Selects the data format to be read or written: text, csv (Comma Separated
Values), or binary. The default is text.
"""
I suppose including the syntax term "format_type" might help, but the
all-caps FORMAT is definitive.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2020-10-29 22:33:13 | Re: What does "[backends] should seldom or never need to wait for a write to occur" mean? |
| Previous Message | PG Doc comments form | 2020-10-29 18:20:20 | What does "[backends] should seldom or never need to wait for a write to occur" mean? |