Skip site navigation (1) Skip section navigation (2)

Re: [COMMITTERS] pgsql: Reset 'ps' display just once when resolving VXID conflicts.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [COMMITTERS] pgsql: Reset 'ps' display just once when resolving VXID conflicts.
Date: 2010-12-17 16:20:27
Message-ID: 752.1292602827@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Fri, Dec 17, 2010 at 9:52 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I imagine the reason for the original coding was to avoid a useless
>> gettimeofday kernel call in the common case that there are no
>> conflicting xacts to wait for. Could we restore that behavior?

> Something like the attached?

I would just add the return-at-the-top.  Changing the loop logic is
not necessary --- the loop test is cheap.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Pavel StehuleDate: 2010-12-17 16:21:57
Subject: Re: proposal: FOREACH-IN-ARRAY (probably for 9.2?)
Previous:From: Tom LaneDate: 2010-12-17 16:18:35
Subject: Re: bug in SignalSomeChildren

pgsql-committers by date

Next:From: Robert HaasDate: 2010-12-17 16:33:02
Subject: pgsql: Try to save a kernel call inResolveRecoveryConflictWithVirtualX
Previous:From: Robert HaasDate: 2010-12-17 16:13:51
Subject: Re: [COMMITTERS] pgsql: Reset 'ps' display just once when resolving VXID conflicts.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group