| From: | Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com>, Fabien <coelho(at)cri(dot)ensmp(dot)fr> |
| Cc: | PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: parametric block size? |
| Date: | 2014-07-27 00:39:32 |
| Message-ID: | 53D44A44.10008@catalyst.net.nz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 26/07/14 21:05, Andres Freund wrote:
>
>> More advanced features, but with much more impact on the code, would be to
>> be able to change the size at database/table level.
>
> That'd be pretty horrible because the size of pages in shared_buffers
> wouldn't be uniform anymore.
>
>
Possibly stopping at the tablespace level might be more straightforward.
To avoid messing up the pages in shared buffers we'd perhaps need
something like several shared buffer pools - each with either its own
blocksize or associated with a (set of) tablespace(s).
Obviously this sort of thing has a pretty big architecture/code impact,
probably better to consider a 1st iteration with it being initdb
specifiable only (as that would still be very convenient)!
Regards
Mark
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2014-07-27 04:44:22 | Re: PL/PgSQL: EXIT USING ROLLBACK |
| Previous Message | Andrew Dunstan | 2014-07-26 23:44:59 | Re: building pdfs |