pgsql: SPI_cursor_open failed to enforce that only read-only queries - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: SPI_cursor_open failed to enforce that only read-only queries
Date
Msg-id 20070317031538.9A9AA9FB609@postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
SPI_cursor_open failed to enforce that only read-only queries could be
executed in read_only mode.  This could lead to various relatively-subtle
failures, such as an allegedly stable function returning non-stable results.
Bug goes all the way back to the introduction of read-only mode in 8.0.
Per report from Gaetano Mendola.

Modified Files:
--------------
    pgsql/src/backend/executor:
        spi.c (r1.172 -> r1.173)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/spi.c.diff?r1=1.172&r2=1.173)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Ooops, got only one of the two ArrayExpr variants correct in
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: SPI_cursor_open failed to enforce that only read-only queries