| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com>, Joe Conway <mail(at)joeconway(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal: session server side variables |
| Date: | 2016-12-30 06:50:30 |
| Message-ID: | alpine.DEB.2.20.1612300742210.32017@lancre |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2016-12-30 07:13:13 | Re: BUG: pg_stat_statements query normalization issues with combined queries |
| Previous Message | Fabien COELHO | 2016-12-30 06:42:05 | Re: proposal: session server side variables |