pgsql: Update based on user comments: < in PL/PgSQL is to use

From: momjian(at)svr1(dot)postgresql(dot)org (Bruce Momjian)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Update based on user comments: < in PL/PgSQL is to use
Date: 2005-08-26 19:32:43
Message-ID: 20050826193243.D36F5D7978@svr1.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Update based on user comments:

< in PL/PgSQL is to use EXECUTE.
> in PL/PgSQL is to use EXECUTE. One complexity is that a function
> might itself drop and recreate dependent tables, causing it to
> invalidate its own query plan.

Modified Files:
--------------
pgsql/doc:
TODO (r1.1638 -> r1.1639)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1638&r2=1.1639)
pgsql/doc/src/FAQ:
TODO.html (r1.145 -> r1.146)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.145&r2=1.146)

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2005-08-26 19:41:19 pgsql: Add description and item: > > Currently, while \e saves a
Previous Message Bruce Momjian 2005-08-26 19:10:48 pgsql: Update constraint_exclusion items: < inheritance, and allow it