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

Port Bug Report: Commands in psql that return nothing cause connection to backend to be closed

From: Unprivileged user <nobody>
To: pgsql-ports(at)postgresql(dot)org
Subject: Port Bug Report: Commands in psql that return nothing cause connection to backend to be closed
Date: 1999-03-10 05:31:05
Message-ID: 199903100531.AAA52693@hub.org (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: front-end
Severity		: serious

Summary: Commands in psql that return nothing cause connection to backend to be closed

System Configuration
--------------------
  Operating System   : Redhat 5.0 (2.0.35)

  PostgreSQL version : 6.5

  Compiler used      : gcc 2.7.2.3-8

Hardware:
---------
Pentium PRO 200 MHz 96 MByte Ram
Linux flame.flame.co.za 2.0.35 #1 Thu Jul 23 14:01:04 EDT 1998 i686 unknown

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

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

Problem Description:
--------------------
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 backend to drop.


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

Test Case:
----------
[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


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

Solution:
---------
Suggestion/Question: Function pqReadData() closes the connection when nread == 0. Is this correct
when there is no result set??

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


pgsql-ports by date

Next:From: Larry HerbisonDate: 1999-03-10 22:26:29
Subject: Install feedback
Previous:From: ming lap chowDate: 1999-03-10 02:02:40
Subject: trouble running "intdb"

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