Re: Row-level Security vs Application-level authz

From: David Steele <david(at)pgmasters(dot)net>
To: Stephen Frost <sfrost(at)snowman(dot)net>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Row-level Security vs Application-level authz
Date: 2015-02-24 18:10:30
Message-ID: 54ECBE96.6040500@pgmasters.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 2/23/15 8:16 PM, Stephen Frost wrote:
> * David G. Johnston (david(dot)g(dot)johnston(at)gmail(dot)com) wrote:
>> I take it that the table has to be permanent otherwise you would have
>> suggested
>> and unlogged temporary table as the target...
>
> A temporary table would have to be recreated each time and that'd be
> less than ideal. You can use a single unlogged table which includes the
> backend pid (which can be acquired through a function call) to keep
> track of which user is logged in on a given backend at a given point in
> time.

It's not clear to me why creating a temp table per session would be less
than ideal. I've certainly used session-scope temp tables to good
effect a number of times. Transaction-scope would be another story of
course.

Am I missing something?

--
- David Steele
david(at)pgmasters(dot)net

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Roxanne Reid-Bennett 2015-02-24 18:46:38 Re: What is the alternate of FILTER below Postgresql 9.4 ?
Previous Message Ramesh T 2015-02-24 18:08:14