BUG #13038: Unobvious snapshotting behavior on altered tables

From: bashtanov(at)imap(dot)cc
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #13038: Unobvious snapshotting behavior on altered tables
Date: 2015-04-13 09:25:22
Message-ID: 20150413092522.26382.97939@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 13038
Logged by: Alexey Bashtanov
Email address: bashtanov(at)imap(dot)cc
PostgreSQL version: 9.4.1
Operating system: Linux CentOS 6.5 x64
Description:

Hello!

On truncate statement docs page there is a nice pink warning
http://www.postgresql.org/docs/9.4/static/sql-truncate.html#AEN85039

This warning also affects some table-rewriting ALTER TABLE statement, see
http://johtopg.blogspot.com.br/2014/11/postgresql-gotcha-of-week-week-45_6.html

The problem is
1) This is undocumented. Please document which commands can lead to this
behavior.
2) Not all the table-rewriting statements can show an empty snapshot. ALTER
TABLE ADD COLUMN, ALTER TABLE SET WITH/WITHOUT OIDS and TRUNCATE surely can.
ALTER TABLE SET TABLESPACE, CLUSTER, VACUUM FULL probably cannot. What is
the difference between the commands in the first list and in the second one?
Maybe this annoying behavior can be fixed for all DDL statements?

Best Regards
Alexey Bashtanov

Browse pgsql-bugs by date

  From Date Subject
Next Message Sandeep Thakkar 2015-04-13 12:10:05 Re: BUG #13013: Cannot install PostgreSQL
Previous Message alemagox 2015-04-12 11:56:30 BUG #13034: Inconsistent attrelid field in pg_attribute table after adding columns to table.