> 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 ?
pgsql-hackers by date
|Next:||From: Mark Cave-Ayland||Date: 2005-06-01 11:18:12|
|Subject: Re: Quick-and-dirty compression for WAL backup blocks|
|Previous:||From: Hannu Krosing||Date: 2005-06-01 09:54:58|
|Subject: Re: NOLOGGING option, or ?|