Re: Proposal: SET ROLE hook

From: Joe Conway <mail(at)joeconway(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: Proposal: SET ROLE hook
Date: 2016-01-07 17:08:37
Message-ID: 568E9B95.5070406@joeconway.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 01/06/2016 10:36 AM, Tom Lane wrote:
> I think a design that was actually somewhat robust would require two
> hooks, one at check_role and one at assign_role, wherein the first one
> would do any potentially-failing work and package all required info into
> a blob that could be passed through to the assign hook.

Fair enough -- will rework the patch and example code.

Thanks!

Joe

--
Crunchy Data - http://crunchydata.com
PostgreSQL Support for Secure Enterprises
Consulting, Training, & Open Source Development

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jarred Ward 2016-01-07 17:28:29 Re: pglogical_output - a general purpose logical decoding output plugin
Previous Message Joe Conway 2016-01-07 17:04:27 Re: Multi-tenancy with RLS