On Fri, Aug 30, 2013 at 12:59 AM, Tom Lane wrote:
> Andres Freund writes:
>> But I think that actually coordinating a consistent visibility order
>> between commit, wal insertion and the procarray would have bigger
>> scalability impact than the second record. I might be missing some
>> clever tr
On Fri, Aug 30, 2013 at 12:33 AM, Andres Freund wrote:
> FWIW, WAL is still the major bottleneck for INSERT heavy workloads. The
> per CPU overhead actually minimally increased (at least in my tests), it
> just scales noticeably better than before.
Interesting. Do you have any insight what is beh
Andres Freund writes:
> But I think that actually coordinating a consistent visibility order
> between commit, wal insertion and the procarray would have bigger
> scalability impact than the second record. I might be missing some
> clever tricks here though.
Yeah. ISTM the only way to really gua
On 2013-08-30 00:22:49 +0300, Ants Aasma wrote:
> Hi, thanks for your reply.
>
> On Thu, Aug 29, 2013 at 6:40 PM, Robert Haas wrote:
> > I think approach #2 is dead on arrival, at least as a default policy.
> > It essentially amounts to requiring two commit records per transaction
> > rather than
Hi, thanks for your reply.
On Thu, Aug 29, 2013 at 6:40 PM, Robert Haas wrote:
> I think approach #2 is dead on arrival, at least as a default policy.
> It essentially amounts to requiring two commit records per transaction
> rather than one, and I think that has no chance of being acceptable.
>
On Wed, Aug 28, 2013 at 10:58 AM, Ants Aasma wrote:
> I currently see the following courses of action:
>
> 1. Do nothing about the inconsistency, use a transient global counter
> for master commit order and commit record LSN for slaves.
>Pro: doesn't change any semantics
>Con: we are not m
I'm currently implementing commit sequence number (CSN) based
snapshots and I hit a design decision that I would like to resolve
before I have too much code to rewrite.
The issue is commit visibility ordering on slaves. As a couple of
threads on hackers have already noted, currently commit order o
