Re: [ADMIN] Processing very large TEXT columns (300MB+) using C/libpq - Mailing list pgsql-admin

From Tom Lane
Subject Re: [ADMIN] Processing very large TEXT columns (300MB+) using C/libpq
Date
Msg-id 4750.1508518522@sss.pgh.pa.us
Whole thread Raw
In response to Re: [ADMIN] Processing very large TEXT columns (300MB+) using C/libpq  (Cory Nemelka <cnemelka@gmail.com>)
Responses Re: [ADMIN] Processing very large TEXT columns (300MB+) using C/libpq  (Bear Giles <bgiles@coyotesong.com>)
List pgsql-admin
Cory Nemelka <cnemelka@gmail.com> writes:
> Yes, but I should be able to read them much faster.  The psql client can
> display an 11MB column in a little over a minute, while in C using libpg
> library, it takes over an hour.

Well, of course psql relies on libpq, so it seems unlikely that libpq
itself is where the time is going.  Have you tried applying a profiler?
"perf" or "oprofile" or similar tool ought to pinpoint the culprit
pretty easily.
        regards, tom lane


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin

pgsql-admin by date:

Previous
From: Cory Nemelka
Date:
Subject: Re: [ADMIN] Processing very large TEXT columns (300MB+) using C/libpq
Next
From: Bear Giles
Date:
Subject: Re: [ADMIN] Processing very large TEXT columns (300MB+) using C/libpq