From: | Alan Hodgson <ahodgson(at)lists(dot)simkin(dot)ca> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Can user specification of a column value be required when querying a view ? |
Date: | 2023-11-21 00:24:12 |
Message-ID: | 73acc1a178aa851f6f5a424d6874a157ca0db2f7.camel@lists.simkin.ca |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, 2023-11-20 at 13:44 -0800, Christophe Pettus wrote:
>
>
> > On Nov 20, 2023, at 13:41, David Gauthier <dfgpostgres(at)gmail(dot)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.
If it's really about SSN's it might be more about bulk access to PII
than performance.
A function is probably the right choice in either case.
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2023-11-21 00:26:32 | Re: Prepared statements versus stored procedures |
Previous Message | David Gauthier | 2023-11-20 22:12:55 | Re: Can user specification of a column value be required when querying a view ? |