Re: pgsql: Allow for plugin control over path generation strategies.

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Aleksander Alekseev <aleksander(at)tigerdata(dot)com>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org, Michael Paquier <michael(at)paquier(dot)xyz>
Subject: Re: pgsql: Allow for plugin control over path generation strategies.
Date: 2026-01-29 14:11:55
Message-ID: CA+TgmoZ8XW5y1ddKF5OQbr1y3=OEL3jo38Ky5cKr2V7ELP7XMw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Thu, Jan 29, 2026 at 8:53 AM Aleksander Alekseev
<aleksander(at)tigerdata(dot)com> wrote:
> ... you could just rewrite the `if` condition in cost_material():
>
> ```
> if (path->parent != NULL && /* <--- is false */
> path->parallel_workers == 0 &&
> ```

In the interest of keeping the discussion unified, can we move this
part of the conversation over to the pg_plan_advice thread? Lukas
Fittl has also posted about this topic over there.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Álvaro Herrera 2026-01-29 17:44:32 pgsql: Replace literal 0 with InvalidXLogRecPtr for XLogRecPtr assignme
Previous Message Aleksander Alekseev 2026-01-29 13:53:29 Re: pgsql: Allow for plugin control over path generation strategies.