From: | SAKAIDA <sakaida(at)psn(dot)co(dot)jp> |
---|---|
To: | pgsql-hackers(at)postgreSQL(dot)org |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Subject: | Re: psql \l error |
Date: | 2000-05-02 09:17:13 |
Message-ID: | 390E9D19280.E184SAKAIDA@smtp.psn.ne.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Eisentraut <e99re41(at)DoCS(dot)UU(dot)SE> wrote:
> On Tue, 2 May 2000, Tom Lane wrote:
>
> > I think there are some other small incompatibilities between 7.0 psql
> > and pre-7.0 servers anyway, so eliminating this one by dumbing down \l
> > is probably not the way to proceed.
>
> The oidvector thing is essentially a show stopper for this.
In my client software named PGBASH-2.1, I have dealt with "\l"
compatibility problem as following.
query1= SELECT pg_database.datname ..
pg_encoding_to_char(pg_database.encoding) as \"Encoding\" ..
..
query2= SELECT pg_database.datname ..
pg_database.encoding as \"Encoding\" ..
..
1. Make pset->quiet quiet mode.
2. Send query1.
3. Make pset->quiet original mode.
3. If error occurs then send query2.
--
Regards,
SAKAIDA Masaaki -- Osaka, Japan
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Inoue | 2000-05-02 10:15:37 | Re: psql \l error |
Previous Message | Peter Eisentraut | 2000-05-02 08:50:36 | Re: When malloc returns zero ... |