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

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

Merlin Moncure <mmoncure(at)gmail(dot)com> writes:
> On Mon, Jul 27, 2009 at 10:20 AM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> 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.

If you don't actually use the toast table, it doesn't cost anything very
noticeable ...

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2009-07-27 15:41:05 Re: When is a record NULL?
Previous Message Tom Lane 2009-07-27 15:27:41 Re: Non-blocking communication between a frontend and a backend (pqcomm)