From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [RFC] new digest datatypes, or generic fixed-len hex types? |
Date: | 2009-07-27 16:02:32 |
Message-ID: | 4A6DCF98.7040308@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Merlin Moncure wrote:
> On Mon, Jul 27, 2009 at 10:20 AM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
>> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
>>
>>> We've developed some code to implement fixed-length datatypes for well
>>> known digest function output (MD5, SHA1 and the various SHA2 types).
>>> These types have minimal overhead and are quite complete, including
>>> btree and hash opclasses.
>>>
>>> We're wondering about proposing them for inclusion in pgcrypto.
>>>
>> Wasn't this proposed and rejected before? (Or more to the point,
>> why'd you bother? The advantage over bytea seems negligible.)
>>
>
> well, one nice things about the fixed length types is that you can
> keep your table from needing a toast table when you have a bytea in
> it.
>
>
>
Can't you just set storage on the column to MAIN to stop it being stored
in a toast table?
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2009-07-27 16:05:07 | Re: Review: Revise parallel pg_restore's scheduling heuristic |
Previous Message | Kevin Grittner | 2009-07-27 15:54:23 | Re: Review: Revise parallel pg_restore's scheduling heuristic |