Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from ) id 1j9PsQ-0001xL-Ei for pgsql-admin@arkaria.postgresql.org; Wed, 04 Mar 2020 08:59:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1j9PsO-0006fV-Va for pgsql-admin@arkaria.postgresql.org; Wed, 04 Mar 2020 08:59:36 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1j9PsO-0006fO-In for pgsql-admin@lists.postgresql.org; Wed, 04 Mar 2020 08:59:36 +0000 Received: from mail-wr1-x443.google.com ([2a00:1450:4864:20::443]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1j9PsK-000128-G7 for pgsql-admin@lists.postgresql.org; Wed, 04 Mar 2020 08:59:34 +0000 Received: by mail-wr1-x443.google.com with SMTP id n7so1310917wrt.11 for ; Wed, 04 Mar 2020 00:59:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20150623.gappssmtp.com; s=20150623; h=message-id:subject:from:to:date:in-reply-to:references:user-agent :mime-version:content-transfer-encoding; bh=sa8Bkst5zbrKvJgttAWcgwPcoz4sjcEE3YNfmLoibQk=; b=07tDvL/Ck/DMayL1iLW8q43x7k0cJnkvs7kxG/tsdHBr00qKcFxFZ+DfHZflV10AJa JJmztH4mYokYY4CwixJStuTLeIdXtrmuYEF7wvVByCNf6LHBoJ1CKXUw6PBHRGuZaCZc nbjuIUZF61TyGSWuTAlt2+OxvKArunSCoAqhXvbRNEBJZ3uyu72dDKMfH4K9HqNbatX9 vEmpSbUkFgiuS+lF19dutAj8+rIx+vG+JdCDD97vC7QJiEabSWm3WiS0rigqmagGovpq C73sOkiHbtbj0t3003JhTzSOR1MD753sCu46weJ7pa8jDOe7H6HUrdwom7J9n+TXN0sa HtZQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=sa8Bkst5zbrKvJgttAWcgwPcoz4sjcEE3YNfmLoibQk=; b=nYmneNsEnJJsL+eH5B04xMopwjKlQ45EPdeJQrdRV63a+wtLUYxY27Db2hEoz4u9HB WfV365Op53qgPocZmNk1vvhIfydLNiY5712oCh5CcP/x0v86Ryt9Tsah+O5h9lADMbKx uA93gxuC9xMW+oLX5z2LD8JacZdsyNrmr38378XKSNBIobMfoOQE4taosLiaEQIFZK0b 8/ssG/2elYlRTXHtnurRFnr5U4HGuj2wCpAYM8RvXJrs05R6LSBmH7wpbzO2DAgVm6k0 DAv0knM4t8GO50O24DwEUdyGaJhjkwueQlVjM+zzOdNiI4ZwvjdK6VJyH7Co+UQyuwxS it/g== X-Gm-Message-State: ANhLgQ23gBX7iSoXJJgLW6Km4LA7LcJS1PsCy51AmVwD0ssbETJabPGD g1MrpEgoD1ztSfZA0YPjFWGW5Q== X-Google-Smtp-Source: ADFU+vvGy6DPhFA/D9s5Tgkz4gy13oXGGuMFaMCXqo1g+bqHv+wsET8f9SXyUF+ebBg+4Ec4CBNjxw== X-Received: by 2002:a5d:4e8b:: with SMTP id e11mr74523wru.136.1583312370817; Wed, 04 Mar 2020 00:59:30 -0800 (PST) Received: from localhost.localdomain ([212.186.219.234]) by smtp.gmail.com with ESMTPSA id a7sm2915754wmj.12.2020.03.04.00.59.30 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 04 Mar 2020 00:59:30 -0800 (PST) Message-ID: <6e96e27ce4f93ceb9ab68cb5dfc2f34f0c00d575.camel@cybertec.at> Subject: Re: JIT- on/off from postgres database From: Laurenz Albe To: Raj kumar , pgsql-admin@lists.postgresql.org Date: Wed, 04 Mar 2020 09:59:29 +0100 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.32.5 (3.32.5-1.fc30) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Wed, 2020-03-04 at 14:20 +0530, Raj kumar wrote: > I am using Postgres 12. I could see that it is possible to set 'JIT' as 'ON/OFF' at user level as well as database level. > > Should I always executed these commands from 'postgres' database? Because, if I alter JIT value > for an application database where I am connected to that database, It is not getting reflected unless > otherwise I switch to a different database and switch back to the same application database. Parameters changed with ALTER DATABASE or ALTER ROLE won't take effect during the current session. You have to disconnect and reconnect. Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com