Couldn't we install the 9.1 and the new osm2pgsql in parallel, do a fresh import there and than switch over? Or isn't there enough disk space?
Julian 2011/9/12 Stephan Knauss <[email protected]> > On 12.09.2011 18:29, Kai Krueger wrote: > >> I hope somebody else could install the postgres_upgrade_fix. > > That's not so good either. > > If I understood it correctly the postgres_upgrade_fix is only relevant > > if one updates postgresql. However, as far as I know, postgresql wasn't > > upgraded and it is still running 8.3. So I doubt this will fix anything. > I had asked before. So if no upgrade happened this can't be the cause of > the corruption. The script would also only prevent it from getting > corrupted. > If we don't have a backup then I sound like the db needs to be rebuild. > > BTW: PostgreSQL 9.1 was just released... > and osm2pgsql main development branch no longer supports intarray. This > migration also needed a re-import. > > Is this a hint that we should do a big upgrade? > Could wait for the rendering to complete so we have some tiles still to > deliver while the db rebuilds for a day or two. > > > Stephan > > _______________________________________________ > Maps-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/maps-l >
_______________________________________________ Maps-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/maps-l
