Re: Problem displaying functions and views in 7.1b3 - Mailing list pgsql-bugs

From Constantin Teodorescu
Subject Re: Problem displaying functions and views in 7.1b3
Date
Msg-id 004101c091f6$b2018400$03ffe6c1@flex.ro
Whole thread Raw
In response to Problem displaying functions and views in 7.1b3  (pgsql-bugs@postgresql.org)
List pgsql-bugs
----- Original Message -----
From: "Tom Lane" <tgl@sss.pgh.pa.us>
To: "Hiroshi Inoue" <Inoue@tpf.co.jp>
Cc: <teo@flex.ro>; <pgsql-bugs@postgresql.org>
Sent: Thursday, February 08, 2001 4:12 AM
Subject: Re: [BUGS] Problem displaying functions and views in 7.1b3


> Hiroshi Inoue <Inoue@tpf.co.jp> writes:
> > Tom Lane wrote:
> >> Uh, has it ever done differently?  \df certainly appears to me to list
> >> all functions in 7.0.*.
>
> > There's the following code in src/bin/pgaccess/lib/mainlib.tcl
> >                 wpg_select $CurrentDB "select proname from pg_proc where
> > oid>$maxim order by proname" rec {
> > where maxim(the oid of "template1" database) is 1 in 7.1.
>
> Okay, so pgaccess has got a behavior change ... but the bug report was
> about psql, or so I thought.
>
> We can easily change pgaccess to do this correctly for 7.1, but then it
> will fail completely on older releases (there was no datlastsysoid column
> in pg_database before).  Is backward compatibility a design concern for
> pgaccess, or not?

We can detect the PostgreSQL version (select version();)  so we can
implement different behaviors.
if { $PG_VERSION >= 7} {
   wpg_select .....
} else {
  wpg_select ....
}

Constantin Teodorescu

pgsql-bugs by date:

Previous
From: Mike Howard
Date:
Subject: Referencial integerity problem
Next
From: Stephen van Egmond
Date:
Subject: Re: Backend crash while indexing large strings