Nikhil Sontakke ebbca2dd77 Fix leaks with functions in DML
If plpgsql functions are used in DML queries then we were leaking 8KB
for every invocation of that function. This can quickly add up.

The issue was that the "CurTransactionContext" was not getting cleaned
up after every invocation. The reason was that we were inadvertantly
allocating a temporary list in that context. Postgres then thought that
this CurTransactionContext needs to be re-used further and kept it
around. We now use a proper memory context to avoid this.

Fixes #7053
2024-07-02 13:32:06 +05:30
..
2022-08-23 19:40:51 +03:00
2024-05-26 13:52:59 -03:00
2023-12-05 16:15:24 +01:00
2023-10-04 14:49:05 +05:30
2020-09-28 12:15:42 +02:00
2023-03-07 20:45:12 +05:30
2024-05-14 17:19:20 +02:00
2021-06-01 20:21:06 +02:00
2023-09-28 08:14:30 +02:00
2024-05-14 17:19:20 +02:00
2024-05-14 17:19:20 +02:00
2022-08-31 14:14:34 +03:00
2023-10-18 11:45:06 -03:00
2024-02-08 16:02:19 +01:00
2023-05-27 10:29:11 +05:30
2021-06-01 20:21:06 +02:00
2019-01-13 23:30:22 +01:00
2023-12-18 10:53:27 +01:00
2023-11-16 16:35:38 +01:00
2021-06-01 20:21:06 +02:00
2024-04-10 15:13:29 +02:00
2024-05-14 17:19:20 +02:00
2023-11-16 16:35:38 +01:00