Re: Unreproducible bug in snapshot import code - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Unreproducible bug in snapshot import code
Date
Msg-id 201110281411.p9SEB9F04063@momjian.us
Whole thread Raw
In response to Re: Unreproducible bug in snapshot import code  (Gurjeet Singh <singh.gurjeet@gmail.com>)
Responses Re: Unreproducible bug in snapshot import code  (Gurjeet Singh <singh.gurjeet@gmail.com>)
List 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@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: pg_upgrade if 'postgres' database is dropped
Next
From: Robert Haas
Date:
Subject: Re: pg_upgrade if 'postgres' database is dropped