| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Estevan Rech <softrech(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Rob Sargent <robjsargent(at)gmail(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Best Strategy for Large Number of Images |
| Date: | 2021-12-15 19:37:19 |
| Message-ID: | ff4e75a4-d771-4dbe-0be2-fc59d1db1fde@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 12/15/21 11:22, Estevan Rech wrote:
> The possibilities are known, but does anyone have experience with this
> scenario?
It would help if you elaborated on the scenerio is?
There is no questioning that you can store images in the database. The
issues are what you want to do with them once they are there, the
hardware(real or virtual) you have available, the user load on the
database, etc?
Providing at least an outline that answers the above would go a long way
to getting some reasonable answers based on experience.
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Estevan Rech | 2021-12-15 20:12:10 | Re: Best Strategy for Large Number of Images |
| Previous Message | Rob Sargent | 2021-12-15 19:24:31 | Re: Best Strategy for Large Number of Images |