| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Erik Rijkers <er(at)xs4all(dot)nl>, Michael Paquier <michael(at)paquier(dot)xyz>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, DUVAL REMI <REMI(dot)DUVAL(at)cheops(dot)fr>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: proposal: schema variables |
| Date: | 2024-11-16 14:34:58 |
| Message-ID: | CAFj8pRAX4Pmh_pNcOFF7r_hHkdDNnZ7iwEb_7JyxOzZ8ZrxpXA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
Hi
> As a side note, I've recently caught myself thinking "it would be cool to
> have
> session variables here". The use case was preparing a policy for RLS,
> based on
> some session-level data set by an application. This session-level data is
> of a
> composite data type, so simple current_setting is cumbersome to use, and a
> temporary table will be dropped at the end, taking the policy with it due
> to
> the recorded dependency between them. Thus a session variable of some
> composite
> type sounds like a good fit.
>
yes, RLS support is one mentioned use case, and strong reason the access
rights are implemented there.
Regards
Pavel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ranier Vilela | 2024-11-16 14:40:58 | Re: define pg_structiszero(addr, s, r) |
| Previous Message | Dmitry Dolgov | 2024-11-16 14:27:30 | Re: proposal: schema variables |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Wolfgang Walther | 2024-11-16 14:56:53 | Re: proposal: schema variables |
| Previous Message | Dmitry Dolgov | 2024-11-16 14:27:30 | Re: proposal: schema variables |