Re: Can user specification of a column value be required when querying a view ? - Mailing list pgsql-general

From David Gauthier
Subject Re: Can user specification of a column value be required when querying a view ?
Date
Msg-id CAEs=6DnJsbA03tbWvQNOXcX0HwPuiRjxpBYLO4TQAFWjsirJ-Q@mail.gmail.com
Whole thread Raw
In response to Re: Can user specification of a column value be required when querying a view ?  (Christophe Pettus <xof@thebuild.com>)
List pgsql-general
OK, didn't think so, just checking.  Thanks for verifying ! 

On Mon, Nov 20, 2023 at 4:45 PM Christophe Pettus <xof@thebuild.com> wrote:


> On Nov 20, 2023, at 13:41, David Gauthier <dfgpostgres@gmail.com> wrote:
> I want the users to be required to provide a value for ssn in the following query...
> "select * from huge_view where ssn = '106-91-9930' "
> I never want them to query the view without specifying ssn.
> It has to do with resources and practicality.
>
> Is there a way to do that ?

Not in a way that PostgreSQL itself will enforce.  If you are concerned about a query running wild and taking up resources, setting statement_timeout for the user that will be running these queries is the best way forward.  A user that has general access to PostgreSQL and can run arbitrary queries will be able to craft a query that takes up a lot of system time and memory without too much trouble.

pgsql-general by date:

Previous
From: Christophe Pettus
Date:
Subject: Re: Can user specification of a column value be required when querying a view ?
Next
From: Alan Hodgson
Date:
Subject: Re: Can user specification of a column value be required when querying a view ?