Guidance Needed for Testing PostgreSQL Patch (CF-5044)

Hi, I recently installed and tested the CF-5044 patch using the query provided on the PostgreSQL community page but could not confirm its functionality. I followed the standard process: 1. Applied the patch using git. 2. Rebuilt PostgreSQL from source (./configure, make, make install).

Guidance Needed for Testing PostgreSQL Patch (CF-5044)

Hi pg_hackers, I hope you are doing well. I am working on reviewing PostgreSQL community tickets and started with the patch cf/5044. This patch is in the branch cf/5044, and I pulled the code to test it. Here’s what I have done so far: * Pulled the code from the branch cf/5044. * Compiled th

RE: Replace IN VALUES with ANY in WHERE clauses during optimization

Hi Ivan, I tested the patch using the input provided in commands.sql and observed improvements in both planning and execution time. These optimizations are especially noticeable when working with a mulitple tables. Even when querying just a single table, there is a small improvement in planning

Re: Replace IN VALUES with ANY in WHERE clauses during optimization

The following review has been posted through the commitfest application: make installcheck-world: tested, failed Implements feature: tested, failed Spec compliant: tested, failed Documentation:tested, failed Hi Ivan Kush I tested the patch with `commands.sql` and obser

Re: New "raw" COPY format

The following review has been posted through the commitfest application: make installcheck-world: tested, failed Implements feature: tested, failed Spec compliant: tested, failed Documentation:tested, failed Hi Joel, After testing the patch, I observed that for single-

Re: [PoC] Reducing planning time when tables have many partitions

The following review has been posted through the commitfest application: make installcheck-world: tested, failed Implements feature: tested, failed Spec compliant: tested, failed Documentation:tested, failed Hi Yuya, Tested this patch and noted that this patch signific

Re: [PoC] Add CANONICAL option to xmlserialize

The following review has been posted through the commitfest application: make installcheck-world: tested, failed Implements feature: tested, failed Spec compliant: tested, failed Documentation:tested, failed Hi Jim, I tested the function with dynamically generated XML

Re: in BeginCopyTo make materialized view using COPY TO instead of COPY (query).

The following review has been posted through the commitfest application: make installcheck-world: not tested Implements feature: not tested Spec compliant: not tested Documentation:not tested Hi, Tested the latest patch that allows direct `COPY` operations on Materiali

Re: pg_dump, pg_dumpall, pg_restore: Add --no-policies option

The following review has been posted through the commitfest application: make installcheck-world: not tested Implements feature: not tested Spec compliant: not tested Documentation:not tested Hi, Tested this patch with `--no-policies` option works as expected by ensuri

Re: Add XMLNamespaces to XMLElement

The following review has been posted through the commitfest application: make installcheck-world: not tested Implements feature: not tested Spec compliant: not tested Documentation:not tested Hi Pavel, I have tested this patch, and it proves to be highly useful when h

Re: speedup COPY TO for partitioned table.

Hi Jian, Tested this patch with COPY sales TO STDOUT; ~ 1.909ms, improving performance over the older COPY (SELECT * FROM sales) TO STDOUT; ~ 3.80ms method. This eliminates query planning overhead and significantly speeds up data export from partitioned tables. Our test setup involved creating