| From: | "Gavin M(dot) Roy" <gmr(at)ehpg(dot)net> |
|---|---|
| To: | Holger Marzen <holger(at)marzen(dot)de> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Binary data in PostgreSQL |
| Date: | 2004-02-21 21:49:00 |
| Message-ID: | 4037D24C.8020000@ehpg.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
It's not the most effective use of space, and I'm sure not the best way
to do it, but I store such data as base64 encoded text. Works very
well for my needs, in that regard.
Gavin
Holger Marzen wrote:
>Hi all,
>
>AFAIK it is possible for columns to be very large, up to about 2 GB. Are
>there any hints or experiences about storing binary data (jpg-images,
>pdf-documents) in PostgrreSQL with or without the complicated lo-stuff?
>
>Of course it's in many cases a good approach to store those files simply
>in the file system but there's always a risk of running out of sync
>(filesystem and tables), e.g. by deleting files and not deleting the
>table rows with the filenames.
>
>Any ideas and comments welcome.
>
>---------------------------(end of broadcast)---------------------------
>TIP 7: don't forget to increase your free space map settings
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | dewins murillo | 2004-02-22 01:51:04 | Meet this embebed postgresql in Visual Basic |
| Previous Message | Uwe C. Schroeder | 2004-02-21 21:06:00 | Re: Binary data in PostgreSQL |