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
The following bug has been logged online:
Bug reference: 1856
Logged by: tk
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.0.3
Operating system: linux
Description:chinese sort error
Details:
chinese sort errorï¼ä¸ææåºä¸å¯¹ï¼
å¦æä¸ä¸ªè¡¨ä¸æä¸
On Aug 28, 2005, at 7:14 , Michael Fuhr wrote:Do you get the error if you execute "SET enable_bitmapscan TO off;" and then run EXPLAIN? This works fine, thanks. I'll wait for the next beta to try it without. It's just enough of a hassle for me to do a build that I don't want to keep them goi
12 matches
Mail list logo
