Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id D7B1B9552D5 for ; Tue, 28 Feb 2012 15:28:20 -0400 (AST) Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1S2Sig-0003Lx-1l for pgsql-performance@postgresql.org; Tue, 28 Feb 2012 19:28:19 +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 q1SJS4gI009467; Tue, 28 Feb 2012 14:28:04 -0500 (EST) To: Jon Nelson cc: pgsql-performance@postgresql.org Subject: Re: problems with set_config, work_mem, maintenance_work_mem, and sorting In-reply-to: References: Comments: In-reply-to Jon Nelson message dated "Tue, 28 Feb 2012 13:16:27 -0600" Date: Tue, 28 Feb 2012 14:28:03 -0500 Message-ID: <9466.1330457283@sss.pgh.pa.us> From: Tom Lane X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201202/253 X-Sequence-Number: 46425 Jon Nelson writes: > The config shows 128MB for work_mem and 2GB for maintenance_work_mem. > Why does PostgreSQL /sometimes/ use the globally-configured values and > sometimes use the values that come from the connection? You sure those log entries are all from the same process? regards, tom lane