Re: [COMMITTERS] pgsql: Automatic view update rules Bernd Helmle

From: Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org, Bernd Helmle <mailings(at)oopsware(dot)de>
Subject: Re: [COMMITTERS] pgsql: Automatic view update rules Bernd Helmle
Date: 2009-01-27 21:23:09
Message-ID: 3073cc9b0901271323j29d5f09ci71bf9ebdf801bdff@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Tue, Jan 27, 2009 at 3:36 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
>> On Tuesday 27 January 2009 17:19:28 Tom Lane wrote:
>>> It's a potential security hole, since GRANT ALL on a view used to
>>> be de facto the same as GRANT SELECT, if you hadn't bothered to
>>> create any rules.
>
>> That is a good point. But the only clean solution would be to make views
>> never updatable by default, and invent a nonstandard syntax to make them so,
>> which seems very unattractive to me. A GUC variable as a transition measure
>> could work, though.
>
> Yeah, I tend to prefer the GUC approach over nonstandard syntax too.
> We'd need a GUC anyway to determine the default behavior if no
> nonstandard clause appeared; so we might as well just do that and not
> bother with the syntax options.
>

+1

--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message User Mkz 2009-01-28 10:59:27 pgbouncer - pgbouncer: duh, seems we did not include COPYRIGHT file in
Previous Message Tom Lane 2009-01-27 20:36:01 Re: [COMMITTERS] pgsql: Automatic view update rules Bernd Helmle

Browse pgsql-hackers by date

  From Date Subject
Next Message Devrim GÜNDÜZ 2009-01-27 21:26:06 Re: 8.4 release planning
Previous Message Stephen Frost 2009-01-27 21:14:05 Re: 8.4 release planning