Hi, 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 ;-) Bye Frederik _______________________________________________ dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/dev
