Hello colleagues -
The problem description:
We're moving from 9.6 to 11.5. There is a SQL code that never ends in 11.5
but works fine in 9.6. The main cause is the optimizer considers of using NL
Anti join instead of Merge in 9.6. And the root cause - wrong estimation
while self-joining.
S
On Mon, Nov 18, 2019 at 03:46:03PM +0100, Ekaterina Amez wrote:
El 18/11/19 a las 15:16, Tomas Vondra escribió:
Not sure I understand. Whenever PostgreSQL process needs memory it
requests it from the kernel by calling malloc(), and the amount of
availabe RAM is limited. So when kernel can't p
El 18/11/19 a las 15:16, Tomas Vondra escribió:
Not sure I understand. Whenever PostgreSQL process needs memory it
requests it from the kernel by calling malloc(), and the amount of
availabe RAM is limited. So when kernel can't provide more memory,
it returns NULL.
Understood.
If it fini
On Mon, Nov 18, 2019 at 03:02:16PM +0100, Ekaterina Amez wrote:
El 18/11/19 a las 13:25, Tomas Vondra escribió:
On Mon, Nov 18, 2019 at 12:41:27PM +0100, Ekaterina Amez wrote:
Hi all,
This morning I was checking postgres servers logs, looking for
errors (we've recently upgraded them and chan
El 18/11/19 a las 13:25, Tomas Vondra escribió:
On Mon, Nov 18, 2019 at 12:41:27PM +0100, Ekaterina Amez wrote:
Hi all,
This morning I was checking postgres servers logs, looking for errors
(we've recently upgraded them and changed default config) and long
running queries when I found one of
On Mon, Nov 18, 2019 at 12:41:27PM +0100, Ekaterina Amez wrote:
Hi all,
This morning I was checking postgres servers logs, looking for errors
(we've recently upgraded them and changed default config) and long
running queries when I found one of the servers had really big logs
since yesterday.
Hi all,
This morning I was checking postgres servers logs, looking for errors
(we've recently upgraded them and changed default config) and long
running queries when I found one of the servers had really big logs
since yesterday. It was giving the error of this mail's subject: out of
memory,