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

Re: Unreproducible bug in snapshot import code

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Unreproducible bug in snapshot import code
Date: 2011-10-28 14:11:09
Message-ID: 201110281411.p9SEB9F04063@momjian.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Gurjeet Singh wrote:
> > > I have tried reproducing the bug starting from 1 and 2 transactions
> > before
> > > the one shown in snippet, and I used tab-completion to get the same
> > > screen-output as termonal1.txt and yet it's not reproducible.
> >
> > I could reproduce it when I typed TAB just after typing "set" in "set
> > transaction snapshot".
> > As Tom and Alvaro pointed out, the tab-completion issues a query and which
> > prevents the "set transaction snapshot" command.
> >
> 
> Great! That settles it then. Reproducible, but not a bug.

Yes, it is only tabs that query the database for completion that cause
this.  Should this be documented somehow?  (No idea how.)

-- 
  Bruce Momjian  <bruce(at)momjian(dot)us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +

In response to

Responses

pgsql-hackers by date

Next:From: Robert HaasDate: 2011-10-28 14:14:49
Subject: Re: pg_upgrade if 'postgres' database is dropped
Previous:From: Bruce MomjianDate: 2011-10-28 14:09:29
Subject: Re: pg_upgrade if 'postgres' database is dropped

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