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

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: 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 15:12:48
Message-ID: b42b73150907270812q69f985f8x73d02a2fd198aa25@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

merlin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-07-27 15:27:41 Re: Non-blocking communication between a frontend and a backend (pqcomm)
Previous Message Tom Lane 2009-07-27 15:09:28 Re: Review: support for multiplexing SIGUSR1