Re: NOLOGGING option, or ?

From: "Zeugswetter Andreas DAZ SD" <ZeugswetterA(at)spardat(dot)at>
To: "Luke Lonergan" <llonergan(at)greenplum(dot)com>, "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 10:09:26
Message-ID: E1539E0ED7043848906A8FF995BDA5790C518C@m0143.s-mxs.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> 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.

If you mean syntax to specify escape and delimiter (and newline ?),
that is a great addition, that imho all would like.

> Also, escape
> processing would be "false" as the default, so that the only special
> characters by default would be the newline and delimiter characters.

I don't see how that would be any advantage ? What is so wrong about having syntax to
choose no escape processing, like "escape ''" ?

Andreas

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jonah H. Harris 2005-06-02 13:22:24 Re: Google's Summer of Code ...
Previous Message Neil Conway 2005-06-02 08:09:22 Re: lastval()