AW: [PATCH] Re: Setuid functions - Mailing list pgsql-hackers

From Zeugswetter Andreas SB
Subject AW: [PATCH] Re: Setuid functions
Date
Msg-id 11C1E6749A55D411A9670001FA687963368344@sdexcsrv1.f000.d0188.sd.spardat.at
Whole thread Raw
Responses Re: AW: [PATCH] Re: Setuid functions
List pgsql-hackers
> > This patch will implement the "ENABLE PRIVILEGE" and "DISABLE PRIVILEGE"
> > commands   in PL/pgSQL, which, respectively, change the effective uid to that
> > of the function owner and back. It doesn't break security (I hope). The
> > commands can be abbreviated as "ENABLE" and "DISABLE" for the poor saps that

Anybody else want to object to this abbreviation idea ? Seems 
reading ENABLE; or DISABLE; is very hard to interpret in source code
(enable what ?) and should thus not be allowed (or allow "ENABLE PRIV").

Andreas


pgsql-hackers by date:

Previous
From: Hannu Krosing
Date:
Subject: Re: AW: Re: Re: REPLACE INTO table a la mySQL
Next
From: Zeugswetter Andreas SB
Date:
Subject: AW: Good name for new lock type for VACUUM?