Need suggestion

From: Carl von Clausewitz <clausewitz45(at)gmail(dot)com>
To: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Need suggestion
Date: 2011-06-01 08:08:14
Message-ID: BANLkTi=Vt21VW7TXzr0df8DdwDRgF9o9rw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hello Everyone,

I got a new project, with 100 user in Europe. In this case, I need to handle
production and sales processes an its documentations in PostgreSQL with PHP.
The load of the sales process is negligible, but every user produces 2
transaction in the production process, with 10-30 scanned documents (each
are 400kb - 800kb), and 30-50 high resolution pictures (each are 3-8 MB),
and they wanted to upload it to 'somewhere'. 'Somewhere' could be the server
files system, and a link in the PostgreSQL database for the location of the
files (with some metadata), or it could be the PostgreSQL database.

My question is that: what is your opinion about to store the scanned
documentation and the pictures in the database? This is a huge amount of
data (between daily 188MB and 800MB data, average year is about 1 TB data),
but is must be searchable, and any document must be retrieved within 1 hour.
Every documentations must be stored for up to 5 years... It means the
database could be about 6-7 TB large after 5 years, and then we can start to
archive documents. Any other data size is negligible.

If you suggest, to store all of the data in PostgreSQL, what is your
recommendation about table, index structure, clustering, archiving?

Thank you in advance!
Regards,
Carl

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Aleksey Chirkin 2011-06-01 09:32:44 Returning from insert on view
Previous Message Pavel Stehule 2011-06-01 07:14:27 Re: Psql Internal Variable question