Re: psql copy errors - Mailing list pgsql-admin

From Alvaro Herrera
Subject Re: psql copy errors
Date
Msg-id 20050624145656.GA7762@surnet.cl
Whole thread Raw
In response to Re: psql copy errors  (Scott Marlowe <smarlowe@g2switchworks.com>)
List pgsql-admin
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
canalso 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

pgsql-admin by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: unicode
Next
From: Gaetano Mendola
Date:
Subject: RPM or RPMS for RH9.0