Re: Tablespace-level Block Size Definitions - Mailing list pgsql-hackers

From Hannu Krosing
Subject Re: Tablespace-level Block Size Definitions
Date
Msg-id 1117629520.4772.25.camel@fuji.krosing.net
Whole thread Raw
In response to Re: Tablespace-level Block Size Definitions  (Dawid Kuroczko <qnex42@gmail.com>)
List pgsql-hackers
On K, 2005-06-01 at 14:00 +0200, Dawid Kuroczko wrote:
> On 6/1/05, Zeugswetter Andreas DAZ SD <ZeugswetterA@spardat.at> wrote:
> > You could create a separate bufferpool per page size. Of course that
> > has other disadvantages.
> > 
> > Is it really so difficult to create and attach another shmem segment ?
> 
> Well, I don't think it is much different from having two database clusters,
> each with different block size.  Hmm, perhaps it could be possible to
> make them all available through one "virtual" DB host/port using
> pg_pool even. :)
> 
> It shouldn't be too difficult to create benchmarks testing performance
> of PostgreSQL under different block sizes, I guess.  I wonder what
> perfromance win is possible...

Perhaps it is simpler to just put different tablespaces on different
disks and then play with filesystem readahead settings at disk level.

It's not exactly the same thing, but may solve at least some problems.

-- 
Hannu Krosing <hannu@skype.net>



pgsql-hackers by date:

Previous
From: Hannu Krosing
Date:
Subject: Re: NOLOGGING option, or ?
Next
From: "Marc G. Fournier"
Date:
Subject: Re: Deadlock with tsearch2 index ...