Re: [SQL/PGQ] Native executor for Graph query

From: Henri GASC <henri(dot)gasc(at)airbus(dot)com>
To: assam258(at)gmail(dot)com
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [SQL/PGQ] Native executor for Graph query
Date: 2026-09-15 08:44:03
Message-ID: CAJyuutgJzqVJEsKGFaQpPbp812TcAx69wpgSuHjn6vVDmEdBVw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

*Classification: * Privacy: Basic Personal Data; Export Control:
Not Technical; National Security: Not National Security; Company
Classification: Not Applicable; Business or Private Data: Business data

Hello hackers,
Here is the updated patch, now in different files. It should hopefully
be clearer to understand and easier to review.
This series only implements the WALK syntax.

Best regards,
Henri GASC

On Tue, Sep 8, 2026 at 1:18 PM Henson Choi <assam258(at)gmail(dot)com> wrote:

> Hi Henri,
>
> Glad it was useful.
>
> > I think I will either reimplement only what I need, or build upon
> > the parent (like I did before).
>
> I would build upon the parent. The open items behind the revert are
> about catalogs and dependencies, not about execution, so the shape
> your node sits on should come back much as it was. Reimplementing a
> subset means answering the catalog questions that are exactly the ones
> still open, and your executor patch would then have to carry them.
>
> Reverting the revert gives you a commit, and that commit is your
> development base:
>
> git checkout -b pgq-restore master
> git revert --no-commit b1f106c80
> git commit -m "Restore SQL/PGQ as a cfbot base; not for review"
>
> Then build your work on top of it, and post both commits in order:
>
> git format-patch -o . master..<your branch>
>
> That gives 0001 for the base and 0002 for your work, and cfbot has
> something to apply.
>
> One thing to watch: the base is a large patch touching many files, so
> with your own on top the mail may be big enough to be held for
> moderation.
>
> Once Ashutosh posts the patch series again, use that as the base
> instead and drop 0001.
>
> Best regards,
> Henson
>
The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised.
If you are not the intended recipient, please notify Airbus immediately and delete this e-mail.
Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately.
All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.

Attachment Content-Type Size
0004-Split-graph-queries-into-GraphScan-Append-SeqScan-et.patch application/octet-stream 119.1 KB
0003-Parse-grammar-for-VLE.patch application/octet-stream 15.2 KB
0002-Add-GUC-enable_native-and-max_depth.patch application/octet-stream 15.5 KB
0005-Implement-the-executor.patch application/octet-stream 80.1 KB
0001-Restore-SQL-PGQ-as-a-cfbot-base-not-for-review.patch application/octet-stream 743.9 KB
0008-Remove-dead-code-and-simplify-GraphScan.patch application/octet-stream 30.1 KB
0007-Add-rows-estimate-to-planner-and-use-IndexScan-if-po.patch application/octet-stream 47.5 KB
0006-Correct-bug-const-with-label-disjunction-and-show-pl.patch application/octet-stream 15.4 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexandre Felipe 2026-09-15 08:47:17 Re: FIX: BUG #19687: ALTER SEQUENCE missing lock
Previous Message Bharath Rupireddy 2026-09-15 08:38:00 Re: REPACK (CONCURRENTLY) backend waits indefinitely when decoding worker fails to start