Re: Do we need a TODO? (was Re: Concurrently updating an updatable view)

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Richard Huxton <dev(at)archonet(dot)com>
Cc: "Florian G(dot) Pflug" <fgp(at)phlo(dot)org>, Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp>, Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Do we need a TODO? (was Re: Concurrently updating an updatable view)
Date: 2007-05-28 23:56:09
Message-ID: 200705282356.l4SNu9R17687@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Added to TODO:

* Fix self-referential UPDATEs seeing inconsistent row versions in
read-committed mode

http://archives.postgresql.org/pgsql-hackers/2007-05/msg00507.php

---------------------------------------------------------------------------

Richard Huxton wrote:
> Florian G. Pflug wrote:
> >
> > Is there consensus what the correct behaviour should be for
> > self-referential updates in read-committed mode? Does the SQL Spec
> > have anything to say about this?
>
> This seems to have gone all quiet. Do we need a TODO to keep a note of
> it? Just "correct behaviour for self-referential updates"
>
> Hiroshi originally noted the problem in one of his views here:
> http://archives.postgresql.org/pgsql-hackers/2007-05/msg00507.php
>
> --
> Richard Huxton
> Archonet Ltd
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2007-05-29 00:18:55 TOAST usage setting
Previous Message Jim Nasby 2007-05-28 23:49:08 Re: Reviewing temp_tablespaces GUC patch