pgsql: Remove incorrect statement about IPC configuration on OpenBSD

2018-05-25 Thread Magnus Hagander
Remove incorrect statement about IPC configuration on OpenBSD kern.ipc.shm_use_phys is not a sysctl on OpenBSD, and SEMMAP is not a kernel configuration option. These were probably copy pasteos from when the documentation had a single paragraph for *BSD. Author: Daniel Gustafsson

pgsql: Remove incorrect statement about IPC configuration on OpenBSD

2018-05-25 Thread Magnus Hagander
Remove incorrect statement about IPC configuration on OpenBSD kern.ipc.shm_use_phys is not a sysctl on OpenBSD, and SEMMAP is not a kernel configuration option. These were probably copy pasteos from when the documentation had a single paragraph for *BSD. Author: Daniel Gustafsson

pgsql: Remove incorrect statement about IPC configuration on OpenBSD

2018-05-25 Thread Magnus Hagander
Remove incorrect statement about IPC configuration on OpenBSD kern.ipc.shm_use_phys is not a sysctl on OpenBSD, and SEMMAP is not a kernel configuration option. These were probably copy pasteos from when the documentation had a single paragraph for *BSD. Author: Daniel Gustafsson

pgsql: Remove incorrect statement about IPC configuration on OpenBSD

2018-05-25 Thread Magnus Hagander
Remove incorrect statement about IPC configuration on OpenBSD kern.ipc.shm_use_phys is not a sysctl on OpenBSD, and SEMMAP is not a kernel configuration option. These were probably copy pasteos from when the documentation had a single paragraph for *BSD. Author: Daniel Gustafsson

pgsql: Fix misidentification of SQL statement type in plpgsql's exec_st

2018-05-25 Thread Tom Lane
Fix misidentification of SQL statement type in plpgsql's exec_stmt_execsql. To distinguish SQL statements that are INSERT/UPDATE/DELETE from other ones, exec_stmt_execsql looked at the post-rewrite form of the statement rather than the original. This is problematic because it did that only

pgsql: Fix misidentification of SQL statement type in plpgsql's exec_st

2018-05-25 Thread Tom Lane
Fix misidentification of SQL statement type in plpgsql's exec_stmt_execsql. To distinguish SQL statements that are INSERT/UPDATE/DELETE from other ones, exec_stmt_execsql looked at the post-rewrite form of the statement rather than the original. This is problematic because it did that only

pgsql: Fix misidentification of SQL statement type in plpgsql's exec_st

2018-05-25 Thread Tom Lane
Fix misidentification of SQL statement type in plpgsql's exec_stmt_execsql. To distinguish SQL statements that are INSERT/UPDATE/DELETE from other ones, exec_stmt_execsql looked at the post-rewrite form of the statement rather than the original. This is problematic because it did that only

pgsql: Fix misidentification of SQL statement type in plpgsql's exec_st

2018-05-25 Thread Tom Lane
Fix misidentification of SQL statement type in plpgsql's exec_stmt_execsql. To distinguish SQL statements that are INSERT/UPDATE/DELETE from other ones, exec_stmt_execsql looked at the post-rewrite form of the statement rather than the original. This is problematic because it did that only

pgsql: Fix misidentification of SQL statement type in plpgsql's exec_st

2018-05-25 Thread Tom Lane
Fix misidentification of SQL statement type in plpgsql's exec_stmt_execsql. To distinguish SQL statements that are INSERT/UPDATE/DELETE from other ones, exec_stmt_execsql looked at the post-rewrite form of the statement rather than the original. This is problematic because it did that only

pgsql: Fix misidentification of SQL statement type in plpgsql's exec_st

2018-05-25 Thread Tom Lane
Fix misidentification of SQL statement type in plpgsql's exec_stmt_execsql. To distinguish SQL statements that are INSERT/UPDATE/DELETE from other ones, exec_stmt_execsql looked at the post-rewrite form of the statement rather than the original. This is problematic because it did that only