On Sat, Dec 11, 2010 at 11:28 PM, Simon Riggs <si...@2ndquadrant.com> wrote: >> This problem happens because ResolveRecoveryConflictWithVirtualXIDs >> resets PS display for each read-only transactions that recovery >> waits for. Why do we need to reset that each time even though >> the conflict has not been resolved yet? The attached patch >> suppresses such a needless reset. Comments? > > The reset occurs at most each 500ms, so not much problem there. > > But if it annoys you, it seems OK to change it. Don't see a reason to > backpatch though?
I think that It's worth backpatch to prevent users who observe the occurrence of the query conflicts carefully for testing 9.0 from getting confusing. Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
