On 18 September 2014 07:32, Pavan Deolasee wrote:
> 564 /*
> 565 * Set state to complete; see SyncRepWaitForLSN() for discussion
> of
> 566 * the various states.
> 567 */
> 568 thisproc->syncRepState = SYNC_REP_WAIT_COMPLETE;
> 569
> 570 /*
> 571
Pavan,
* Pavan Deolasee (pavan.deola...@gmail.com) wrote:
> On Mon, Sep 22, 2014 at 6:50 PM, Stephen Frost wrote:
> > I agree that it looks like there may be a race condition there- but
> > could you provide the test cases you're working with? What kind of
> > behavior is it that's making it sho
On Mon, Sep 22, 2014 at 6:50 PM, Stephen Frost wrote:
> Pavan,
>
> * Pavan Deolasee (pavan.deola...@gmail.com) wrote:
> > On Thu, Sep 18, 2014 at 12:02 PM, Pavan Deolasee <
> pavan.deola...@gmail.com>
> > wrote:
> > > While running some tests on REL9_2_STABLE branch, I saw an assertion
> > > fail
Pavan,
* Pavan Deolasee (pavan.deola...@gmail.com) wrote:
> On Thu, Sep 18, 2014 at 12:02 PM, Pavan Deolasee
> wrote:
> > While running some tests on REL9_2_STABLE branch, I saw an assertion
> > failure in syncrep.c. The stack trace looks like this:
> >
> Any comments on this? I see it very regul
On Thu, Sep 18, 2014 at 12:02 PM, Pavan Deolasee
wrote:
> Hi All,
>
> While running some tests on REL9_2_STABLE branch, I saw an assertion
> failure in syncrep.c. The stack trace looks like this:
>
>
Any comments on this? I see it very regularly during my pgbench tests.
Thanks,
Pavan
--
Pavan
