Re: PQgetlength vs. octet_length()

Поиск
Список
Период
Сортировка
От Kevin Grittner
Тема Re: PQgetlength vs. octet_length()
Дата
Msg-id 4A8A81180200002500029C22@gw.wicourts.gov
обсуждение исходный текст
Ответ на Re: PQgetlength vs. octet_length()  (Michael Clark <codingninja@gmail.com>)
Список pgsql-hackers
Michael Clark <codingninja@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 current
development issues, problems and bugs, and proposed new features. If
your question cannot be answered by people in the other lists, and it
is likely that only a developer will know the answer, you may re-post
your question in this list. You must try elsewhere first!"
Your question sounds appropriate for the pgsql-general list.
>> 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
>> --------------
>>     143721188
>>
>> When fetching the row through the C API, and I use PQgetlength() on
>> the column of the row in question I get:
>> (gdb) p (int)PQgetlength(result, rowIndex, i)
>> $3 = 544453159
As long as I'm replying, I'll point out that the relative sizes would
make sense if you were using an interface which got the text
representation of the bytea column, since many bytes would be
represented in octal with a backslash escape (four characters per
byte).
-Kevin


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Michael Clark
Дата:
Сообщение: Re: PQgetlength vs. octet_length()
Следующее
От: Tom Lane
Дата:
Сообщение: "make install" now tries to build the documentation