Greg Stark wrote:
If you use binary encoding then you don't have to deal with that.
Though I seem to recall there is still a gotcha you have to worry
about if there are nul bytes in your datum. I don't recall exactly
what that meant you had to do though.
As far as I know, it only means that
Hello - am I in the wrong mailing list for this sort of problem? :-/
Thanks,
Michael.
On Mon, Aug 17, 2009 at 6:28 PM, Michael Clark codingni...@gmail.comwrote:
Hello everyone.
Having a weird issue.
I have a value inserted into a bytea column, which is about 137megs in
size.
If I use
Michael Clark codingni...@gmail.com wrote:
Hello - am I in the wrong mailing list for this sort of problem? :-/
Probably. If you check here:
http://www.postgresql.org/community/lists/
You'll find this description for the list:
The PostgreSQL developers team lives here. Discussion of
On Tue, Aug 18, 2009 at 4:04 PM, Michael Clarkcodingni...@gmail.com wrote:
Hello - am I in the wrong mailing list for this sort of problem? :-
Probably but it's also a pretty technical point and you're programming
in C so it's kind of borderline.
If you're using text-mode then your datum that
Hello everyone.
Having a weird issue.
I have a value inserted into a bytea column, which is about 137megs in size.
If I use octet_length() to check the size of the column for this specific
row I get this:
TestDB=# SELECT octet_length(rawdata) FROM LargeData;
octet_length
--
