Re: Death postgres

On 2023-05-12 17:41:37 +0200, Marc Millas wrote: > On Fri, May 12, 2023 at 8:31 AM Peter J. Holzer wrote: > My guess is that the amount of parallelism is the problem. > > work_mem is a per-node limit. Even a single process can use a multiple of > work_mem if the query contains nested

Re: Death postgres

On Fri, May 12, 2023 at 8:31 AM Peter J. Holzer wrote: > On 2023-05-11 21:27:57 +0200, Marc Millas wrote: > > the 75 lines in each tables are not NULLs but '' empty varchar, > which, > > obviously is not the same thing. > > and which perfectly generates 500 billions lines for the left join.

Re: Death postgres

On 2023-05-11 21:27:57 +0200, Marc Millas wrote: > the 75 lines in each tables are not NULLs but '' empty varchar, which, > obviously is not the same thing. > and which perfectly generates 500 billions lines for the left join. > So, no planner or statistics pbs. apologies for the time wasted.

Re: Death postgres

On Thu, May 11, 2023 at 1:56 AM Peter J. Holzer wrote: > On 2023-05-10 22:52:47 +0200, Marc Millas wrote: > > On Wed, May 10, 2023 at 7:24 PM Peter J. Holzer > wrote: > > > > On 2023-05-10 16:35:04 +0200, Marc Millas wrote: > > > Unique (cost=72377463163.02..201012533981.80

Re: Death postgres

On Thu, May 11, 2023 at 1:56 AM Peter J. Holzer wrote: > On 2023-05-10 22:52:47 +0200, Marc Millas wrote: > > On Wed, May 10, 2023 at 7:24 PM Peter J. Holzer > wrote: > > > > On 2023-05-10 16:35:04 +0200, Marc Millas wrote: > > > Unique (cost=72377463163.02..201012533981.80

Re: Death postgres

On 2023-05-10 22:52:47 +0200, Marc Millas wrote: > On Wed, May 10, 2023 at 7:24 PM Peter J. Holzer wrote: > > On 2023-05-10 16:35:04 +0200, Marc Millas wrote: > >  Unique  (cost=72377463163.02..201012533981.80 rows=1021522829864 width= > 97) > >    ->  Gather Merge  

Re: Death postgres

On Wed, May 10, 2023 at 7:24 PM Peter J. Holzer wrote: > On 2023-05-10 16:35:04 +0200, Marc Millas wrote: > > Unique (cost=72377463163.02..201012533981.80 rows=1021522829864 > width=97) > >-> Gather Merge (cost=72377463163.02..195904919832.48 > rows=1021522829864 width=97) > ... > >

Re: Death postgres

On 2023-05-10 16:35:04 +0200, Marc Millas wrote: >  Unique  (cost=72377463163.02..201012533981.80 rows=1021522829864 width=97) >    ->  Gather Merge  (cost=72377463163.02..195904919832.48 rows=1021522829864 > width=97) ... >                ->  Parallel Hash Left Join  

Re: Death postgres

On Wed, 2023-05-10 at 16:35 +0200, Marc Millas wrote: > > > postgres 14.2 on Linux redhat > > > > > > temp_file_limit set around 210 GB. > > > > > > a select request with 2 left join have crashed the server (oom killer) > > > after the postgres > > > disk occupation did grow from 15TB to 16 TB.

Re: Death postgres

On Sun, May 7, 2023 at 8:42 PM Laurenz Albe wrote: > On Sat, 2023-05-06 at 03:14 +0200, Marc Millas wrote: > > postgres 14.2 on Linux redhat > > > > temp_file_limit set around 210 GB. > > > > a select request with 2 left join have crashed the server (oom killer) > after the postgres > > disk

Re: Death postgres

On Sat, 2023-05-06 at 03:14 +0200, Marc Millas wrote: > postgres 14.2 on Linux redhat > > temp_file_limit set around 210 GB. > > a select request with 2 left join have crashed the server (oom killer) after > the postgres > disk occupation did grow from 15TB to 16 TB. > > What are the cases

Re: Death postgres

On 5/7/23 04:46, Marc Millas wrote: Le sam. 6 mai 2023 à 21:46, Adrian Klaver > a écrit : On 5/6/23 10:13, Marc Millas wrote: > > >     When you restarted the server where there any warnings shown? > > Sadly, I cannot. Will be

Re: Death postgres

Le sam. 6 mai 2023 à 21:46, Adrian Klaver a écrit : > On 5/6/23 10:13, Marc Millas wrote: > > > > > > > When you restarted the server where there any warnings shown? > > > > Sadly, I cannot. Will be done next tuesday. > > Cannot do what: > > 1) Get to the log to see if there are warnings? >

Re: Death postgres

On 5/6/23 10:13, Marc Millas wrote: When you restarted the server where there any warnings shown? Sadly, I cannot. Will be done next tuesday. Cannot do what: 1) Get to the log to see if there are warnings? 2) Restart the server? Your original post said the server crashed. If that

