pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: CHRIS HOOVER <CHRIS.HOOVER@companiongroup.com>
To: CHRIS.HOOVER@companiongroup.com
Cc: pgsql-admin@postgresql.org, H J Sanders <hjs@rmax.nl>
Subject: Re: copy
Date: Wed, 1 Dec 2004 10:13:00 -0500
Message-ID: <NY5a4125-73fc333a@companiongroup.com> (raw)

fat fingered that one:

cat < file> | sed 's/<delimiter>$//'> <file>.new
------------------( Forwarded letter 1 follows )---------------------
Date: Wed, 1 Dec 2004 10:03:00 -0500
To: H.J.Sanders[hjs]@rmax.nl.comp
Cc: pgsql-admin@postgresql.org.comp
From: CHRIS.HOOVER@companiongroup.com.comp
Sender: pgsql-admin-owner+m15600@postgresql.org.comp
Subject: Re: [ADMIN] copy

cat <file> | sed '<delimiter>$//' > <file>.new

this should remove the last delimiter
------------------( Forwarded letter 1 follows )---------------------
Date: Wed, 1 Dec 2004 13:33:26 +0100
To: pgsql-admin@postgresql.org.comp
From: H.J.Sanders[hjs]@rmax.nl.comp
Sender: pgsql-admin-owner+m15591@postgresql.org.comp
Subject: [ADMIN] copy


Hello.

We are moving a database from informix to Postgresql.

To do so we do an unload from Informix and copy to postgresql.

Informix unloads with a delimiter also after the last field in a record.

This is no problem when doing a copy to Postgresql 7.2
You get a warning (to many fields) but the copy process continues.

In 7.4 however the copy stops .

Does anyone know how to proceed the copy or a fast way to remove the last
character
from the unload files.

They are anyhow to big to handle with vi.

Many thanks

Henk Sanders


---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
    (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
      joining column's datatypes do not match



view thread (11+ messages)  latest in thread

Message-ID: <NY5a4125-73fc333a@companiongroup.com>
Permalink:  ../NY5a4125-73fc333a@companiongroup.com/
Also on:    postgresql.org/message-id/NY5a4125-73fc333a@companiongroup.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: CHRIS.HOOVER@companiongroup.com, hjs@rmax.nl
  Subject: Re: copy
  In-Reply-To: <NY5a4125-73fc333a@companiongroup.com>
  References: <NY5a4125-73fc333a@companiongroup.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox