Hello, > > If that does not help, you'll have to change the query probably. The > problem is the explain analyze you've provided > (http://explain.depesz.com/s/MY1) does not match the query from your > yesterday's post so we can't really help with it. Thanks for the pointers. I think I posted the same plan, may be the variable values changed. Anyway, I changed the query and now it comes back in 2 seconds. Here is the plan http://explain.depesz.com/s/n9S Interesting observation - PostgreSQL takes from 2 seconds to 20 minutes fetch the same data set of 2212 records, with slightly modified queries. Oracle is consistent (taking under 1 minute in both cases), though not consistently faster. The modified query is SELECT PFLMST.MEMSHPNUM, PFLMST.MEMSHPTYP, ACCMST.PRGCOD, CNTINF.EMLADR, CNTINF.CELISDCOD, CNTINF.CELARACOD, CNTINF.CELNUM, CNTINF.ADRLINONE , CNTINF.ZIPCOD, CNTINF.ADRTYP, (select ONE.FLDDES from COMONETIM ONE WHERE ONE.CMPCOD =ACCMST.CMPCOD AND ONE.FLDCOD='program.member.accountStatus' AND ONE.FLDVAL=ACCMST.ACCSTA)ACCSTA, (SELECT ONE1.FLDDES FROM COMONETIM ONE1 WHERE ONE1.CMPCOD =ACCMST.CMPCOD AND ONE1.FLDCOD='common.member.membershipStatus' AND ONE1.FLDVAL=PFLMST.MEMSHPSTA )MEMSHPSTA, INDINF.CMPNAM EMPNAM, INDINF.PRFADR, INDINF.GVNNAM GVNNAM, INDINF.FAMNAM FAMNAM, INDINF.MEMDOB MEMDOB FROM PRGMEMACCMST ACCMST JOIN EAIMEMPFLMST PFLMST ON ACCMST.CMPCOD = PFLMST.CMPCOD AND ACCMST.MEMSHPNUM = PFLMST.MEMSHPNUM JOIN EAICUSPFLCNTINF CNTINF ON CNTINF.CMPCOD = PFLMST.CMPCOD AND CNTINF.CUSNUM = PFLMST.CUSNUM LEFT JOIN EAICUSPFLINDINF INDINF ON INDINF.CMPCOD = PFLMST.CMPCOD AND INDINF.CUSNUM = PFLMST.CUSNUM WHERE ACCMST.CMPCOD= 'SA' AND UPPER(INDINF.FAMNAM) LIKE 'PRICE' || '%' ORDER BY UPPER(INDINF.GVNNAM), UPPER(INDINF.FAMNAM), UPPER(INDINF.CMPNAM)
Regards, Jayadevan
DISCLAIMER:
"The information in this e-mail and any attachment is intended only for the person to whom it is addressed and may contain confidential and/or privileged material. If you have received this e-mail in error, kindly contact the sender and destroy all copies of the original communication. IBS makes no warranty, express or implied, nor guarantees the accuracy, adequacy or completeness of the information contained in this email or any attachment and is not liable for any errors, defects, omissions, viruses or for resultant loss or damage, if any, direct or indirect."