| From: | Tino Wildenhain <tino(at)wildenhain(dot)de> |
|---|---|
| To: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
| Cc: | Brent Wood <b(dot)wood(at)niwa(dot)co(dot)nz>, pgsql-general(at)postgresql(dot)org, avin_friends(at)yahoo(dot)com |
| Subject: | Re: To store and retrive image data in postgresql |
| Date: | 2008-07-08 04:47:27 |
| Message-ID: | 4872F15F.4050506@wildenhain.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi,
Craig Ringer wrote:
> Brent Wood wrote:
...
>> I need to store
>> an image in postgresql database and after that i need to retrive the
>> image back.Can you please help me how to do this?
...
> - Storing image data in the DB is probably much less efficient in
> storage space and for access; and
> - You face possible MVCC bloat with image data when storing in the
> DB, so careful management would be needed
>
> The first really cool MS-SQL feature I've heard about relates to this.
> NTFS now has transaction support. I'm pretty sure I remember hearing
*snip*
In that case, would that MVCC bloat not just transferred to the
filesystem? Large objects should currently give you pretty much
the same results without plug for MS-SQL :-)
And in most cases bytea as mentioned elsewhere are not so bad either
(especially for p*m-Images :-)
Cheers
Tino
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hendra | 2008-07-08 06:59:02 | Hi there, new here and have question |
| Previous Message | Craig Ringer | 2008-07-08 02:45:39 | Re: To store and retrive image data in postgresql |