Seems this still fails. Hackers, does the crash cause other backends to
abort?
>
> Hello,
>
> I was just experimenting, trying to see if I could find a function that
> would format a numeric value like 'money' with Postgres 7.0.2. Here's
> what happened:
>
> ##
> cascade=> select cash_o
Bruce Momjian <[EMAIL PROTECTED]> writes:
>> cascade=> select cash_out(2);
>> pqReadData() -- backend closed the channel unexpectedly.
> I can confirm this is crashes in 7.1 too.
You can get this sort of result with almost any input or output function
:-(. The problem is that they're mostly mis
Added to TODO:
* SELECT cash_out(2) crashes because of opaque
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> >> cascade=> select cash_out(2);
> >> pqReadData() -- backend closed the channel unexpectedly.
>
> > I can confirm this is crashes in 7.1 too.
>
> You can get this sort of resul
I can confirm this is crashes in 7.1 too.
>
> Hello,
>
> I was just experimenting, trying to see if I could find a function that
> would format a numeric value like 'money' with Postgres 7.0.2. Here's
> what happened:
>
> ##
> cascade=> select cash_out(2);
> pqReadData() -- backend closed
Hello,
I was just experimenting, trying to see if I could find a function that
would format a numeric value like 'money' with Postgres 7.0.2. Here's
what happened:
##
cascade=> select cash_out(2);
pqReadData() -- backend closed the channel unexpectedly.
This probably means the back
