Skip site navigation (1) Skip section navigation (2)

Re: Inserting/updating large text fields w/libpq -- Please ignore

From: Jeremy Wohl <jeremyw-pginterfaces(at)igmus(dot)org>
To: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: Inserting/updating large text fields w/libpq -- Please ignore
Date: 2001-11-01 12:59:05
Message-ID: 20011101045905.A9796@zydeco.igmus.org (view raw or flat)
Thread:
Lists: pgsql-interfaces
Verdict: really dumb.  Directly after posting, I dove into the 7.1.3 code,
curious about the details.  Not finding any such error ("query .. too long"),
it was obviously a link problem.  Sure enough, old, system RedHat libs.
Lots of testing with the right libs & huge input does fine.

Sorry folks.  Please ignore.

-jeremy

On Thu, Nov 01, 2001 at 02:33:11AM -0800, Jeremy Wohl wrote:
> Hi folks,
> 
> How does one insert large 'text' fields via libpq?  That is, data in
> insert/update statements that exceed the 16K limit in stock 7.1.3 setups.
> 
> For the moment, I'm iterating over a concat (column = column || 'next chunk'),
> but that's ~64 net trips for my average 1meg entries.
> 
> I suspect there's a coming, unimplemented API for these types opened up by
> TOAST, to obviate Large Objects.  However, to ease current requirements,
> I hope I'm doing something really dumb.
> 
> Thoughts?
> 
> thanks,
> -jeremy
> _____________________________________________________________________
> jeremy wohl ..: http://igmus.org
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)

In response to

pgsql-interfaces by date

Next:From: Bruce MomjianDate: 2001-11-01 20:07:35
Subject: Re: ECPG - connection name in "EXEC SQL AT ... " statement
Previous:From: Jeremy WohlDate: 2001-11-01 10:33:11
Subject: Inserting/updating large text fields w/libpq

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group