Re: PostGIS dropgeometrycolumn function (Was: Re: [7.4] "permissions problem" with pl/pgsql function ) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: PostGIS dropgeometrycolumn function (Was: Re: [7.4] "permissions problem" with pl/pgsql function )
Date
Msg-id 24549.1074616586@sss.pgh.pa.us
Whole thread Raw
In response to PostGIS dropgeometrycolumn function (Was: Re: [7.4] "permissions problem" with pl/pgsql function )  ("Marc G. Fournier" <scrappy@postgresql.org>)
Responses Re: PostGIS dropgeometrycolumn function (Was: Re: [7.4]
List pgsql-hackers
"Marc G. Fournier" <scrappy@postgresql.org> writes:
> On Mon, 19 Jan 2004, Tom Lane wrote:
>> in particular, what SQL command is it trying to execute when it chokes?

> The function is executing:

>     EXECUTE ''update pg_attribute set attnotnull = false from pg_class where
>                   pg_attribute.attrelid = pg_class.oid and pg_class.relname = '' ||
>                   quote_literal(table_name) ||'' and pg_attribute.attname = '' ||
>                   quote_literal(column_name);

Well, no wonder.  You have to be superuser to do that, and it's a pretty
bad idea even then.

We do have ALTER TABLE ... SET/DROP NOT NULL since 7.3, so hacking
pg_attribute directly isn't necessary for this anymore.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [Fwd: plpgsql and booleans?]
Next
From: "Marc G. Fournier"
Date:
Subject: Re: PostGIS dropgeometrycolumn function (Was: Re: [7.4]