Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: huge disparities in =/IN/BETWEEN performance
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: "George Pavlov" <gpavlov(at)mynewplace(dot)com>
- Cc: pgsql-sql(at)postgresql(dot)org
- Subject: Re: huge disparities in =/IN/BETWEEN performance
- Date: Thu, 08 Feb 2007 20:54:28 -0500
- Message-id: <7377(dot)1170986068(at)sss(dot)pgh(dot)pa(dot)us>
"George Pavlov" <gpavlov(at)mynewplace(dot)com> writes: > there is, admittedly, substantial complexity inside v_foo, with GROUP > BYs on user_id and various subqueries, but my basic thought is that > should not really matter... You're unlikely to get any useful comment on this when you have not shown any of those details, nor even an EXPLAIN. regards, tom lane
- Follow-Ups:
- Re: huge disparities in =/IN/BETWEEN performance
- From: George Pavlov
- Re: huge disparities in =/IN/BETWEEN performance
- References:
- huge disparities in =/IN/BETWEEN performance
- From: George Pavlov
- huge disparities in =/IN/BETWEEN performance
- Prev by Date: Re: Seeking quick way to clone a row, but give it a new pk.
- Next by Date: Re: huge disparities in =/IN/BETWEEN performance
- Previous by thread: huge disparities in =/IN/BETWEEN performance
- Next by thread: Re: huge disparities in =/IN/BETWEEN performance
- Indexes: