Received: from localhost (IDENT:root@hectic-2.jpl.nasa.gov [128.149.68.204]) by hub.org (8.9.3/8.9.3) with ESMTP id JAA62131 for ; Wed, 20 Oct 1999 09:15:16 -0400 (EDT) (envelope-from lockhart@alumni.caltech.edu) Received: from alumni.caltech.edu (lockhart@localhost [127.0.0.1]) by localhost (8.8.7/8.8.7) with ESMTP id NAA25513; Wed, 20 Oct 1999 13:14:10 GMT Sender: lockhart@hub.org Message-ID: <380DC022.ABD260C@alumni.caltech.edu> Date: Wed, 20 Oct 1999 13:14:10 +0000 From: Thomas Lockhart X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.0.36 i686) X-Accept-Language: en MIME-Version: 1.0 To: Oliver Elphick , Chuan-kai Lin CC: pgsql-interfaces@postgreSQL.org Subject: Re: [INTERFACES] Re: PostgreSQL-6.5.2-0.3 Comment References: <199910201038.LAA14600@linda.lfix.co.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > >I have recently installed your PostgreSQL 6.5.2-0.3 packages on my > >newly upgraded potato system. ODBC (which is the main purpose of > >the upgrade to your packages) seems to be fine, though I am still > >a little bit pissed about the dirty solution used to handle large > >objects. So far I have only encountered one problem: when I list > >all tables with \l under psql, psql disconnects itself from the > >backend automatically. Other operations, such as SQL queries, seem > >to work fine. Any ideas? > There are no Debian-specific issues involved, so I am forwarding this > to the PostgreSQL interfaces list. Perhaps someone will have some idea? Sure. Perhaps Mr. Lin would like to contribute a solution to whatever is upsetting him regarding large objects. Oh, that's not what you meant? ;) \l (which lists databases, not tables) behaves itself on my RH5.2 system with the current development tree. - Thomas postgres=> \l datname |datdba|encoding|datpath ---------+------+--------+--------- template1| 100| 0|template1 postgres | 100| 0|postgres (2 rows) -- Thomas Lockhart lockhart@alumni.caltech.edu South Pasadena, California