From: | Zahir Lalani <ZahirLalani(at)oliver(dot)agency> |
---|---|
To: | Estevan Rech <softrech(at)gmail(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | RE: Best Strategy for Large Number of Images |
Date: | 2021-12-19 14:24:48 |
Message-ID: | DB9P251MB05464940999593ADDF72A9A4A77A9@DB9P251MB0546.EURP251.PROD.OUTLOOK.COM |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Confidential
We have a large B2B application used in marketing management – heavily focused on images/video – no binaries ever stored in DB – we have all the metadata in the DB and binaries in scalable folder structure. Serving up images from the DB is not very scalable. I am not sure what you will do with the binary data that it is needed in the DB?
Z
From: Estevan Rech <softrech(at)gmail(dot)com>
Sent: 15 December 2021 17:45
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Best Strategy for Large Number of Images
Hi,
I don't currently use PostgreSQL, but I plan to migrate and I have a question about the best way/strategy for storing images. I have about 2 million images with a growth trend of around 1 million images per year. I plan to store in bytea format in an isolated table. Is this recommended? Is there another better way?
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Mühlbeyer | 2021-12-20 09:35:14 | md5 issues Postgres14 on OL7 |
Previous Message | Shubham Mittal | 2021-12-19 11:50:21 | PGBouncer logs explanation required |