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

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Cc: decibel <decibel(at)decibel(dot)org>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Subject: Re: [RFC] new digest datatypes, or generic fixed-len hex types?
Date: 2009-07-30 08:10:13
Message-ID: 200907301110.13603.peter_e@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wednesday 29 July 2009 20:16:48 decibel wrote:
> bytea doesn't cast well to and from text when you're dealing with hex
> data; you end up using the same amount of space as a varchar. What
> would probably work well is a hex datatype that internally works like
> bytea but requires that the input data is hex (I know you can use
> encode/decode, but that added step is a pain). A similar argument
> could be made for base64 encoded data.

There is a patch in the queue that adds hex input and output to bytea.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message KaiGai Kohei 2009-07-30 08:13:51 Re: SE-PostgreSQL Specifications
Previous Message Sergey V. Karpov 2009-07-30 07:46:57 Re: improvements for dict_xsyn extended synonym dictionary - RRR