From: | David Gauthier <dfgpostgres(at)gmail(dot)com> |
---|---|
To: | Christophe Pettus <xof(at)thebuild(dot)com> |
Cc: | 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-20 22:12:55 |
Message-ID: | CAEs=6DnJsbA03tbWvQNOXcX0HwPuiRjxpBYLO4TQAFWjsirJ-Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
OK, didn't think so, just checking. Thanks for verifying !
On Mon, Nov 20, 2023 at 4:45 PM Christophe Pettus <xof(at)thebuild(dot)com> 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.
From | Date | Subject | |
---|---|---|---|
Next Message | Alan Hodgson | 2023-11-21 00:24:12 | Re: Can user specification of a column value be required when querying a view ? |
Previous Message | Christophe Pettus | 2023-11-20 21:44:22 | Re: Can user specification of a column value be required when querying a view ? |