From: | A J <s5aly(at)yahoo(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Pagesize for large-objects (ONLY) database. |
Date: | 2010-11-01 16:08:18 |
Message-ID: | 151658.65855.qm@web120002.mail.ne1.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hello,
I am planning to have a postgres database for large object storage. I believe
that with version 9.0, the 'world readable' issue with pg_largeobject is
resolved and we can now control at object level- which users can read/write what
objects.
Streaming performance is an issue and hence will need to increase the PAGE SIZE
(BLCKSZ ) to ensure access is sequential. Does anyone have recommendation on a
BLCKSZ I can start with.
There will be lot of reads,updates,inserts,deletes of the objects. Also any
ideas on how big of an issue fragmentation can be and how can it be contained ?
About 70% of the objects will be less than 1MB, about 25% upto 10MB and rest 5%
or so may be larger than 10MB.
Metadata management is also important so just a distributed filesystem (rather
than database) is not viable. Any other suggestions are welcome.
Thank you! - AJ
From | Date | Subject | |
---|---|---|---|
Next Message | Ray Stell | 2010-11-01 16:14:26 | ssl client cert authentication |
Previous Message | Dragos Valentin Moinescu | 2010-11-01 12:45:31 | plpgsql: some 'DELETE' queries are returning ROWCOUNT = 0 |