| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | zhangjinyu <beijing_pg(at)163(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org, pgsql-docs(at)postgresql(dot)org |
| Subject: | Re: [BUGS] Re: BUG #13541: There is a visibility issue when run some DDL and Query. The time window is very shot |
| Date: | 2015-08-14 14:23:10 |
| Message-ID: | 4140.1439562190@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-docs |
zhangjinyu <beijing_pg(at)163(dot)com> writes:
> The DDL query(alter ...set data type ) rewrites all tuples with new
> transaction xid, so if the transaction isolation level is repeatable read,
> that will cause wrong result.
Yes. This is unlikely to change, but we ought to document it.
I see that we have documentation warning about this sort of effect in the
TRUNCATE reference page, but not in ALTER TABLE's. Rather than
copy-and-paste that, ISTM it'd be better to move the warning to somewhere
in mvcc.sgml.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | herbertsilver | 2015-08-14 16:39:19 | BUG #13572: Foreign Key Corruption |
| Previous Message | Tom Lane | 2015-08-14 13:58:08 | Re: BUG #13571: sql-only extension segfaults backend during creation |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-08-14 14:32:41 | Error in ALTER TABLE documentation |
| Previous Message | zhangjinyu | 2015-08-14 11:45:34 | Re: BUG #13541: There is a visibility issue when run some DDL and Query. The time window is very shot |