Re: stupid subselect core dumps

From: "Vadim B(dot) Mikheev" <vadim(at)sable(dot)krasnoyarsk(dot)su>
To: "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu>
Cc: Postgres Hackers List <hackers(at)postgresql(dot)org>
Subject: Re: stupid subselect core dumps
Date: 1998-02-18 06:27:42
Message-ID: 34EA7F5E.FDCD8854@sable.krasnoyarsk.su
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thomas G. Lockhart wrote:
>
> I know this is too simple to be useful, but it was the first test case I
> tried for a regression test :)
>
> regression=> SELECT 1 AS one WHERE 1 IN (SELECT 1);
> PQexec() -- Request was sent to backend, but backend closed the channel
> before responding.
> This probably means the backend terminated abnormally before or
> while processing the request.
>
> Should we disallow parts of this in or near the parser, or can the
> backend possibly handle it?

Fixed. Patch for nodeResult.c follows.

Vadim

Attachment Content-Type Size
DF application/octet-stream 638 bytes

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas G. Lockhart 1998-02-18 06:54:18 Re: [HACKERS] Memory leaks for large objects
Previous Message Thomas G. Lockhart 1998-02-18 06:05:53 stupid subselect core dumps