upgrade issues

[robe]

If I try to upgrade 1.4.0SVN to 1.4 beta -- doesn't work -- again not a biggie since I presume no one will be doing this. Just thought I would mention it. Gives:

ERROR: type "box3d_extent" already exists

Error

ERROR: type "box3d_extent" already exists SQL state: 42710

[pramsey]

Soft upgrade or hard? (postgis_upgrade.sql or the perl script)?

[robe]

the postgis_upgrade.sql

[pramsey]

Can you be clearer about where the issues begin and end? I just make a 1.3 database, loaded data, updated to 1.4 and built an index no problem. But perhaps I was misreading the ticket.

[pramsey]

There's no issue updating (actually it's downgrading) from 1.4.0SVN to 1.4b, because we have committed to no API changes. There will never be any functions to change, right? Maybe not. Somehow this script ends up having to be version-aware.

[robe]

Paul,

Sorry about that. I'm retracing my steps by reloading my database from 1.3.6 backup.

1) This is a database that has gone thru many upgrades (form 1.1) -- so loading it from a PostgreSQL 8.2 (1.3.6) to PostgreSQL 8.4 RC1

2) Then upgrading that using the postgis_upgrade.sql (first error I got was about my view vwtest -- so dropped that and reran script). Script said it was fine.

3) Did select postgis_full_version() -- stated I was running "POSTGIS="1.4.0b1" GEOS="3.1.1-CAPI-1.6.0" PROJ="Rel. 4.6.1, 21 August 2008" USE_STATS" (looks good)

3) Ran some queries -- super slow and Hmm I noticed non of my tables got the gist index (but forgot to check if they had them before the upgrade so this might be a restore issue or my 1.3.6 install on PostgreSQL 8.3).

4) Proceeded to build index on table -- bam ERROR: data type geometry has no default operator class for access method "gist" HINT: You must specify an operator class for the index or define a default operator class for the data type.

(Looked at my Operator Classes section and gist for geometry is missing).

I suspect this may be a false alarm that maybe there is something wrong with my 1.3.6 install on PostgreSQL 8.4

[pramsey]

Trying to replicate your situation (table with existing index, do upgrade) I'm not seeing the same effect, so I'm going to alter the description of this issue to exclude everything except the final case, which is the (upcoming) issue of 1.4.X upgrades, which won't work because the script is hard-coded to expect a 1.3->1.4 upgrade.