Re: Disallow SET command in a postgresql server

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Fabio Rueda Carrascosa <avances123(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Disallow SET command in a postgresql server
Date: 2013-04-09 16:06:59
Message-ID: 20130409160659.GG3751@eldon.alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Fabio Rueda Carrascosa escribió:
> My grant/revoke architecture is fine, you mean about costly cpu/ram queries?

Sure. The SQL dialect supported by Postgres is Turing-complete, so
people can write statements that consume arbitrary amounts of RAM and
diskspace, and run for arbitrary amounts of time -- regardless of
work_mem and other settings. (Actually, this was true even before the
dialect got to be Turing-complete).

Please don't top-post.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message kiran 2013-04-09 16:07:43 Create a DBLink from PostrgeSQL 9.2 to Oracle 11g
Previous Message Fabio Rueda Carrascosa 2013-04-09 15:57:50 Re: Disallow SET command in a postgresql server