Tom Lane wrote:
I suspect the fact that the pre-patch code made the "right" permissions
check was really coincidental, and that the correct fix will not involve
reversion of that patch but rather adding a facility somewhere to ensure
that the original view gets properly permission-checked even if t
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> On Fri, Dec 12, 2003 at 04:24:32AM +0100, Florian G. Pflug wrote:
>> Am I right to assume that updating to 7.4 will have the same effekt as
>> updating to 7.3.5?
> No, you're not. You can update to 7.3.5 by just dropping the new
> executables into plac
Tom Lane said:
> Hm. By rights it *should* fail, since the ACL is clearly not granting
UPDATE permissions to anybody.
>
> The fact that it fails to fail seems to be because the rules on
> pg_settings rewrite the UPDATE into DO INSTEAD NOTHING (which does
nothing, in particular makes no permission
Joe Conway <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> This fix may need to be rethought. I'm not sure though where is a clean
>> place to plug in the UPDATE permissions check given that the rules for
>> this case do not generate any UPDATE query.
> Do you want me to take a look at this, or
Tom Lane wrote:
Now, why does Florian see a permissions failure (which is really the
*right* behavior) when we don't? He didn't say exactly which PG version
he was running, but I see a likely-related bug fix between 7.3.2 and
7.3.3:
That seems to be it:
# psql regression
Welcome to psql 7.3.2, th
Florian G. Pflug wrote:
I installed a postgres-application (which was developed on debian woody)
on red hat 9 today, using the postgres 7.3 rpms from redhad.
One of my the triggers uses the pg_settings table (more precisely, it
updates that table to change the search_path temporarily). With the
Hi
I installed a postgres-application (which was developed on debian
woody) on red hat 9 today, using the postgres 7.3 rpms from redhad.
One of my the triggers uses the pg_settings table (more precisely, it
updates that table to change the search_path temporarily). With the
postgres 7.3 (and 7.
