pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: 李江华 <ljh1469@alibaba-inc.com>
To: David.Bear@asu.edu <David.Bear@asu.edu>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: psql copy errors
Date: Fri, 24 Jun 2005 13:52:40 +0800
Message-ID: <20050624055243.3B13566C13B@smtp-hz> (raw)

David Bear:

	    Yes. I agree with you.
        \copy is really too brittle.
        I wonder why \copy is not like oracle's sqlldr?
        I think sqlldr is more powerful. When using sqlldr,we can specify the maximum error records we allow,and we can also specify the number we should commit in every transaction.

		I think PostgreSQL should consider this.

       Another aspect is also important. Oracle has better partition table facilities,it's especially suitable for large tables,as well as index partition concepts.But PostgreSQL has no such concepts.These are really important for large database.
     
        I think if PostgreSQL can implement those above in the future.It will be more powerful and more suitable for large business application.

		

 

======= 2005-06-24 03:27:44 you wrote:=======

>I'm finding the \copy is very brittle. It seems to stop for everyone
>little reason. Is there a way to tell it to be more forgiving -- for
>example, to ignore extra data fields that might exists on a line?
>
>Or, to have it just skip that offending record but continue on to the
>next.
>
>I've got a tab delimited file, but if \copy sees any extra tabs in the
>file it just stops at that record. I want to be able to control what
>pg does when it hits an exception.
>
>I'm curious what others do for bulk data migration. Since copy seems
>so brittle, there must be a better way...
>
>-- 
>David Bear
>phone: 	480-965-8257
>fax: 	480-965-9189
>College of Public Programs/ASU
>Wilson Hall 232
>Tempe, AZ 85287-0803
> "Beware the IP portfolio, everyone will be suspect of trespassing"
>
>---------------------------(end of broadcast)---------------------------
>TIP 2: you can get off all lists at once with the unregister command
>    (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>

= = = = = = = = = = = = = = = = = = = =
			

       Best regards!
  
        
                               李江华
                               Seamus Dean
                               Alibaba.com
			                   TEL:0571-85022088-2287
                        ljh1469@alibaba-inc.com
                        2005-06-24


view thread (6+ messages)  latest in thread

Message-ID: <20050624055243.3B13566C13B@smtp-hz>
Permalink:  ../20050624055243.3B13566C13B@smtp-hz/
Also on:    postgresql.org/message-id/20050624055243.3B13566C13B@smtp-hz

 · 

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: ljh1469@alibaba-inc.com, David.Bear@asu.edu
  Subject: Re: psql copy errors
  In-Reply-To: <20050624055243.3B13566C13B@smtp-hz>
  References: <20050624055243.3B13566C13B@smtp-hz>

* 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