Postgres Pro
Downloads
Home   >   mailing lists

pgsql: Update based on user comments: < in PL/PgSQL is to use - Mailing list pgsql-committers

From momjian@svr1.postgresql.org (Bruce Momjian)
Subject pgsql: Update based on user comments: < in PL/PgSQL is to use
Date
Msg-id 20050826193243.D36F5D7978@svr1.postgresql.org
Whole thread Raw
List pgsql-committers
Tree view 
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)

pgsql-committers by date:

Previous
From: momjian@svr1.postgresql.org (Bruce Momjian)
Date:
Subject: pgsql: Update constraint_exclusion items: < inheritance, and allow it
Next
From: momjian@svr1.postgresql.org (Bruce Momjian)
Date:
Subject: pgsql: Add description and item: > > Currently, while \e saves a