I had the same question recently. In addition, I looked at the results of
tpch which scale factor is 1 ran on postgres REL_15_STABLE and observed no
performance improvement from physical tlist. To be specific, I run two
versions of tpch, one with physical tlist enabled and one with physical
tlist
On 2023-Jul-26, Jian Guo wrote:
> It looks the columns besides `ps_supplycost` and `ps_availqty` are not
> necessary, but fetched from tuples all at once. For the row-based
> storage such as heap, it looks fine, but for column-based storage, it
> would result into unnecessary overhead and impact
Hi hackers,
I have a question about `use_physical_tlist()` which is applied in
`create_scan_plan()`:
```
if (flags == CP_IGNORE_TLIST)
{
tlist = NULL;
}
else if (use_physical_tlist(root, best_path, flags))
{
if (best_path->pathtype == T_IndexOnlyScan)
{
/* For index-only scan, the
