Re: Bug in ALTER LANGUAGE ... RENAME TO ...;

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Sergey N(dot) Yatskevich" <syatskevich(at)2100(dot)gosniias(dot)ru>
Cc: PostgreSQL BUGS <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Bug in ALTER LANGUAGE ... RENAME TO ...;
Date: 2005-02-14 06:52:22
Message-ID: 20952.1108363942@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> "Sergey N. Yatskevich" <syatskevich(at)2100(dot)gosniias(dot)ru> writes:
>> RenameLanguage procedure in src/backend/commands/proclang.c open
>> and update pg_catalog.pg_shadow table instead pg_catalog.pg_language.

> Wow. Apparently this has been broken since it was written, and
> nobody ever tested it. Thanks!

BTW, is there a security issue here? In my testing all I got was
harmless "tuple concurrently updated" failures --- but it seems like
this bug ought to result in either a core dump or storing a bogus row
into pg_shadow. Neither of which sound appealing.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Magnus Hagander 2005-02-14 08:56:40 Re: BUG #1478: Upper function does not work
Previous Message Oliver Jowett 2005-02-14 06:36:10 Re: PreparedStatement setObject