From: | "Steve Howe" <howe(at)carcass(dot)dhs(dot)org> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | PQexec() 8191 bytes limit and text fields |
Date: | 2001-07-18 08:51:09 |
Message-ID: | 9j3ilp$2hrs$1@news.tht.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello all,
Writing my interface application, which use the PQexec library, I
came across the PQexec() queries 8191 bytes limit.
What useful are 4Gb text fields if I have this limit ?
I mean, if a user make an update to this field, with a large value
(let's say, 4Mb), do I have to call PQexec multiple (more then 500) times,
concatenating the strings each time I call it ??? Can't this be better
implemented ? This is too slow, and generates much more traffic then I ever
wish.
This problem also plagues the large objects API, since they're only
a wrapper to the built-in large objects API.
Does anyone have a better way of doing this ?
Best Regards,
Steve Howe
http://www.vitavoom.com
From | Date | Subject | |
---|---|---|---|
Next Message | Gunnar Rønning | 2001-07-18 10:46:54 | Re: Re: Idea: recycle WAL segments, don't delete/recreate 'em |
Previous Message | Zeugswetter Andreas SB | 2001-07-18 08:42:04 | AW: Re: Idea: recycle WAL segments, don't delete/recrea te 'emm |