Skip site navigation (1) Skip section navigation (2)

Re: NOLOGGING option, or ?

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Alon Goldshuv <agoldshuv(at)greenplum(dot)com>
Cc: Steve Atkins <steve(at)blighty(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: NOLOGGING option, or ?
Date: 2005-06-03 18:12:48
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Alon Goldshuv wrote:
> Bruce,
> Point taken. 
> > Now, you can argue that
> > a different escape should be possible, or that some other escape syntax
> > could be used, but the existing mechanism is clearly 100% reliable when
> > used properly and not broken.
> I think that having an option for another escape syntax (such as using
> ESCAPE AS clause in delimited format (non-csv) COPY) with a default of '\\'
> is a good compromise that will allow users to escape their data (like COPY
> currently is), or by specifying another escape character allow all of their
> backslashes to be treated as data.
> I'll start a new discussion about it on a new thread soon.

Yep, great.  Right now we only support single-byte escapes (and
delimiters), so there should be a discussion if multiple byte values are
useful too.  Also, there was discussion of what the default should be. 
I don't think there is any agreement to change the existing defaults. 
You might argue for a new mode that sets certain defaults to be easier
to load, but I am afraid of a new format that isn't 100% reliable,
because it assumes that some sequence of bytes will never appear in the

Anyway, these are ideas you can consider when making a proposal.

  Bruce Momjian                        |
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

In response to


pgsql-hackers by date

Next:From: Gevik babakhaniDate: 2005-06-03 18:56:44
Subject: executing OS programs from pg
Previous:From: Gevik babakhaniDate: 2005-06-03 17:12:00
Subject: Re: PostgreSQL Developer Network

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group