Horton

Re: Column rename in an extension update script

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Adrian Klaver <adrian.klaver@aklaver.com>
Cc: Philippe BEAUDOIN <phb.emaj@free.fr>, pgsql-general@postgresql.org
Date: 2017-05-03T17:29:57Z
Lists: pgsql-hackers, pgsql-general 
Adrian Klaver <adrian.klaver@aklaver.com> writes:
> On 04/30/2017 11:54 PM, Philippe BEAUDOIN wrote:
>> Just after the ALTER TABLE statement, I want to access this table. But
>> at this time, the altered column is not visible with its new name.

>  From the error it looks to me like the statements are each run in a 
> separate session and the UPDATE is not seeing the ALTER TABLE.

No, it's in the same session; the problem is the lack of a
CommandCounterIncrement call between the ALTER's update and the parsing
of the next statement.  That means the update isn't visible yet,
even in its own session.  See the fix here:

https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=9209e07605afe0349660447f20d83ef165cdd0ae

			regards, tom lane

Commits

  1. Ensure commands in extension scripts see the results of preceding DDL.

  2. Stamp 9.6.2.