Re: pg_class catalog question...

From: Thomas Hallgren <thomas(at)tada(dot)se>
To: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
Cc: "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>, Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_class catalog question...
Date: 2006-04-02 18:53:46
Message-ID: 44301DBA.80405@tada.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jim C. Nasby wrote:
> On Sat, Apr 01, 2006 at 05:42:34PM +0200, Thomas Hallgren wrote:
>
>> Why not simply a fixed number of bytes, i.e. byte(16) or octet(16)?
>> Hexadecimal is just a convenient human-readable representation.
>>
>
> Well, hex is much easier to deal with in many regards than raw bytes,
> though. But yes, the idea is that you'd just store raw bytes on disk.
> byte or octet would work fine if they existed.
>
IIRC, Oracle actually uses the term RAW. It makes sense I think. No
conversion applied, no nothing. Just simple raw data.

- thomas

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-04-02 19:18:50 Re: pg_class catalog question...
Previous Message Jim C. Nasby 2006-04-02 18:50:38 Re: pg_class catalog question...