Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 1A0AD989B4E for ; Wed, 11 Jan 2012 12:15:17 -0400 (AST) Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Rl0pU-0005t2-Su for pgsql-sql@postgresql.org; Wed, 11 Jan 2012 16:15:16 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id q0BGEwDH020906; Wed, 11 Jan 2012 11:14:58 -0500 (EST) To: Gerardo Herzig cc: pgsql-sql@postgresql.org Subject: Re: amount of join's and sequential access to the tables involved In-reply-to: <1326297994.28802.6.camel@inca.fmed.uba.ar> References: <1326296192.24629.12.camel@inca.fmed.uba.ar> <20152.1326296428@sss.pgh.pa.us> <1326297994.28802.6.camel@inca.fmed.uba.ar> Comments: In-reply-to Gerardo Herzig message dated "Wed, 11 Jan 2012 13:06:34 -0300" Date: Wed, 11 Jan 2012 11:14:58 -0500 Message-ID: <20905.1326298498@sss.pgh.pa.us> From: Tom Lane X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201201/40 X-Sequence-Number: 36211 Gerardo Herzig writes: > So, what happens, when a plsql function is excecuted, it takes is own > enviroment variables, or something like that? No, but it probably cached a plan from an execution before you changed join_collapse_limit ... regards, tom lane