Skip site navigation (1) Skip section navigation (2)

Re: Tablespace-level Block Size Definitions

From: "Zeugswetter Andreas DAZ SD" <ZeugswetterA(at)spardat(dot)at>
To: "Alvaro Herrera" <alvherre(at)surnet(dot)cl>,"Jonah H(dot) Harris" <jharris(at)tvi(dot)edu>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Tablespace-level Block Size Definitions
Date: 2005-06-01 11:07:57
Message-ID: E1539E0ED7043848906A8FF995BDA5790C5186@m0143.s-mxs.net (view raw or flat)
Thread:
Lists: pgsql-hackers
> The problem I see with this proposal is that the buffer manager knows
> how to handle only a equally-sized pages.  And the shared memory stuff
> gets sized according to size * num_pages.  So what happens if a certain
> tablespace A with pagesize=X gets to have a lot of its pages cached,
> evicting pages from tablespace B with pagesize=Y, where Y < X?

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 ? 

Andreas

Responses

pgsql-hackers by date

Next:From: Mark Cave-AylandDate: 2005-06-01 11:18:12
Subject: Re: Quick-and-dirty compression for WAL backup blocks
Previous:From: Hannu KrosingDate: 2005-06-01 09:54:58
Subject: Re: NOLOGGING option, or ?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group