On 2017-03-24 13:50:54 -0400, Robert Haas wrote:
> On Fri, Mar 24, 2017 at 12:27 PM, Robert Haas wrote:
> > On Fri, Mar 24, 2017 at 12:14 PM, Robert Haas wrote:
> >> On Fri, Mar 24, 2017 at 10:23 AM, Simon Riggs
> >> wrote:
> >>> Avoid SnapshotResetXmin() during AtEOXact_Snapshot()
> >>>
> >>>
On 24 March 2017 at 16:14, Robert Haas wrote:
> I suspect that is the fault of this patch. Please fix or revert.
Will revert then fix.
--
Simon Riggshttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-hackers m
On Fri, Mar 24, 2017 at 12:27 PM, Robert Haas wrote:
> On Fri, Mar 24, 2017 at 12:14 PM, Robert Haas wrote:
>> On Fri, Mar 24, 2017 at 10:23 AM, Simon Riggs wrote:
>>> Avoid SnapshotResetXmin() during AtEOXact_Snapshot()
>>>
>>> For normal commits and aborts we already reset PgXact->xmin
>>> Avo
On Fri, Mar 24, 2017 at 12:14 PM, Robert Haas wrote:
> On Fri, Mar 24, 2017 at 10:23 AM, Simon Riggs wrote:
>> Avoid SnapshotResetXmin() during AtEOXact_Snapshot()
>>
>> For normal commits and aborts we already reset PgXact->xmin
>> Avoiding touching highly contented shmem improves concurrent
>>
On Fri, Mar 24, 2017 at 10:23 AM, Simon Riggs wrote:
> Avoid SnapshotResetXmin() during AtEOXact_Snapshot()
>
> For normal commits and aborts we already reset PgXact->xmin
> Avoiding touching highly contented shmem improves concurrent
> performance.
>
> Simon Riggs
I'm getting occasional crashes
