On 27/05/10 22:56, Robert Haas wrote:
On Thu, May 27, 2010 at 3:52 PM, Kevin Grittner
<kevin.gritt...@wicourts.gov> wrote:
Robert Haas<robertmh...@gmail.com> wrote:
On Thu, May 27, 2010 at 3:15 PM, Kevin Grittner
(a) The tuples were written within the same transaction which
created or truncated the table.
In case (a), you mess up visibility with respect to other
command-IDs within the transaction.
Surely that problem is surmountable?
I proposed an idea at PGCon, but I believe Tom and Heikki thought it
was far too grotty to consider.
No, I think it's surmountable too. We discussed hacks to teach the MVCC
checks that all frozen tuples on a table that was created in the same
transaction (i.e. the same cases where we skip WAL logging) were
actually created by the running transaction, and check commandid
accordingly.
Or detect simple DML commands where we know that the command doesn't
read the table. COPY would usually fall into that category, though
non-immutable input functions make that a bit iffy.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
