MIME-Version: 1.0
Subject: BUG #13541: There is a visibility issue when run some DDL and Query.
 The time window is very shot
To: pgsql-bugs@postgresql.org
From: beijing_pg@163.com
Date: Fri, 07 Aug 2015 12:16:43 +0000
Message-ID: <20150807121643.32633.60549@wrigleys.postgresql.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-bugs-owner@postgresql.org

The following bug has been logged on the website:

Bug reference:      13541
Logged by:          zhangjinyu
Email address:      beijing_pg@163.com
PostgreSQL version: 9.2.13
Operating system:   suse
Description:        

There is a visibility issue when run some DDL and Query. The time window is
very shot. Postgres is to hold relation lock after getsnapshot. Before a
query holds relation lock, if another session run a DDL(alter table alter
column set datatype), Once this DDL committed, select query will return zero
row, because the DDL(alter table alter column set datatype) will rewrite all
tuples with new transaction id.

We can use the following test case to repro the issue.  we add sleep(40)
after GetTransactionSnapshot (in function exec_simple_query) to enlarge the
time window.
Step1: session1: select * from t; (return 3 row)
                 set enable_sleep30_after_getsnapshot=on;
select * from t;
Step2: session2: begin transaction;
alter table t alter c1 set type char(10); 
commit;

we can see session1 "select * from t" return 0 row.
======================================
session1:
select * from t;  (it returns 3 rows)  
set enable_sleep30_after_getsnapshot=on;
select * from t;  (it returns 0 row)    

session2:
start transaction;
alter table t alter c1 set type char(10); 
end;


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs