Jeff Davis da32a99df1 Limit memory usage of pg_walinspect functions. ... GetWALRecordsInfo() and pg_get_wal_fpi_info() can leak memory across WAL record iterations. Fix this by using a temporary memory context that's reset for each WAL record iteraion. Also use a temporary context for loops in GetXLogSummaryStats(). The number of iterations is a small constant, so the previous behavior was not a leak, but fix for clarity (but no need to backport). Backport GetWALRecordsInfo() change to version 15. pg_get_wal_fpi_info() didn't exist in version 15. Reported-by: Peter Geoghegan Author: Bharath Rupireddy Discussion: https://www.postgresql.org/message-id/CAH2-WznLEJjn7ghmKOABOEZYuJvkTk%3DGKU3m0%2B-XBAH%2BerPiJQ%40mail.gmail.com Backpatch-through: 15		2023-02-20 11:29:31 -08:00
..
expected
sql
.gitignore
Makefile
pg_walinspect--1.0.sql	Use float8 datatype for percentiles in pg_walinspect stat functions	2022-09-12 09:38:07 +02:00
pg_walinspect.c	Limit memory usage of pg_walinspect functions.	2023-02-20 11:29:31 -08:00
pg_walinspect.control
walinspect.conf