X-Original-To: pgsql-sql@postgresql.org Received: from candle.pha.pa.us (momjian.navpoint.com [207.106.42.251]) by postgresql.org (Postfix) with ESMTP id B2C4D474E4F for ; Thu, 6 Mar 2003 14:53:42 -0500 (EST) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.10.1) id h26JrU624270; Thu, 6 Mar 2003 14:53:30 -0500 (EST) From: Bruce Momjian Message-Id: <200303061953.h26JrU624270@candle.pha.pa.us> Subject: Re: Relation "pg_relcheck" In-Reply-To: <6288.1046293754@sss.pgh.pa.us> To: Tom Lane Date: Thu, 6 Mar 2003 14:53:30 -0500 (EST) Cc: Tilo Schwarz , pgsql-sql@postgresql.org X-Mailer: ELM [version 2.4ME+ PL99 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200303/169 X-Sequence-Number: 12209 Tom Lane wrote: > Tilo Schwarz writes: > > Because this sort of questions appears quite often, I was wondering, if the > > start up message of psql could be changed from > > Welcome to psql 7.4devel, the PostgreSQL interactive terminal. > > to something like > > Welcome to psql 7.4devel, the PostgreSQL interactive terminal. > > Connected to PostgreSQL . > > to make it easier to catch these errors. > > I'm not eager to add yet another hidden query cycle to the connection > startup overhead, especially not one that does nothing for people who > aren't making mistakes ;-). What's been in the back of my mind is that > when we redesign the FE/BE protocol (real soon now, I hope) we should > extend the backend's first message to the frontend to include its > version number, as well as any other useful info we can think of > (database encoding and default client encoding come to mind). This Added to TODO: > o Report server version number, database encoding, client encoding -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073