Re: [HACKERS] proposal: session server side variables - Mailing list pgsql-hackers

From Fabien COELHO
Subject Re: [HACKERS] proposal: session server side variables
Date
Msg-id alpine.DEB.2.20.1612300742210.32017@lancre
Whole thread Raw
In response to Re: [HACKERS] proposal: session server side variables  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
Responses Re: [HACKERS] proposal: session server side variables  (Craig Ringer <craig@2ndquadrant.com>)
List pgsql-hackers
>> I know this one. It can be empty, which a singleton cannot be. For a 
>> singleton table, you should have one and only one row, you cannot insert or 
>> delete, so this is only part of the real thing.
>
> Surely we can do a bit better than that, if that's what you really want.
> Create the table with an initial row and add a trigger preventing anything 
> except update.

Yes.

I just meant that this is not available easily "out of the box", but it is 
obviously doable with some effort... which people would seldom do.

-- 
Fabien.



pgsql-hackers by date:

Previous
From: Fabien COELHO
Date:
Subject: Re: [HACKERS] proposal: session server side variables
Next
From: Fabien COELHO
Date:
Subject: Re: [HACKERS] BUG: pg_stat_statements query normalization issueswith combined queries