| From: | Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Configuring BLCKSZ and XLOGSEGSZ (in 8.3) |
| Date: | 2006-12-01 20:20:21 |
| Message-ID: | 45708E85.1000107@sun.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Tom Lane wrote:
> "Simon Riggs" <simon(at)2ndquadrant(dot)com> writes:
>> It seems possible to vary both BLCKSZ and XLOGSEGSZ rather than have
>> them set within pg_config_manual.
>
> The work required for this is much larger than you make it out to be,
> and zero evidence has been offered for any benefit. I have not heard of
> anyone bothering to use a custom BLCKSZ since we added TOAST to get rid
> of the row-length limitation ...
I think, Configurable BLCKSZ could be useful for regression test. See
hash index problem. Some kind of stress test could be check behavior on
different BLCKSZ without recompilation.
Zdenek
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2006-12-01 20:46:56 | Re: FOR SHARE vs FOR UPDATE locks |
| Previous Message | Merlin Moncure | 2006-12-01 20:11:59 | Re: FOR SHARE vs FOR UPDATE locks |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2006-12-01 23:04:05 | Dynamic Tracing docs |
| Previous Message | Tom Lane | 2006-11-30 06:30:15 | Re: elog(FATAL)ing non-existent roles during client authentication |