Skip site navigation (1) Skip section navigation (2)

Re: Bad copy-n-paste on character conversion fix - how screwed am I?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "C(dot) Bensend" <benny(at)bennyvision(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Bad copy-n-paste on character conversion fix - how screwed am I?
Date: 2005-05-03 01:47:39
Message-ID: 4471.1115084859@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-admin
"C. Bensend" <benny(at)bennyvision(dot)com> writes:
>    The following erroneous command was entered:
> UPDATE pg_proc SET proacl = '{=}'
> ;
>    .. instead of the correct one (missing the WHERE clause).  It
> updated 1747 rows - oh crap.

Always a good idea to do this kind of thing inside a BEGIN block ;-)

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.

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.

			regards, tom lane

In response to

Responses

pgsql-admin by date

Next:From: C. BensendDate: 2005-05-03 01:58:32
Subject: Re: Bad copy-n-paste on character conversion fix - how
Previous:From: C. BensendDate: 2005-05-03 01:16:22
Subject: Bad copy-n-paste on character conversion fix - how screwed am I?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group