From: Tom Lane <tgl@sss.pgh.pa.us>
To: Cory Nemelka <cnemelka@gmail.com>
cc: Aldo Sarmiento <aldo@bigpurpledot.com>, pgsql-admin@postgresql.org
Subject: Re: Processing very large TEXT columns (300MB+) using C/libpq
In-reply-to: 
 <CAMe5Gn1ksuVLRcR6DPp+nzsEsNZVVRHjMUoM-9t_JBAW2Xg4HA@mail.gmail.com>
References: 
 <CAMe5Gn1OMeOutXDLzGOHHO28r8ZYy5URdsuTxP2R14oTMeZ8pw@mail.gmail.com>
 <CAHX=r6wgC=WvEtgRYbhvNoK80-fqS9QBaJBwqyyU_xv9NpAfuw@mail.gmail.com>
 <CAMe5Gn1ksuVLRcR6DPp+nzsEsNZVVRHjMUoM-9t_JBAW2Xg4HA@mail.gmail.com>
Comments: In-reply-to Cory Nemelka <cnemelka@gmail.com>
	message dated "Fri, 20 Oct 2017 09:14:48 -0600"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4749.1508518522.1@sss.pgh.pa.us>
Date: Fri, 20 Oct 2017 12:55:22 -0400
Message-ID: <4750.1508518522@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

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