Re: Bug in ALTER LANGUAGE ... RENAME TO ...; - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Bug in ALTER LANGUAGE ... RENAME TO ...;
Date
Msg-id 20952.1108363942@sss.pgh.pa.us
Whole thread Raw
In response to Re: Bug in ALTER LANGUAGE ... RENAME TO ...;  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
> "Sergey N. Yatskevich" <syatskevich@2100.gosniias.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

pgsql-bugs by date:

Previous
From: Oliver Jowett
Date:
Subject: Re: PreparedStatement setObject
Next
From: "Magnus Hagander"
Date:
Subject: Re: BUG #1478: Upper function does not work