| From: | Andrey Lepikhov <a(dot)lepikhov(at)postgrespro(dot)ru> |
|---|---|
| To: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Increase value of OUTER_VAR |
| Date: | 2021-09-15 06:41:38 |
| Message-ID: | f2cf616d-608d-98ed-245b-3e11296431ce@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 14/9/21 16:37, Aleksander Alekseev wrote:
> Hi Andrey,
>
>> only performance issues
>
> That's interesting. Any chance you could share the hardware
> description, the configuration file, and steps to reproduce with us?
>
I didn't control execution time exactly. Because it is a join of two
empty tables. As I see, this join used most part of 48GB RAM memory,
planned all day on a typical 6 amd cores computer.
I guess this is caused by sequental traversal of the partition list in
some places in the optimizer.
If it makes practical sense, I could investigate reasons for such poor
performance.
--
regards,
Andrey Lepikhov
Postgres Professional
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2021-09-15 06:46:50 | Re: Teach pg_receivewal to use lz4 compression |
| Previous Message | Alexander Pyhalov | 2021-09-15 06:40:46 | Re: Defer selection of asynchronous subplans until the executor initialization stage |