This is a discussion on pgcrypto volatility and strictness changes within the Pgsql Patches forums, part of the PostgreSQL category; --> This patch updates the DDL for contrib/pgcrypto to create all functions as STRICT, and all functions except gen_salt() as ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| This patch updates the DDL for contrib/pgcrypto to create all functions as STRICT, and all functions except gen_salt() as IMMUTABLE. gen_salt() is VOLATILE. Although the functions are now STRICT, I left their PG_ARGISNULL() checks in place as a protective measure for users who install the new code but use old (non-STRICT) catalog entries (e.g., restored from a dump). Per recent discussion in pgsql-hackers. -- Michael Fuhr http://www.fuhr.org/~mfuhr/ ---------------------------(end of broadcast)--------------------------- TIP 8: explain analyze is your friend |
| |||
| Michael Fuhr wrote: > This patch updates the DDL for contrib/pgcrypto to create all > functions as STRICT, and all functions except gen_salt() as IMMUTABLE. > gen_salt() is VOLATILE. Barring any objections, I'll apply this tomorrow. -Neil ---------------------------(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 |
| ||||
| Michael Fuhr wrote: > This patch updates the DDL for contrib/pgcrypto to create all > functions as STRICT, and all functions except gen_salt() as IMMUTABLE. > gen_salt() is VOLATILE. Applied, thanks. -Neil ---------------------------(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 |