Skip site navigation (1) Skip section navigation (2)

Backend drops on empty result

From: Theo Kramer <theo(at)flame(dot)flame(dot)co(dot)za>
To: pgsql-ports(at)postgreSQL(dot)org
Subject: Backend drops on empty result
Date: 1999-03-08 20:16:27
Message-ID: 199903082016.WAA20784@flame.flame.co.za (view raw or flat)
Thread:
Lists: pgsql-ports
============================================================================
                        POSTGRESQL BUG REPORT TEMPLATE
============================================================================


Your name		: Theo Kramer
Your email address	: theo(at)flame(dot)co(dot)za

Category		: runtime: psql
Severity		: serious

Summary: psql commands

System Configuration
--------------------
  Operating System   : Redhat 5.0 Kernel 2.0.35

  PostgreSQL version : 6.5

  Compiler used      : gcc 2.7.2.3-8

Hardware:
---------
Pentium PRO 200 MHz 96 MByte Ram

Versions of other tools:
------------------------
make-3.76.1-2 

--------------------------------------------------------------------------
Problem Description:
--------------------
Commands in psql that return nothing cause backend to drop.

--------------------------------------------------------------------------

Test Case:
----------

The following illustrates the problem. Note that this is when no tables
have been created. Creating a table (no indexes) then \d works fine,
however, a command like \di then again causes the connection to the
backend to drop.


[postgres(at)flame postgres]$ psql template1
Welcome to the POSTGRESQL interactive sql monitor:
  Please read the file COPYRIGHT for copyright terms of POSTGRESQL

   type \? for help on slash commands
   type \q to quit
   type \g or terminate with semicolon to execute query
 You are currently connected to the database: template1

template1=> \d
pqReadData() -- backend closed the channel unexpectedly.
        This probably means the backend terminated abnormally
        before or while processing the request.
template1=> \q   
[postgres(at)flame postgres]$ 

--------------------------------------------------------------------------

Solution:
---------

Function pqReadData() closes the connection when nread == 0. Is this correct
when there is no result set??

--------------------------------------------------------------------------


Regards
Theo

pgsql-ports by date

Next:From: Unprivileged userDate: 1999-03-09 10:34:01
Subject: Port Bug Report: bad transaction support
Previous:From: AshokDate: 1999-03-08 16:25:24
Subject: Problem in installation

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group