Re: Death postgres

Le sam. 6 mai 2023 à 18:11, Adrian Klaver a écrit : > On 5/6/23 05:25, Marc Millas wrote: > > > > > > Le sam. 6 mai 2023 à 06:18, Adrian Klaver > > a écrit : > > > > On 5/5/23 18:14, Marc Millas wrote: > > > Hi, > > > > > > postgres 14.2 on

Re: Death postgres

On 5/6/23 05:25, Marc Millas wrote: Le sam. 6 mai 2023 à 06:18, Adrian Klaver > a écrit : On 5/5/23 18:14, Marc Millas wrote: > Hi, > > postgres 14.2 on Linux redhat > > temp_file_limit set around 210 GB. > > a select

Re: Death postgres

On 2023-05-05 21:14, Marc Millas wrote: Hi, postgres 14.2 on Linux redhat temp_file_limit set around 210 GB. a select request with 2 left join have crashed the server (oom killer) after the postgres disk occupation did grow from 15TB to 16 TB. What are the cases where postgres may grow

Re: Death postgres

On 5/6/23 08:52, Marc Millas wrote: Le sam. 6 mai 2023 à 15:15, Ron a écrit : [snip] If your question is about temp_file_limit, don't distract us with OOM issues. My question is how postgres can use space without caring about temp_file_limit. The oom info is kind of hint about

Re: Death postgres

Le sam. 6 mai 2023 à 15:15, Ron a écrit : > On 5/6/23 07:19, Marc Millas wrote: > > > > Le sam. 6 mai 2023 à 09:46, Peter J. Holzer a écrit : > >> On 2023-05-06 03:14:20 +0200, Marc Millas wrote: >> > postgres 14.2 on Linux redhat >> > >> > temp_file_limit set around 210 GB. >> > >> > a select

Re: Death postgres

Le sam. 6 mai 2023 à 15:15, Ron a écrit : > On 5/6/23 07:19, Marc Millas wrote: > > > > Le sam. 6 mai 2023 à 09:46, Peter J. Holzer a écrit : > >> On 2023-05-06 03:14:20 +0200, Marc Millas wrote: >> > postgres 14.2 on Linux redhat >> > >> > temp_file_limit set around 210 GB. >> > >> > a select

Re: Death postgres

On 5/6/23 07:19, Marc Millas wrote: Le sam. 6 mai 2023 à 09:46, Peter J. Holzer a écrit : On 2023-05-06 03:14:20 +0200, Marc Millas wrote: > postgres 14.2 on Linux redhat > > temp_file_limit set around 210 GB. > > a select request with 2 left join have crashed the

Re: Death postgres

Le sam. 6 mai 2023 à 06:18, Adrian Klaver a écrit : > On 5/5/23 18:14, Marc Millas wrote: > > Hi, > > > > postgres 14.2 on Linux redhat > > > > temp_file_limit set around 210 GB. > > > > a select request with 2 left join have crashed the server (oom killer) > > after the postgres disk occupation

Re: Death postgres

Le sam. 6 mai 2023 à 09:46, Peter J. Holzer a écrit : > On 2023-05-06 03:14:20 +0200, Marc Millas wrote: > > postgres 14.2 on Linux redhat > > > > temp_file_limit set around 210 GB. > > > > a select request with 2 left join have crashed the server (oom killer) > after > > the postgres disk

Re: Death postgres

On 2023-05-06 03:14:20 +0200, Marc Millas wrote: > postgres 14.2 on Linux redhat > > temp_file_limit set around 210 GB. > > a select request with 2 left join have crashed the server (oom killer) after > the postgres disk occupation did grow from 15TB to 16 TB. temp_file_limit limits the space a

Re: Death postgres

On 5/5/23 18:14, Marc Millas wrote: Hi, postgres 14.2 on Linux redhat temp_file_limit set around 210 GB. a select request with 2 left join have crashed the server (oom killer) after the postgres disk occupation did grow from 15TB to 16 TB. The result of EXPLAIN would be helpful. What

Death postgres

Hi, postgres 14.2 on Linux redhat temp_file_limit set around 210 GB. a select request with 2 left join have crashed the server (oom killer) after the postgres disk occupation did grow from 15TB to 16 TB. What are the cases where postgres may grow without caring about temp_file_limit ? thanks,