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

Re: PSQL commands not backwards-compatible

From: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>,Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-bugs(at)postgresql(dot)org,Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Subject: Re: PSQL commands not backwards-compatible
Date: 2005-08-31 19:09:38
Message-ID: 20050831190938.GC98175@pervasive.com (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-patches
On Wed, Aug 31, 2005 at 02:05:13PM -0400, Tom Lane wrote:
> I like this better than Bruce's recent proposal to print a warning at
> psql startup, because it emits the info when you actually need it.
> How many people pay attention to psql's startup banner at all?

Aren't there other compatability issues as well? The warning on \connect
seems like a good idea to me. Of course nothing says we can't do both...
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby(at)pervasive(dot)com
Pervasive Software        http://pervasive.com        512-569-9461

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2005-08-31 19:24:35
Subject: Re: PSQL commands not backwards-compatible
Previous:From: Tom LaneDate: 2005-08-31 18:05:13
Subject: Re: PSQL commands not backwards-compatible

pgsql-patches by date

Next:From: Tom LaneDate: 2005-08-31 19:24:35
Subject: Re: PSQL commands not backwards-compatible
Previous:From: Tom LaneDate: 2005-08-31 18:05:13
Subject: Re: PSQL commands not backwards-compatible

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