pgsql: SPI_cursor_open failed to enforce that only read-only queries

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: SPI_cursor_open failed to enforce that only read-only queries
Date: 2007-03-17 03:16:04
Message-ID: 20070317031604.07D679FB609@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

Tags:
----
REL8_0_STABLE

Modified Files:
--------------
pgsql/src/backend/executor:
spi.c (r1.133.4.1 -> r1.133.4.2)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/spi.c.diff?r1=1.133.4.1&r2=1.133.4.2)

Browse pgsql-committers by date

  From Date Subject
Next Message User Eggyknap 2007-03-17 03:45:23 pgsnmpd - pgsnmpd: New Directory
Previous Message Tom Lane 2007-03-17 03:15:55 pgsql: SPI_cursor_open failed to enforce that only read-only queries