"Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> 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 ba
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 i
Josh Berkus writes:
> Hmmm ... how difficult would it be to give a useful error message instead of
> a
> SQL error? Something like:
> "I'm sorry, that PSQL command did not work. Most likely, you are connecting
> to a different version of PostgreSQL."
Well, "useful" is in the eye of the beho
Tom,
> Can you point to any single one of the past five major releases in which
> psql's backslash commands *WERE* completely backwards-compatible with
> previous versions of PostgreSQL? This is not breaking news.
Because this is the first time I can remember where *none* of the \ commands
work
Josh Berkus writes:
> I think we should put something in the release notes:
> WARNING: 8.1's "psql" is not completely backwards-compatible with previous
> versions of PostgreSQL.
Can you point to any single one of the past five major releases in which
psql's backslash commands *WERE* completely
On Tue, Aug 30, 2005 at 07:35:40PM -0400, Bruce Momjian wrote:
> Josh Berkus wrote:
> > Tom,
> >
> > > They've been broken on a fairly regular basis in past releases.
> > > Certainly 7.3 broke every single one because of the addition of
> > > schema syntax ...
> >
> > Yeah, and we warned people a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tom Lane wrote:
>>> This isn't a bug, it's a feature request. We've never had backwards
>>> compatibility of psql backslash commands.
>> In the past, most of these usually worked.
> They've been broken on a fairly regular basis in past releases.
>
Josh Berkus wrote:
> Tom,
>
> > They've been broken on a fairly regular basis in past releases.
> > Certainly 7.3 broke every single one because of the addition of
> > schema syntax ...
>
> Yeah, and we warned people about it, as I recall. Also, we had about 25x
> less users then. I think we
Tom,
> They've been broken on a fairly regular basis in past releases.
> Certainly 7.3 broke every single one because of the addition of
> schema syntax ...
Yeah, and we warned people about it, as I recall. Also, we had about 25x
less users then. I think we should put something in the releas
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> This isn't a bug, it's a feature request. We've never had backwards
>> compatibility of psql backslash commands.
> In the past, most of these usually worked.
They've been broken on a fairly regular basis in past releases.
Certainl
Tom Lane wrote:
> This isn't a bug, it's a feature request. We've never had backwards
> compatibility of psql backslash commands.
In the past, most of these usually worked. As it appears now, most of
them won't work at all, so we should really put a bigger warning sign
somewhere, because in sp
On Tue, Aug 30, 2005 at 12:09:03PM -0700, Josh Berkus wrote:
> Discovered some problems using 8.1 psql to connect to an 8.0 server:
>
> test_stats=# \l
> ERROR: relation "pg_catalog.pg_roles" does not exist
> test_stats=# \dt
> ERROR: relation "pg_catalog.pg_roles" does not exist
> test_stats=#
This isn't a bug, it's a feature request. We've never had backwards
compatibility of psql backslash commands.
There was some talk just a day or two ago about starting to support
that beginning in 8.2; it's not happening for 8.1 though.
regards, tom lane
-
Folks,
Discovered some problems using 8.1 psql to connect to an 8.0 server:
test_stats=# \l
ERROR: relation "pg_catalog.pg_roles" does not exist
test_stats=# \dt
ERROR: relation "pg_catalog.pg_roles" does not exist
test_stats=# \dv
ERROR: relation "pg_catalog.pg_roles" does not exist
This is
14 matches
Mail list logo