time dates - Search results
Mailing lists >> pgsql-hackers >> Thread
2025-05-29 17:59:45 | Re: Fixing memory leaks in postgres_fdw (Tom Lane)
Date: Thu, 29 May 2025 10:47:54 -0400 Subject: [PATCH v6 2/4] Reap the benefits of not having to avoid leaking PGresults. Remove a bunch of PG_TRY constructs, de-volatilize related variables, remove
Mailing lists >> pgsql-hackers >> Thread
2025-05-28 23:56:32 | Re: Fixing memory leaks in postgres_fdw (Tom Lane)
time aren't
high, but losing track of an open connection seems pretty bad.
regards, tom lane
From 1d32ebcbae932c3d473fe90094e3c4c90723c0eb Mon Sep 17 00:00:00 2001
From: Tom Lane
Mailing lists >> pgsql-hackers >> Thread
2025-05-26 22:36:14 | Re: Fixing memory leaks in postgres_fdw (Tom Lane)
Date: Mon, 26 May 2025 14:10:23 -0400 Subject: [PATCH v4 2/5] Reap the benefits of not having to avoid leaking PGresults. Remove a bunch of PG_TRY constructs, de-volatilize related variables, remove
Mailing lists >> pgsql-hackers >> Thread
2025-05-25 22:53:17 | Re: Fixing memory leaks in postgres_fdw (Tom Lane)
Date: Sun, 25 May 2025 15:16:23 -0400 Subject: [PATCH v2 1/2] Fix memory leakage in postgres_fdw's DirectModify code path. postgres_fdw tries to use PG_TRY blocks to ensure that