Re: [SQL/PGQ] Native executor for Graph query - Mailing list pgsql-hackers

From Henri GASC
Subject Re: [SQL/PGQ] Native executor for Graph query
Date
Msg-id CAJyuutjcJhwH9Xz9=8jK-Ch=38AiAzJ6XG-_QooiEUaT0M5Shw@mail.gmail.com
Whole thread
In response to Re: [SQL/PGQ] Native executor for Graph query  (Henri GASC <henri.gasc@airbus.com>)
Responses Re: [SQL/PGQ] Native executor for Graph query
List 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 everyone,
Here is an updated version of the patches that should (hopefully)
pass world tests.
Sorry for sending all the patches again; I'm unsure if cfbot will be
able to pick up the previous version if there is no "v2" for a file (and
all hashes changed).

 Henri Gasc

On Tue, Sep 15, 2026 at 10:44 AM Henri GASC <henri.gasc@airbus.com> wrote:
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@gmail.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

pgsql-hackers by date:

Previous
From: Diego
Date:
Subject: Re: [PATCH] libpq: Add PQpassfileLookup()
Next
From: Heikki Linnakangas
Date:
Subject: Re: pgsql: Revert online data checksum transitions