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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: PostGIS dropgeometrycolumn function (Was: Re: [7.4] "permissions problem" with pl/pgsql function )
Date: 2004-01-20 16:36:26
Message-ID: 24549.1074616586@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Marc G. Fournier" <scrappy(at)postgresql(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Marc G. Fournier 2004-01-20 16:50:48 Re: PostGIS dropgeometrycolumn function (Was: Re: [7.4]
Previous Message Tom Lane 2004-01-20 16:28:46 Re: [Fwd: plpgsql and booleans?]