From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCH] reloptions - RELOPT_KIND_ALL |
Date: | 2009-01-26 12:30:42 |
Message-ID: | 497DACF2.3040002@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Zdenek Kotala wrote:
> Alvaro Herrera píše v pá 23. 01. 2009 v 11:04 -0300:
>> Zdenek Kotala wrote:
>>> I attached patch which add capability to have single record for all
>>> realation kind in the reloption list. It is usefull in situation when
>>> all parameters are same for all relation kinds.
>> Do you have an example use case for this?
>
> I use it in my space reservation patch. I going to send it soon. The
> default value is zero in all relkind and max value as well. It seems to
> me waste a space to copy and paste same lines several times.
Aside from the other issues mentioned, ISTM the amount of space
reservation wanted depends on the exact changes across releases that
make that space reservation necessary in the first place. And depending
on what those changes are, the space reservation requirements could be
wildly different for each access and storage method.
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2009-01-26 13:01:48 | Re: Compiler warnings fix |
Previous Message | Peter Eisentraut | 2009-01-26 12:06:45 | Re: problem with archive_command as suggested by documentation |