Re: Limit GRAPH_TABLE path combinations to prevent memory exhaustion

From: Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: SATYANARAYANA NARLAPURAM <satyanarlapuram(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, peter(at)eisentraut(dot)org
Subject: Re: Limit GRAPH_TABLE path combinations to prevent memory exhaustion
Date: 2026-08-13 12:01:50
Message-ID: CAExHW5tC0UcpWqGFiA7tfnQuNXL8swiCOpJu_s+hv-ESVspD=Q@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Nathan,

On Thu, Aug 13, 2026 at 1:49 AM Nathan Bossart <nathandbossart(at)gmail(dot)com> wrote:
>
> [RMT hat]
>
> I've added this as an open item for v19, although I'm not sure whether this
> can/should be addressed as such. Peter, WDYT?

Thanks for the reminder and sorry for missing it. I think we should at
least add the CFI as the last patch does. Attaching here after
cleaning up the rest of the changes.

--
Best Wishes,
Ashutosh Bapat

Attachment Content-Type Size
v20260813-0001-Make-generate_queries_for_path_pattern_rec.patch text/x-patch 1.5 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2026-08-13 12:34:02 Re: Fix unsafe coding in ResourceOwnerReleaseAll()
Previous Message Amit Kapila 2026-08-13 11:38:47 Re: Logical replication row filter loses unchanged toasted columns