That was probably the manifestation of the bug #801217, and was fixed in 5.3-gis with the patch to it.
That was probably the manifestation of the bug #801217, and was fixed in 5.3-gis with the patch to it.