From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Michael Glaesemann <grzm(at)seespotcode(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: exposing float8-as-value to PGXS/makefiles |
Date: | 2011-05-20 19:42:07 |
Message-ID: | 1305920501-sup-2912@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Excerpts from Michael Glaesemann's message of vie may 20 15:07:27 -0400 2011:
>
> On May 20, 2011, at 12:51, Alvaro Herrera wrote:
>
> > Excerpts from Tom Lane's message of vie may 20 12:43:25 -0400 2011:
> >> Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> >>> I was just messing around with a datatype that's based in int64
> >>> representation. Pretty much everything (seems to) work cleanly, but one
> >>> problem I have is that I cannot build the correct CREATE TYPE sentence
> >>> in the .sql.in file to actually install the type, because there's no
> >>> easy way to figure out whether float64 (and therefore int64) is passed
> >>> by value or not.
> >>
> >> We already solved that for contrib/isn --- use the LIKE clause in CREATE
> >> TYPE.
> >
> > Ooh, excellent, thanks.
>
> To confirm, this works for Postgres versions >= 8.4, correct?
Yes, this is in 8.4 (but not in 8.3).
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2011-05-20 21:45:18 | Re: inconvenient compression options in pg_basebackup |
Previous Message | Michael Glaesemann | 2011-05-20 19:07:27 | Re: exposing float8-as-value to PGXS/makefiles |