Re: [OSM-dev] Exhaustion of 32bit signed integer range expected this year

2012-07-12 Thread mick
On Wed, 11 Jul 2012 22:32:30 -0700 (PDT) Kai Krueger wrote: > SimonPoole wrote > > > > It seems as if it would really make sense to make the 64bit ID version > > of osm2pgsql the default now and communicate that it might be a good > > idea to switch on the upcoming reload. > > > So I'll bring

Re: [OSM-dev] Exhaustion of 32bit signed integer range expected this year

2012-07-11 Thread Kai Krueger
SimonPoole wrote > > RSN a large number of sites using OSM data will be reloading their > databases, due to a certain well known change :-). > Well, this time has come closer now... SimonPoole wrote > > It seems as if it would really make sense to make the 64bit ID version > of osm2pgsql th

Re: [OSM-dev] Exhaustion of 32bit signed integer range expected this year

2012-04-14 Thread Frederik Ramm
Hi, On 04/13/2012 04:42 PM, Simon Poole wrote: It seems as if it would really make sense to make the 64bit ID version of osm2pgsql the default now and communicate that it might be a good idea to switch on the upcoming reload. Do we have any idea what the actual impact on DB size etc is? I hav

Re: [OSM-dev] Exhaustion of 32bit signed integer range expected this year

2012-04-13 Thread Derick Rethans
On Fri, 13 Apr 2012, David Earl wrote: > On 13/04/2012 15:15, Frederik Ramm wrote: > > This means that it is likely that by the end of 2012, we will have > > reached (or be very close to reaching) the end of the 32bit "signed > > integer" range (2.15 billion, or 2^31-1). > > Thanks for the remind

Re: [OSM-dev] Exhaustion of 32bit signed integer range expected this year

2012-04-13 Thread Jukka Rahkonen
The latest Windows build of osm2pgsql is just over two years old now. Perhaps we will reach a new build by the end of this year. -Jukka Rahkonen- Frederik Ramm wrote: > Hi, > > this is just a reminder that our current highest node ID is about > 1.7 billion, and that it grows by about 0.05 bil

Re: [OSM-dev] Exhaustion of 32bit signed integer range expected this year

2012-04-13 Thread David Earl
On 13/04/2012 15:15, Frederik Ramm wrote: This means that it is likely that by the end of 2012, we will have reached (or be very close to reaching) the end of the 32bit "signed integer" range (2.15 billion, or 2^31-1). Thanks for the reminder. I was a bit worried about this having coded a lot

Re: [OSM-dev] Exhaustion of 32bit signed integer range expected this year

2012-04-13 Thread Simon Poole
RSN a large number of sites using OSM data will be reloading their databases, due to a certain well known change :-). It seems as if it would really make sense to make the 64bit ID version of osm2pgsql the default now and communicate that it might be a good idea to switch on the upcoming rel

Re: [OSM-dev] Exhaustion of 32bit signed integer range expected this year

2012-04-13 Thread Frederik Ramm
Hi, On 04/13/2012 04:30 PM, Sven Geggus wrote: Or used for other purposes like in osm2pgsql. Will the upcoming licence change add a delay to this problem? No; if anything, node IDs will be used up faster because if the something is deleted by the bot and later re-created with a new ID then t

Re: [OSM-dev] Exhaustion of 32bit signed integer range expected this year

2012-04-13 Thread Sven Geggus
Frederik Ramm wrote: > Software processing OSM data will need to either use unsigned integers > (which can be problematic in cases where negative values are also > required), or switch to 64bit integers altogether. Or used for other purposes like in osm2pgsql. Will the upcoming licence change

[OSM-dev] Exhaustion of 32bit signed integer range expected this year

2012-04-13 Thread Frederik Ramm
Hi, this is just a reminder that our current highest node ID is about 1.7 billion, and that it grows by about 0.05 billion every month. This means that it is likely that by the end of 2012, we will have reached (or be very close to reaching) the end of the 32bit "signed integer" range (2.