On 07/10/09 10:56, Frederik Ramm wrote: > Tom Hughes wrote: >> Essentially if any transaction that started before the end of the >> period the diff covers is still running when the the diff is created >> then changes in that transaction may be missed out as they won't have >> been committed yet. > > Could Postgres be persuaded to abort any transaction that runs longer > than "n" minutes (e.g. 30), and the we run the hourlies at hh:31 or so? > That would probably be a slight inconvenience to those who happen to > start 35-minute transactions but they should just learn to do their bulk > imports properly ;-)
Um... Are you being serious? You want us to arbitrarily abort otherwise valid changeset uploads? Why? We've already solved the problem with the transactional diffs... Tom -- Tom Hughes ([email protected]) http://www.compton.nu/ _______________________________________________ dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/dev
