Re: importing data

From: Mental <Mental(at)NeverLight(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: importing data
Date: 2004-01-19 16:53:35
Message-ID: 20040119165335.GA1756@neverlight.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sat, Jan 17, 2004 at 10:27:09PM -0500, Tom Lane wrote:
> Mental <Mental(at)NeverLight(dot)com> writes:
> > The postgresql documentation for COPY FROM INFILE suggests that high-ascii
> > characters be encoded to a backslash followed by the octal value for the
> > character.
>
> While it's certainly possible to do that, I don't see anyplace in the
> current documentation that recommends it. What did you conclude that
> from?
>

http://www.postgresql.org/docs/7.3/static/sql-copy.html indicated:

\digits , Backslash followed by one to three octal digits specifies the
character with that numeric code

We were having trouble with characters that were high ascii encoded.
Perhaps it was how we were connecting to do the import, but we found that
escaping them as so helped. After filtering, data is copied into the
tables like so:

ENCODING='SQL_ASCII'
$FILTER_DATA
psql -U $USER -c "SET CLIENT_ENCODING TO '$ENCODING'; copy $i from
'$DATA_DIR/$i-noheader.tab' NULL as '' " $DB

--
Mental (Mental(at)NeverLight(dot)com)

I've been told that I need to warn people about inappropriate content.
So if anything I say or post is inappropriate, dont look at it.

GPG public key: http://www.neverlight.com/pas/Mental.asc

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message scott.marlowe 2004-01-19 17:38:04 Re: New PostgreSQL search resource
Previous Message Jared Carr 2004-01-19 16:31:48 Getting rid of duplicate tables.