From: | James Harper <james(dot)harper(at)bendigoit(dot)com(dot)au> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: semi-variable length type |
Date: | 2014-02-21 06:26:27 |
Message-ID: | 6035A0D088A63A46850C3988ED045A4B6F3AE2ED@BITCOM1.int.sbss.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
>
> James Harper <james(dot)harper(at)bendigoit(dot)com(dot)au> writes:
> > I want to make a float(n) type that emulates the mssql float type. The
> > storage requirements are documented as 4 bytes for 1 <= n <=24, and 8
> > bytes for 25 <= n <= 53.
>
> Haven't we got that already?
>
> regression=# create table t1 (f1 float(5), f2 float(30));
> CREATE TABLE
> regression=# \d t1
> Table "public.t1"
> Column | Type | Modifiers
> --------+------------------+-----------
> f1 | real |
> f2 | double precision |
>
> Other than the fact that we don't remember whether you asked for 5 bits
> or 24, I think this meets the spec requirements.
>
Is the 4 byte or 8 byte decision based on (n) implemented in the parser? I can't see a 'float' type in pg_type.
Thanks
James
From | Date | Subject | |
---|---|---|---|
Next Message | Torsten Förtsch | 2014-02-21 08:17:47 | How to continue streaming replication after this error? |
Previous Message | Tom Lane | 2014-02-21 06:09:51 | Re: semi-variable length type |