| From: | "bucoo" <bucoo(at)sohu(dot)com> |
|---|---|
| To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "'David Rowley'" <dgrowleyml(at)gmail(dot)com> |
| Cc: | "'Robert Haas'" <robertmhaas(at)gmail(dot)com>, "'pgsql-hackers'" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | re: partition wise aggregate wrong rows cost |
| Date: | 2022-05-24 06:06:28 |
| Message-ID: | 000c01d86f34$6926c280$3b744780$@sohu.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> We try fairly hard to ensure that the row count estimate for a given relation
> does not vary across paths, so I concur with the OP that this is a bug. Having
> said that, I'm not sure that the consequences are significant. As you say, the
> estimates seem to get a lot closer as soon as the table has some statistics.
> (But nonetheless, they are not identical, so it's still a bug.)
Yes, the estimates seem to get a lot closer as soon as the table has some statistics.
> I'm not sure that the consequences are significant.
At least it doesn't make any difference to me for now.
I noticed this problem while testing aggregation.
It looks a little weird, so I emailed.
Thanks every one.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2022-05-24 06:11:28 | enable/disable broken for statement triggers on partitioned tables |
| Previous Message | Michael Paquier | 2022-05-24 06:03:28 | Improve TAP tests of pg_upgrade for cross-version tests |