Re: [ADMIN] [PERFORM] poor performance in migrated database

2004-11-08 Thread Carlos Lopez
This is one of the queries that work,and is the first in a 4 level nested query where do I find how to interpret explains??? thanks in advance, Carlos. mate=# explain analyze select * from vdocinvdpre;

Re: [PERFORM] poor performance in migrated database

2004-11-07 Thread Troels Arvin
On Sat, 06 Nov 2004 11:52:15 -0800, Carlos Lopez wrote: I have migrated a database from MS SQL to a postgresSQL database, but when running it, the results are very slow (and unusable) which is the only reason we don't entirely move to postgresSQL. Have you run ANALYZE lately? (See manual.)

[PERFORM] poor performance in migrated database

2004-11-06 Thread Carlos Lopez
I have migrated a database from MS SQL to a postgresSQL database, but when running it, the results are very slow (and unusable) which is the only reason we don't entirely move to postgresSQL. The problem is that there are many nested views which normally join tables by using two fields, one

Re: [PERFORM] poor performance in migrated database

2004-11-06 Thread Troels Arvin
On Sat, 06 Nov 2004 11:52:15 -0800, Carlos Lopez wrote: I have migrated a database from MS SQL to a postgresSQL database, but when running it, the results are very slow (and unusable) which is the only reason we don't entirely move to postgresSQL.

Re: [PERFORM] poor performance in migrated database

2004-11-06 Thread Simon Riggs
On Sat, 2004-11-06 at 19:52, Carlos Lopez wrote: The problem is that there are many nested views which normally join tables by using two fields, one character and other integer. PostgreSQL has difficulty with some multi-column situations, even though in general it has a particularly good query

Re: [PERFORM] poor performance in migrated database

2004-11-06 Thread Scott Marlowe
On Sat, 2004-11-06 at 12:52, Carlos Lopez wrote: I have migrated a database from MS SQL to a postgresSQL database, but when running it, the results are very slow (and unusable) which is the only reason we don't entirely move to postgresSQL. The problem is that there are many nested views