Re: lcr v5 - introduction of InvalidCommandId

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: lcr v5 - introduction of InvalidCommandId
Date: 2013-09-09 22:53:36
Message-ID: 29789.1378767216@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> On 2013-09-09 18:43:51 -0400, Tom Lane wrote:
>> Hmm ... shouldn't this patch adjust the error messages in
>> CommandCounterIncrement?

> Hm. You're talking about "cannot have more than 2^32-2 commands in a
> transaction"? If so, the patch and the commit seem to have adjusted that?

Oh! That's what I get for going on memory instead of re-reading the
commit. Sorry, never mind the noise.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Maciek Sakrejda 2013-09-09 23:08:30 Protocol forced to V2 in low-memory conditions?
Previous Message Andres Freund 2013-09-09 22:46:50 Re: lcr v5 - introduction of InvalidCommandId