Zdenek Kotala <[EMAIL PROTECTED]> writes: > Tom Lane napsal(a): >> On the other hand, I remain unconvinced that this problem is severe >> enough to justify much backporting work. AFAIK we've only seen one >> occurence of a problem to date.
> I know about two occurrence. One was reported on -bug > (http://archives.postgresql.org/pgsql-bugs/2008-04/msg00206.php) > and second was reported from our customer. I'm still not impressed. Bear in mind that the patch you are so eager to backport has received *zero* field testing, which means there's a non-negligible risk that there's something wrong with it. Add on the non-negligible risk of messing up something associated with back-porting the earlier patch, and consider that back-branch minor releases go out with no field testing to speak of (there's the build farm but that's about it). You have to seriously question whether the risk is worth what is surely an extremely marginal stability improvement. On the whole I think we've done enough here. regards, tom lane -- Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-patches
