On Tue, Jan 28, 2003 at 08:24:13PM +0100, Peter Eisentraut wrote:
> Bruce Momjian writes:
>
> > we need someone to get MONEY working as an extented NUMERIC type.
>
> How would the new "money" be different from "numeric"? If we have
> "money", should we have "length", "mass", and "temperature"?
On Tue, Jan 28, 2003 at 17:47:14 -0500, tom lane wrote:
[...]
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > How would the new "money" be different from "numeric"?
>
> [ temporarily re-dons currency-trader hat... ]
>
> What would actually be useful is a money type that carries along an
> in
The problem here is not that we are getting rid of MONEY as datatype, (I see
no need for it with having numeric) the problem comes from haveing no way to
migrate MONEY to NUMERIC short of hand editing the pgdump file and then
reimporting. Yes I know I can use sed, but that is not the point. I
Darcy Buskermolen <[EMAIL PROTECTED]> writes:
> In 7.1 and prior I could do a SELECT '1.0'::MONEY::TEXT or to NUMERIC
> or to FLOAT even.
No, you couldn't.
regression=# SELECT '1.0'::MONEY::TEXT ;
ERROR: Cannot cast type 'money' to 'text'
regression=# select version();
Sorry my mistake on versions.
darcy=> SELECT '1.0'::MONEY::FLOAT;
?column?
1
(1 row)
darcy=> SELECT '1.0'::MONEY::TEXT;
?column?
1.0
(1 row)
darcy=> select version();
version
-
Darcy Buskermolen <[EMAIL PROTECTED]> writes:
> Sorry my mistake on versions.
> darcy=> SELECT '1.0'::MONEY::FLOAT;
> ?column?
>
>1
> (1 row)
> darcy=> select version();
> version
> ---
Tom you are correct here (like usual), sorry for the wasted thread and time
regarding functions that I remembered being there but infact were not.
On Wednesday 29 January 2003 10:56, Tom Lane wrote:
> Darcy Buskermolen <[EMAIL PROTECTED]> writes:
> > Sorry my mistake on versions.
> > darcy=> SEL
Chris Brown ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
PQconnectdb SEGV
Long Description
In the libpq C interface, PQconnectdb results in a SEGV when the conn->sock number is
greater than __FD_SETSIZE (1024 on linux). The
[EMAIL PROTECTED] writes:
> In the libpq C interface, PQconnectdb results in a SEGV when the conn->sock number
>is greater than __FD_SETSIZE (1024 on linux). The crash is caused by stack
>corruption when attempting to FD_SET.
Shouldn't you be filing this bug against libc? Seems to me the
left
