| From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Best Strategy for Large Number of Images |
| Date: | 2021-12-15 19:23:56 |
| Message-ID: | f930c152-7238-0b42-6cab-88f2027a4ade@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 12/15/21 11:45 AM, Estevan Rech wrote:
> 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?
We have an application which store images in the database using bytea
fields. The next version of the software will store the images externally,
with the filename in the database, because filesystems just inherently do a
better job at storing *lots* of files than does a database.
--
Angular momentum makes the world go 'round.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rob Sargent | 2021-12-15 19:24:31 | Re: Best Strategy for Large Number of Images |
| Previous Message | Estevan Rech | 2021-12-15 19:22:25 | Re: Best Strategy for Large Number of Images |