From: JanWieck@t-online.de
To: Peter Eisentraut <peter_e@gmx.net>
Cc: Wallingford, Ted <twallingford@indexc.com>
Cc: 'pgsql-admin@postgresql.org' <pgsql-admin@postgresql.org>
Cc: pgsql-sql@postgresql.orgg
Subject: Re: [SQL] Re: create view security
Date: Thu, 1 Jun 2000 04:24:58 +0200 (MEST)
Message-ID: <200006010224.EAA21189@hot.jw.home> (raw)
In-Reply-To: <Pine.LNX.4.21.0005312113390.701-100000@localhost.localdomain>
Peter Eisentraut wrote:
> Wallingford, Ted writes:
>
> > I am using 6.3 in this case.
>
> I'm sorry but that is pre-historic era around here and no one really
> remembers what the problems might have been back then (other than that
> they were surely plenty). Upgrading might be your best bet on all fronts.
You're wrong - I remember, not 100% sure, but good enough.
Just two weeks ago (funny - isn't it) I made a deal with a
friend, exchanging this old 486/33DLC, 8MB, 1GB portable
(640x480 gray but onboard SCSI!) with a planimeter (nice
mechanic tool that fit's perfectly into my sliderule
collection - that friend collects sliderules too so he knows
how to get me :-).
That old portable was the computer, most of the rule system
fixes for v6.4 where developed on. I'm pretty sure that the
Rule-Owner-Needs-Perm changes where part of it.
The executor is doing a permisson check of the result- and
all scan relations just before starting the execution. For
v6.4 (or was THAT in 6.5 - dunno exactly) I added a little
flag to the rangetable entry that tells "this relation is
accessed through a view and permissions are already checked".
Since then, it was the rewriter that checked if the view-
owner would have the permissions for all relations used by
the view.
Anyway, upgrading IS the best (if not the only) choice for
him.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck@Yahoo.com #
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: JanWieck@t-online.de, peter_e@gmx.net, twallingford@indexc.com, pgsql-admin@postgresql.org, pgsql-sql@postgresql.orgg
Subject: Re: [SQL] Re: create view security
In-Reply-To: <200006010224.EAA21189@hot.jw.home>
References: <Pine.LNX.4.21.0005312113390.701-100000@localhost.localdomain> <200006010224.EAA21189@hot.jw.home>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox