[Dachs-support] [itteam] gavo import lock

[Markus Demleitner]

Hi Carlos,

On Mon, Nov 07, 2016 at 02:27:11PM -0200, carlosadean at linea.gov.br wrote:
> gavo=# begin;
> BEGIN
> gavo=# alter table tap_schema.columns add column junk smallint;
> ALTER TABLE
> gavo=# rollback;
> ROLLBACK
> 
> gavo=# \d tap_schema.columns
>      Table "tap_schema.columns"
>     Column    |   Type   | Modifiers 
> --------------+----------+-----------
>  sourcerd     | text     | 
>  column_index | smallint | 
> Indexes:
>     "columns_pkey" PRIMARY KEY, btree (table_name, column_name)

Phewy.  So at least postgres is sane :-)

> [gavo at devel2 ~]$ gavo upgrade
> >  Adding column_index column to TAP_SCHEMA.columns...  ok
> > ingesting column_index for TAP-published tables....** WARNING: Column name 'size' conincides with a ADQL/SQL reserved name.  This may lead to serious trouble later.  Please consider changing the name, or prepend quoted/ to make it a delimited identifier.
> ** WARNING: Somwhere near /opt/dachs/inputs/cluster/mag_auto_10023232_i.rd, (16, 51):  Column pixel may be null but has no explicit null value.
> ** WARNING: RD cluster/mag_auto_10023232_i couldn't be loaded (Element with id u'tilename' could not be located in parse context).  Fix and run gavo imp -m on it to get column indices in TAP_SCHEMA
> *X*X* Uncaught exception at toplevel
> *** Error: Oops.  Unhandled exception UnboundLocalError.
> 
> Exception payload: local variable 'rd' referenced before assignment
> 
> 
> Now I can see another error message and the column_index wasn't re-created.

Hm.  So, at least this is sane.

Anyway, if you fix the cluster/mag_auto_10023232_i (and potentially
other RDs flagged as faulty by gavo val ALL), does the upgrade work?

         -- Markus