Re: Changing work_mem

2019-08-14 Thread rihad
On 08/14/2019 11:42 AM, Laurenz Albe wrote: rihad wrote: Sorry, I just decreased work_mem back to 256MB, reloaded, and instantly started seeing 82mb temp file creation, not 165mb as was usual with work_mem=512MB. So it indeed was applied immediately. Really weird figures ) Increased work_mem t

Re: Changing work_mem

2019-08-14 Thread Laurenz Albe
rihad wrote: > > Sorry, I just decreased work_mem back to 256MB, reloaded, and > > instantly started seeing 82mb temp file creation, not 165mb as was > > usual with work_mem=512MB. > > > > So it indeed was applied immediately. > > Really weird figures ) > > Increased work_mem to 768MB and start

Re: Changing work_mem

2019-08-13 Thread rihad
On 08/13/2019 09:04 PM, rihad wrote: On 08/13/2019 08:44 PM, rihad wrote: On 08/13/2019 08:22 PM, Luca Ferrari wrote: On Tue, Aug 13, 2019 at 5:59 PM rihad wrote: [dbname] LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp93683.257381", size 594 The setting 'work_mem' is within context 'u

Re: Changing work_mem

2019-08-13 Thread rihad
On 08/13/2019 08:44 PM, rihad wrote: On 08/13/2019 08:22 PM, Luca Ferrari wrote: On Tue, Aug 13, 2019 at 5:59 PM rihad wrote: [dbname] LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp93683.257381", size 594 The setting 'work_mem' is within context 'user', that means it will affect runnin

Re: Changing work_mem

2019-08-13 Thread Rob Sargent
On 8/13/19 11:04 AM, rihad wrote: On 08/13/2019 08:44 PM, rihad wrote: On 08/13/2019 08:22 PM, Luca Ferrari wrote: On Tue, Aug 13, 2019 at 5:59 PM rihad wrote: [dbname] LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp93683.257381", size 594 The setting 'work_mem' is within context 'us

Re: Changing work_mem

2019-08-13 Thread rihad
On 08/13/2019 08:22 PM, Luca Ferrari wrote: On Tue, Aug 13, 2019 at 5:59 PM rihad wrote: [dbname] LOG: temporary file: path "base/pgsql_tmp/pgsql_tmp93683.257381", size 594 The setting 'work_mem' is within context 'user', that means it will affect running sessione unless the session itself h

Re: Changing work_mem

2019-08-13 Thread Luca Ferrari
On Tue, Aug 13, 2019 at 5:59 PM rihad wrote: > [dbname] LOG: temporary file: path > "base/pgsql_tmp/pgsql_tmp93683.257381", size 594 > The setting 'work_mem' is within context 'user', that means it will affect running sessione unless the session itself has already issued a SET work_mem to xxx. S

Re: Changing work_mem

2019-08-13 Thread rihad
On 08/13/2019 07:41 PM, Peter Eisentraut wrote: On 2019-08-13 17:16, rihad wrote: If I increase it in postgresql.conf and SIGHUP the master server, will the change be applied to all running backends, or only to the ones started after the change? Thanks. It will be applied to all running backend

Re: Changing work_mem

2019-08-13 Thread Peter Eisentraut
On 2019-08-13 17:16, rihad wrote: > If I increase it in postgresql.conf and SIGHUP the master server, will > the change be applied to all running backends, or only to the ones > started after the change? Thanks. It will be applied to all running backends. -- Peter Eisentraut http:

Changing work_mem

2019-08-13 Thread rihad
If I increase it in postgresql.conf and SIGHUP the master server, will the change be applied to all running backends, or only to the ones started after the change? Thanks.