From: Alvaro Herrera <alvherre@surnet.cl>
To: Scott Marlowe <smarlowe@g2switchworks.com>
Cc: ljh1469@alibaba-inc.com, "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 10:56:56 -0400
Message-ID: <20050624145656.GA7762@surnet.cl> (raw)
In-Reply-To: <1119624222.8208.67.camel@state.g2switchworks.com>
References: <20050624055243.3B13566C13B@smtp-hz>
<1119624222.8208.67.camel@state.g2switchworks.com>
On Fri, Jun 24, 2005 at 09:43:43AM -0500, Scott Marlowe wrote:
> On Fri, 2005-06-24 at 00:52, ????????? wrote:
> > 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.
>
> While I wouldn't mind have the versatility of sqlldr, I would HATE to
> have to deal with such a clunky interface. The only features of sqlldr
> I actually like are the ones that allow rejected records to go into a
> separate file.
There's a PGLoader project in pgfoundry that may suit some people.
> > 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.
>
> No one would complain if someone stepped up and programmed a decent
> table partitioning patch. I have a feeling it's one of the things on
> the TODO list that will happen in the next version or two.
I think Simon Riggs and crew are working on this.
--
Alvaro Herrera (<alvherre[a]surnet.cl>)
Jude: I wish humans laid eggs
Ringlord: Why would you want humans to lay eggs?
Jude: So I can eat them
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: alvherre@surnet.cl, smarlowe@g2switchworks.com, David.Bear@asu.edu
Subject: Re: psql copy errors
In-Reply-To: <20050624145656.GA7762@surnet.cl>
References: <20050624055243.3B13566C13B@smtp-hz> <1119624222.8208.67.camel@state.g2switchworks.com> <20050624145656.GA7762@surnet.cl>
* 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