Re: [PERFORM] Any disadvantages of using =ANY(ARRAY()) instead of IN?

2012-05-13 Thread Noah Misch
On Tue, May 01, 2012 at 04:34:10PM +0200, Clemens Eisserer wrote: > select . from table1 ... left outer join table 15 WHERE > table1.id IN (select id join table16 ... join table20 WHERE > table20.somevalue=?) > > Starting with some amount of joins, the optimizer starts to do quite >

Re: [PERFORM] Maximum number of sequences that can be created

2012-05-13 Thread Craig James
On Sun, May 13, 2012 at 1:12 AM, Віталій Тимчишин wrote: > > > 2012/5/11 Robert Klemme > >> On Fri, May 11, 2012 at 12:50 PM, Vidhya Bondre >> wrote: >> > Is there any max limit set on sequences that can be created on the >> database >> > ? Also would like to know if we create millions of seque

Re: [PERFORM] Any disadvantages of using =ANY(ARRAY()) instead of IN?

2012-05-13 Thread Clemens Eisserer
Hello Noah, Thanks a lot for your feedback and explanations. > Since you have 15+ tables at the top level, the genetic query optimizer should > be kicking in and delivering a plan in reasonable time, albeit with plan > quality hazards.  There's a danger zone when the deterministic planner is > st

Re: [PERFORM] Maximum number of sequences that can be created

2012-05-13 Thread Robert Klemme
On Sun, May 13, 2012 at 10:12 AM, Віталій Тимчишин wrote: > 2012/5/11 Robert Klemme >> On the contrary: what would be the /advantage/ of being able to create >> millions of sequences?  What's the use case? > > We are using sequences as statistics counters - they produce almost no > performance i

Re: [PERFORM] Maximum number of sequences that can be created

2012-05-13 Thread Віталій Тимчишин
2012/5/11 Robert Klemme > On Fri, May 11, 2012 at 12:50 PM, Vidhya Bondre > wrote: > > Is there any max limit set on sequences that can be created on the > database > > ? Also would like to know if we create millions of sequences in a single > db > > what is the downside of it. > The sequences