Re: Remove no-op pull_var_clause flag

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alexander Pyhalov <a(dot)pyhalov(at)postgrespro(dot)ru>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Remove no-op pull_var_clause flag
Date: 2026-01-21 18:27:04
Message-ID: 2309281.1769020024@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alexander Pyhalov <a(dot)pyhalov(at)postgrespro(dot)ru> writes:
> While merging PostgreSQL to our (Shardman) fork, I've noticed that it
> uses the same pull_var_clause() flag as we do (coming from
> https://www.postgresql.org/message-id/CAFjFpRc8ZoDm0%2Bzhx%2BMckwGyEqkOzWcpVqbvjaxwdGarZSNrmA%40mail.gmail.com)
> I was a bit surprised, the patch hasn't landed to master. But flag
> somehow slipped in (but only as no-op). The attached patch removes
> useless flag.

Right, done.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nikolay Shaplov 2026-01-21 18:44:29 Re: [PATCH] ternary reloption type
Previous Message Álvaro Herrera 2026-01-21 18:01:57 Re: bt_index_parent_check and concurrently build indexes