X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 6652553AE8 for ; Mon, 2 May 2005 22:58:37 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 39893-08 for ; Tue, 3 May 2005 01:58:28 +0000 (GMT) Received: from fusion.bennyvision.com (fusion.bennyvision.com [71.32.179.125]) by svr1.postgresql.org (Postfix) with SMTP id 5DCD5539C3 for ; Mon, 2 May 2005 22:58:27 -0300 (ADT) Received: (qmail 20209 invoked by uid 1007); 3 May 2005 01:58:32 -0000 Received: from localhost (HELO webmail.stinkweasel.net) (127.0.0.1) by fusion.bennyvision.com with SMTP; 3 May 2005 01:58:32 -0000 Received: from 63.227.74.41 (SquirrelMail authenticated user benny) by webmail.stinkweasel.net with HTTP; Mon, 2 May 2005 20:58:32 -0500 (CDT) Message-ID: <55769.63.227.74.41.1115085512.squirrel@webmail.stinkweasel.net> In-Reply-To: <4471.1115084859@sss.pgh.pa.us> References: <53520.63.227.74.41.1115082982.squirrel@webmail.stinkweasel.net> <4471.1115084859@sss.pgh.pa.us> Date: Mon, 2 May 2005 20:58:32 -0500 (CDT) Subject: Re: Bad copy-n-paste on character conversion fix - how From: "C. Bensend" To: pgsql-admin@postgresql.org User-Agent: SquirrelMail/1.4.4 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: by amavisd-new at hub.org X-Archive-Number: 200505/13 X-Sequence-Number: 17442 > Always a good idea to do this kind of thing inside a BEGIN block ;-) Yeah. That was the _second_ thing that came to mind. ;) > As far as the system functions are concerned, you can just set the > proacl column to NULL (ie, default) and that'll be fine for everything > except the character conversion functions. So, just to be sure: 1) Start a %(&@#*(&% transaction 2) Set the column to NULL for all rows, undoing my stupidity 3) Issue the CORRECT SQL statement, and that will take care of the character conversion problem 4) COMMIT said transaction after verifying that I'm not doing something stupid _again_ Is this correct? > As far as user-defined functions are concerned, NULL probably works for > most of them too, but you would want to consult a recent backup to see > if any were not like that. Happily, I am a novice at this, and I do not have any user-defined functions. Very simple database. :) Thank you so much! Benny -- "You come from a long line of scary women." -- Ranger, "Three To Get Deadly"