Re: [RFC] new digest datatypes, or generic fixed-len hex types? - Mailing list pgsql-hackers

From Merlin Moncure
Subject Re: [RFC] new digest datatypes, or generic fixed-len hex types?
Date
Msg-id b42b73150907270812q69f985f8x73d02a2fd198aa25@mail.gmail.com
Whole thread Raw
In response to Re: [RFC] new digest datatypes, or generic fixed-len hex types?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [RFC] new digest datatypes, or generic fixed-len hex types?  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: [RFC] new digest datatypes, or generic fixed-len hex types?  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
On Mon, Jul 27, 2009 at 10:20 AM, Tom Lane<tgl@sss.pgh.pa.us> wrote:
> Alvaro Herrera <alvherre@commandprompt.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.

merlin


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Review: support for multiplexing SIGUSR1
Next
From: Tom Lane
Date:
Subject: Re: Non-blocking communication between a frontend and a backend (pqcomm)