Re: PG 7.0 crash on SELECT - Mailing list pgsql-hackers

From Tom Lane
Subject Re: PG 7.0 crash on SELECT
Date
Msg-id 6467.960145026@sss.pgh.pa.us
Whole thread Raw
In response to PG 7.0 crash on SELECT  (Louis-David Mitterrand <cunctator@apartia.ch>)
List pgsql-hackers
Louis-David Mitterrand <cunctator@apartia.ch> writes:
> Issuing the followin SELECT crashes PG 7.0:
> auction=# SELECT a.id,a.title,a.id,(select CASE WHEN a.stopdate < 'now' THEN 'closed' ELSE 'open' end) as
status,to_char(a.time,'DD-MMHH24:MI'),b.price FROM auction* a, bid b WHERE a.id = b.auctionid AND b.login = 'mito2';
 
> pqReadData() -- backend closed the channel unexpectedly.
>         This probably means the backend terminated abnormally
>         before or while processing the request.
> The connection to the server was lost. Attempting reset: Failed.
> !# \q

> Apparently PG doesn't like the (SELECT CASE ... ) statement, until I
> added it everything went well. 

The crash certainly is a bug, but you could get around it for now
by not using an unnecessary sub-SELECT.  Why not just...,a.id,(CASE WHEN ...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: AW: AW: Proposal for enhancements of privilege system
Next
From: Tom Lane
Date:
Subject: Re: Variable formatting of datetime with DateStyle=ISO