Thread: JIT- on/off from postgres database

JIT- on/off from postgres database

From
Raj kumar
Date:
Hi ,

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.

Attached the screenshot.

Thanks,
Raj
Attachment

Re: JIT- on/off from postgres database

From
Laurenz Albe
Date:
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




Re: JIT- on/off from postgres database

From
Raj kumar
Date:
Hi Laurenz,

Thank you :)

Thanks,
Raj.

On Wed, Mar 4, 2020 at 2:29 PM Laurenz Albe <laurenz.albe@cybertec.at> wrote:
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