From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Gregory Stark <stark(at)enterprisedb(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Reducing NUMERIC size for 8.3 |
Date: | 2007-09-25 15:44:27 |
Message-ID: | 46F92CDB.5010909@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Zdenek Kotala wrote:
> Tom Lane wrote:
>> Gregory Stark <stark(at)enterprisedb(dot)com> writes:
>>> We previously discussed compressing the numeric data type for small
>>> values:
>>> http://archives.postgresql.org/pgsql-hackers/2007-06/msg00715.php
>>
>>> We didn't do this for 8.3 but in any case Tom did suggest we ought
>>> to reverse
>>> the weight and sign/dscale so we could do this sometime without
>>> introducing
>>> another incompatibility.
>>
>> I had forgotten about that, but it does seem like a good idea to do
>> it now.
>> Any objections?
>
> For in-place upgrade purpose It would be good change also OID for
> numeric type and preserve current OID for current implementation on
> updated system.
>
>
>
If we want to get into that game we need a better way of allocating
Oids. Right now anything not currently used is liable to be grabbed, so
there's a high risk of reuse.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Kenneth Marshall | 2007-09-25 16:26:05 | Re: Hash index todo list item |
Previous Message | Zdenek Kotala | 2007-09-25 15:28:24 | Re: Reducing NUMERIC size for 8.3 |