From: A J <s5aly@yahoo.com>
To: pgsql-admin@postgresql.org
Subject: Pagesize for large-objects (ONLY) database.
Date: Mon, 1 Nov 2010 09:08:18 -0700 (PDT)
Message-ID: <151658.65855.qm@web120002.mail.ne1.yahoo.com> (raw)
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: s5aly@yahoo.com
Subject: Re: Pagesize for large-objects (ONLY) database.
In-Reply-To: <151658.65855.qm@web120002.mail.ne1.yahoo.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox