Re: [HACKERS] Running pgindent - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [HACKERS] Running pgindent
Date
Msg-id 199802201529.KAA04338@candle.pha.pa.us
Whole thread Raw
In response to Re: [HACKERS] Running pgindent  (jwieck@debis.com (Jan Wieck))
Responses Re: [HACKERS] Running pgindent  (jwieck@debis.com (Jan Wieck))
List pgsql-hackers
>
> >
> > >
> > > Bruce Momjian wrote:
> > > >
> > > > I want to run pgindent before the final release.  Who has outstanding
> > > > patches they are sitting on that would be affected by this?  Only places
> > > > where we have added non-conforming code would be affected.
> > >
> > > I'm changing bufmgr.c & elog.c to fix problems with smgrblind.
> > >
> > > Vadim
> > >
> >
> > Let me know when you would like it done.
>
>     Got very close to the view permission override - just a vew hours
>     for me :-)

Great.  I was thinking about this, and I think it would be best if the
view permissions were checked as the view owner at view USE time, not
view CREATION time, that way if permissions on the base tables change,
the permissions are properly honored.

I think the range table idea is good, so there is an OWNER field on each
range table which defaults to the current user.  As views are replaced
by base tables in the rewrite system, the owner can be changed to the
owner of the view.  The issue is whether the range table entry will be
available in the executor for you to access that owner field.  But at
this point, any fix for this would be great.  People are asking for this
view permissions thing.

Also, this makes non-super-user created views even harder, because if
people can create their own views, they can change the owner field to
anyone they want to, but that is for later.

--
Bruce Momjian
maillist@candle.pha.pa.us

pgsql-hackers by date:

Previous
From: Ronald Baljeu
Date:
Subject: Re: [HACKERS] Solution to the pg_user passwd problem !?? (c)
Next
From: Zeugswetter Andreas SARZ
Date:
Subject: Re: [HACKERS] Who is everyone?