X-Original-To: pgsql-sql@postgresql.org
Received: from davinci.ethosmedia.com (unknown [209.10.40.251])
	by svr1.postgresql.org (Postfix) with ESMTP id 85C5FEF663
	for <pgsql-sql@postgresql.org>; Wed,  4 Jun 2003 04:15:53 +0000 (GMT)
Received: from [66.219.92.2] (HELO temoku)
	by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2)
	with ESMTP id 3087471 for pgsql-sql@postgreSQL.org;
	Mon, 02 Jun 2003 15:50:11 -0700
Content-Type: text/plain;
  charset="us-ascii"
From: Josh Berkus <josh@agliodbs.com>
Reply-To: josh@agliodbs.com
Organization: Aglio Database Solutions
To: pgsql-sql@postgreSQL.org
Subject: Change owner of function in 7.2.4?
Date: Mon, 2 Jun 2003 15:49:33 -0700
User-Agent: KMail/1.4.3
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200306021549.33228.josh@agliodbs.com>
X-Archive-Number: 200306/45
X-Sequence-Number: 13803

Folks,

I have a 7.2.4 database where I accidentally replaced a bunch of functions=
=20
while logged in as the superuser.   Now the normal applicaiton user can't=
=20
modify them.  While I can fix them by dropping the functions as the superus=
er=20
and re-creating them as the regular user, I can't see how to do this in a=
=20
transaction to avoid disrupting the database users.

Are there any dangers I don't know about in either of the options below?
1) updating "proowner" in pg_proc
2) making the regular user a superuser temporarily, replacing the functions=
,=20
and then switching them back.

Thoughts?

--=20
-Josh Berkus
 Aglio Database Solutions
 San Francisco