[PERFORM] LIMIT causes planner to do Index Scan using a less optimal index

2010-04-06 Thread Joel Jacobson
dex_transactions_eventid" btree (eventid) Foreign-key constraints: "transactions_accountid_fkey" FOREIGN KEY (accountid) REFERENCES accounts(accountid) DEFERRABLE "transactions_eventid_fkey" FOREIGN KEY (eventid) REFERENCES events(eventid) DEFERRABLE "transactions_ruleid_fkey" FOREIGN KEY (ruleid) REFERENCES rules(ruleid) DEFERRABLE -- Best regards, Joel Jacobson

Re: [PERFORM] LIMIT causes planner to do Index Scan using a less optimal index

2010-04-08 Thread Joel Jacobson
efeng Zhu (Sherry) > Crown Consulting Inc. -- Oracle DBA > AIM Lab Data Team > (703) 925-3192 > > > > *Sherry CTR Zhu/AWA/CNTR/FAA* > AJR-32, Aeronautical Information Mgmt Group > > 04/06/2010 03:13 PM > To > Robert Haas > cc > Joel Jacobson >

Re: [PERFORM] LIMIT causes planner to do Index Scan using a less optimal index

2010-04-08 Thread Joel Jacobson
nks much! > > Xuefeng Zhu (Sherry) > Crown Consulting Inc. -- Oracle DBA > AIM Lab Data Team > (703) 925-3192 > > > > *Joel Jacobson * > > 04/06/2010 06:30 PM > To > Sherry CTR Zhu/AWA/CNTR/f...@faa, pgsql-performance@postgresql.org > cc > Robe

[PERFORM] plpgsql plan cache

2010-02-22 Thread Joel Jacobson
single query. Still the index is not being used. When running the same query in the sql prompt, the index is in use though. Is there a way to someone clear the entire query cache or even better for a particular plpgsql function? I'm greatful for any ideas. Best regards, Joel Jac

Re: [PERFORM] plpgsql plan cache

2010-02-22 Thread Joel Jacobson
db=# \d FlagValueAccountingTransactions Table "public.flagvalueaccountingtransactions" Column| Type |Modifiers -+-- + -

Re: [PERFORM] plpgsql plan cache

2010-02-22 Thread Joel Jacobson
CUTING-DYN > > On Mon, Feb 22, 2010 at 2:58 PM, Joel Jacobson wrote: >> >> db=# \d FlagValueAccountingTransactions >>                                       Table >> "public.flagvalueaccountingtransactions" >&g

[PERFORM] Backup/restore of pg_statistics

2003-11-17 Thread Joel Jacobson
tatistics could then be restored thus making the planner produce "future-optimized" queries when the PL/pgSQL functions are created, even though the database is empty. I would greatly appreciate any help/comments. Thank you. Joel Jacobson <[EMAIL PROTECTED]> -