| From: | "Luke Lonergan" <llonergan(at)greenplum(dot)com> |
|---|---|
| To: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Alon Goldshuv" <agoldshuv(at)greenplum(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: NOLOGGING option, or ? |
| Date: | 2005-06-02 01:54:51 |
| Message-ID: | BEC3B4FB.6C42%llonergan@greenplum.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>
> Yep, we would _love_ those improvements.
>
Coming soon, probably from the guy you've never heard of :-)
>
> I am confused why you are confused. :-)
>
> Uh, how do you do the escapes if you don't double the escape character
> on input so you can distinguish a literal escape from one use to mark
> special data like a literal delimiter or a null?
Escape processing would proceed as before, but the semantics would change to
allow the use of different characters as the escape character, in addition
to the special characters for delimiter and newline. Also, escape
processing would be "false" as the default, so that the only special
characters by default would be the newline and delimiter characters.
Also of importance is the specification of newline and delimiter as
arbitrary double byte or 8-bit characters.
- Luke
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Qingqing Zhou | 2005-06-02 02:07:32 | Re: Can we simplify win32 threading code |
| Previous Message | Luke Lonergan | 2005-06-02 01:50:23 | Re: NOLOGGING option, or ? |