|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #16953 problem with "bytea" column
Submitted: 2002-05-01 17:11 UTC Modified: 2002-05-03 17:13 UTC
From: stach at toya dot net dot pl Assigned:
Status: Not a bug Package: PostgreSQL related
PHP Version: 4.2.0 OS: Win32
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
Solve the problem:
16 + 44 = ?
Subscribe to this entry?

 [2002-05-01 17:11 UTC] stach at toya dot net dot pl
Apache 1.3.24 on Win32 (Win 2000), php installed as module.
PostgreSQL 7.2.1 on Linux (Debian).
When trying to select data from a column of type "bytea"
with query "select encode(zdjecie, 'base64') as zdjecie" from php, I get the following error:
pg_exec() query failed: pqReadData() -- read() failed: errno=0 No error
However, the same code works well (on the same database), when called from php 4.1.2 apache 1.3.24 on Linux (Debian).
Error reporting is set to E_ALL & ~E_NOTICE.


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2002-05-02 10:14 UTC]
I think this is PostgreSQL problem under Windows.
You are better to ask to PostgreSQL windwos users/developers.
 [2002-05-02 10:35 UTC]
BTW, bytea is _very_ slow compare to large object. 
Bytea could be 40, 50 times slower than lo. AND PHP pgsql module does not provide decode function when you select bytea. This makes slower.

I suggest to wait PostgreSQL 7.3 and PHP supports it or use lo now.

 [2002-05-03 17:13 UTC] stach at toya dot net dot pl
Just FYI, in PostgreSQL 7.2.1 large objects are
implemented using a **bytea** column in system table
pg_largeobject. And they don't work either, of course.
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Thu May 30 22:01:29 2024 UTC