| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Subject: | Re: [RFC] new digest datatypes, or generic fixed-len hex types? |
| Date: | 2009-07-28 14:34:36 |
| Message-ID: | b42b73150907280734s28897444iac7f14e95c394052@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jul 28, 2009 at 7:15 AM, Peter Eisentraut<peter_e(at)gmx(dot)net> wrote:
> On Monday 27 July 2009 14:50:30 Alvaro Herrera wrote:
>> 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.
>>
> I think equipping bytea with a length restriction would be a very natural,
> simple, and useful addition. If we ever want to move the bytea type closer to
> the SQL standard blob type, this will need to happen anyway.
>
+1
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-07-28 14:35:01 | Re: question about the _SPI_save_plan() and plan cache |
| Previous Message | Kevin Grittner | 2009-07-28 14:28:46 | Re: Review: Revise parallel pg_restore's scheduling heuristic |