Thanks, Jan.
Are you still at work?
--Walt (1.85254E-16ly tall) Weaver
-Original Message-
Sent: Friday, September 20, 2002 1:59 PM
To: Multiple recipients of list ORACLE-L
DBA/Developer/
7.0
JP
On Friday 20 September 2002 20:29, you wrote:
> Jan,
>
> Which version of PostgrSQL are y
7.0
JP
On Friday 20 September 2002 20:29, you wrote:
> Jan,
>
> Which version of PostgrSQL are you using?
>
> --Walt Weaver
> Bozeman, Montana
>
> -Original Message-
> Sent: Friday, September 20, 2002 11:35 AM
> To: Multiple recipients of list ORACLE-L
> DBA/Developer/
>
>
> We are usi
Jan,
Which version of PostgrSQL are you using?
--Walt Weaver
Bozeman, Montana
-Original Message-
Sent: Friday, September 20, 2002 11:35 AM
To: Multiple recipients of list ORACLE-L
DBA/Developer/
We are using PostgreSQL, but still have problems with statistics.
Sometimes after VACUUM
We are using PostgreSQL, but still have problems with statistics.
Sometimes after VACUUM ANALYZE optimizer doesn't use indexes
and performance goes down.
JP
On Friday 20 September 2002 18:43, you wrote:
> Ditto for PostgreSQL. For portability you can create a dual table but you
> have to ensure
Ditto for PostgreSQL. For portability you can create a dual table but you
have to ensure that it only has one row. ;-) I finding that portability
between PostgreSQL and Oracle is easier than most... same to_date, to_char
functions, and stuff. Seems like that's part of Postgres' strategy.
-
