[COMMITTERS] pgsql: Fix possible dangling pointer dereference in trigger.c.

2017-09-17 Thread Tom Lane
Fix possible dangling pointer dereference in trigger.c. AfterTriggerEndQuery correctly notes that the query_stack could get repalloc'd during a trigger firing, but it nonetheless passes the address of a query_stack entry to afterTriggerInvokeEvents, so that if such a repalloc occurs, afterTriggerI

[COMMITTERS] pgsql: Fix possible dangling pointer dereference in trigger.c.

2017-09-17 Thread Tom Lane
Fix possible dangling pointer dereference in trigger.c. AfterTriggerEndQuery correctly notes that the query_stack could get repalloc'd during a trigger firing, but it nonetheless passes the address of a query_stack entry to afterTriggerInvokeEvents, so that if such a repalloc occurs, afterTriggerI

[COMMITTERS] pgsql: Fix possible dangling pointer dereference in trigger.c.

2017-09-17 Thread Tom Lane
Fix possible dangling pointer dereference in trigger.c. AfterTriggerEndQuery correctly notes that the query_stack could get repalloc'd during a trigger firing, but it nonetheless passes the address of a query_stack entry to afterTriggerInvokeEvents, so that if such a repalloc occurs, afterTriggerI

[COMMITTERS] pgsql: Fix possible dangling pointer dereference in trigger.c.

2017-09-17 Thread Tom Lane
Fix possible dangling pointer dereference in trigger.c. AfterTriggerEndQuery correctly notes that the query_stack could get repalloc'd during a trigger firing, but it nonetheless passes the address of a query_stack entry to afterTriggerInvokeEvents, so that if such a repalloc occurs, afterTriggerI

[COMMITTERS] pgsql: Fix possible dangling pointer dereference in trigger.c.

2017-09-17 Thread Tom Lane
Fix possible dangling pointer dereference in trigger.c. AfterTriggerEndQuery correctly notes that the query_stack could get repalloc'd during a trigger firing, but it nonetheless passes the address of a query_stack entry to afterTriggerInvokeEvents, so that if such a repalloc occurs, afterTriggerI

[COMMITTERS] pgsql: Fix possible dangling pointer dereference in trigger.c.

2017-09-17 Thread Tom Lane
Fix possible dangling pointer dereference in trigger.c. AfterTriggerEndQuery correctly notes that the query_stack could get repalloc'd during a trigger firing, but it nonetheless passes the address of a query_stack entry to afterTriggerInvokeEvents, so that if such a repalloc occurs, afterTriggerI

[COMMITTERS] pgsql: Fix possible dangling pointer dereference in trigger.c.

2017-09-17 Thread Tom Lane
Fix possible dangling pointer dereference in trigger.c. AfterTriggerEndQuery correctly notes that the query_stack could get repalloc'd during a trigger firing, but it nonetheless passes the address of a query_stack entry to afterTriggerInvokeEvents, so that if such a repalloc occurs, afterTriggerI