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

From Fujii Masao
Subject Re: Unreproducible bug in snapshot import code
Date
Msg-id CAHGQGwHqHwxc9Q5ihTVvjLysgOQ8SYT1Z_=y68bJdJcEdk0KRA@mail.gmail.com
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
On Tue, Oct 25, 2011 at 2:41 AM, Gurjeet Singh <singh.gurjeet@gmail.com> wrote:
> On Mon, Oct 24, 2011 at 1:08 PM, Alvaro Herrera <alvherre@commandprompt.com>
> wrote:
>>
>> Excerpts from Gurjeet Singh's message of lun oct 24 13:55:44 -0300 2011:
>>
>> >     Starting from line 89 of terminal1.txt we see this snippet:
>> >
>> > postgres=# rollback;
>> > ROLLBACK
>> > postgres=# begin TRANSACTION ;
>> > BEGIN
>> > postgres=# set transaction snapshot '000002C8-1';
>> > ERROR:  SET TRANSACTION SNAPSHOT must be called before any query
>> > postgres=# rollback;
>> > ROLLBACK
>> >
>> >
>> >     As you can see the SET TRANSACTION SNAPSHOT was the first statement
>> > in
>> > that transaction, and yet the ERROR message says that it is not.
>>
>> Maybe the tab-completion feature issued a query before the set
>> transaction command.
>
> 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.

Regards,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center


pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Online base backup from the hot-standby
Next
From: Wolfgang Wilhelm
Date:
Subject: Re: So, is COUNT(*) fast now?