From: | "Joe Shevland" <jshevland(at)j-elite(dot)com> |
---|---|
To: | "Dave Cramer" <Dave(at)micro-automation(dot)net> |
Cc: | <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: BLOB performance test FYI |
Date: | 2002-04-17 21:35:57 |
Message-ID: | HEECIHEEJDBMCCGMGIOBKECFCHAA.jshevland@j-elite.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Well, isn't it a bit crazy that bytea is the default JDBC BLOB type given the performance issues shown?
The general public that start to pump binary data into a PostgreSQL database are going to be confused if performance is that bad... and that was a grunty server too with bulkloads of RAM, I shudder to think what'd happen to a client.
I mean, generally if you're storing binary data it is for things such as image or document storage (of course there's many, many other purposes), so the binary data wil be large.
Joe
> -----Original Message-----
> From: Dave Cramer [mailto:Dave(at)micro-automation(dot)net]
> Sent: Wednesday, 17 April 2002 21:29
> To: Joe Shevland
> Cc: pgsql-jdbc(at)postgresql(dot)org
> Subject: Re: [JDBC] BLOB performance test FYI
>
>
> Joe,
>
> Yes, Barry has commented on the reasons for this recently. The short
> version is that when you are using bytea, the backend parses the input.
>
> Dave
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2002-04-17 21:53:44 | Re: BLOB performance test FYI |
Previous Message | Leandro Rodrigo Saad Cruz | 2002-04-17 17:53:43 | using Date and setObject() |