On Sep 18, 2025, at 09:33, Amit Langote <amitlangote09@gmail.com> wrote:On Thu, Sep 18, 2025 at 7:32 AM David Rowley <dgrowleyml@gmail.com> wrote:On Thu, 18 Sept 2025 at 09:43, David Rowley <dgrowleyml@gmail.com> wrote:The first bad commit is:commit bb3ec16e14ded1d23a46d3c7e623a965164fa124Author: Amit Langote <amitlan@postgresql.org>Date: Thu Jan 30 11:57:32 2025 +0900 Move PartitionPruneInfo out of plan nodes into PlannedStmtI think the attached is the correct fix. I also wonder if it's worthan isolation test to exercise this code.Thanks for the patch, David, and for the report, Fei. I indeed forgotto update EvalPlanQualStart() in that commit.I agree about adding an isolation test, which I have done in theattached updated patch.
On Thu, 18 Sept 2025 at 09:43, David Rowley <dgrowleyml@gmail.com> wrote:The first bad commit is:commit bb3ec16e14ded1d23a46d3c7e623a965164fa124Author: Amit Langote <amitlan@postgresql.org>Date: Thu Jan 30 11:57:32 2025 +0900 Move PartitionPruneInfo out of plan nodes into PlannedStmtI think the attached is the correct fix. I also wonder if it's worthan isolation test to exercise this code.
The first bad commit is:commit bb3ec16e14ded1d23a46d3c7e623a965164fa124Author: Amit Langote <amitlan@postgresql.org>Date: Thu Jan 30 11:57:32 2025 +0900 Move PartitionPruneInfo out of plan nodes into PlannedStmt
pgsql-bugs by date:
Соглашаюсь с условиями обработки персональных данных