| From: | beyaNet Consultancy <beyanet(at)ntlworld(dot)com> |
|---|---|
| To: | pgsql-sql(at)postgresql(dot)org |
| Cc: | pgsql-novice(at)postgresql(dot)org |
| Subject: | Binary retrieval - *Best practice* recommendations... |
| Date: | 2004-02-20 15:22:50 |
| Message-ID: | A5260E9A-63B8-11D8-9F4F-0003938366A4@ntlworld.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice pgsql-sql |
Hi,
I have a table in postgreSQL, ver. 7.4.1, which serves up image
data(JPEG) to users browsers. In various posts I have read there has
been a favour towards storing image data as bytea (byte[]) instead of
storing the filesystem location of the image, or whatever binary data
is, in the database. I have decided to store my images on the database
and wanted to know what *best practice* performance tweaks you suggest
I make to postgreSQL in terms of minimising the time it takes to serve
binary data to users?
many thanks in advance
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2004-02-20 18:53:36 | Re: Row counts/data changes. Any catalog table that has this info? |
| Previous Message | joseph speigle | 2004-02-20 15:00:25 | Re: commenting sql code |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | scott.marlowe | 2004-02-20 15:27:14 | Re: date format in 7.4 |
| Previous Message | Silke Trissl | 2004-02-20 14:58:10 | date format in 7.4 |