From: SASIKUMAR Devaraj <sashikumard@yahoo.com>
To: MichaelDBA@sqlexec.com, MichaelDBA <MichaelDBA@sqlexec.com>
Cc: holger@jakobs.com
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: work_mem
Date: Fri, 2 Apr 2021 12:45:52 +0000 (UTC)
Message-ID: <1654783699.2333997.1617367552583@mail.yahoo.com> (raw)
In-Reply-To: <c1e02a03-71cd-4071-e000-967403bcab9d@sqlexec.com>
References: <A2AA6D08-9506-4B41-9738-4D5FF8E2E011@illinois.edu>
<04D84259-1B75-4648-949F-78677916194E@jakobs.com>
<66290583.2329958.1617367063840@mail.yahoo.com>
<c1e02a03-71cd-4071-e000-967403bcab9d@sqlexec.com>
Thanks Michael
For example work_mem is 4M and if I had 300 connections connected to dB the total memory requirement is 1.2 Gb. So as per my understanding this 1.2 gb is not allocated as soon as 300 connections established, but it may vary from 0 to 1.2gb as per operations from client. Please confirm
Regards
Sasi
Sent from Yahoo Mail on Android
On Fri, Apr 2, 2021 at 6:09 PM, MichaelDBA<MichaelDBA@sqlexec.com> wrote: Memory is allocated dynamically per internal work_mem buffer requests.
SASIKUMAR Devaraj wrote on 4/2/2021 8:37 AM:
Hi All
As soon as client session is established work_mem will be allocated or only when sort happens for that particular session? Please advise how the internal behavior? This will help me to configure my database memory with high connections
Regards
Sasi
Sent from Yahoo Mail on Android
On Wed, Mar 31, 2021 at 8:52 PM, Holger Jakobs<holger@jakobs.com> wrote: #yiv8729720470 -- filtered {}#yiv8729720470 filtered {}#yiv8729720470 filtered {}#yiv8729720470 p.yiv8729720470MsoNormal, #yiv8729720470 li.yiv8729720470MsoNormal, #yiv8729720470 div.yiv8729720470MsoNormal {margin:0in;font-size:12.0pt;font-family:sans-serif;}#yiv8729720470 span.yiv8729720470EmailStyle17 {font-family:sans-serif;color:windowtext;}#yiv8729720470 .yiv8729720470MsoChpDefault {font-size:12.0pt;font-family:sans-serif;}#yiv8729720470 filtered {}#yiv8729720470 div.yiv8729720470WordSection1 {}#yiv8729720470 You can show any or all settings with the command SHOW.
show work_mem;
show all;
How many times the amount of work_mem has been allocated currently cannot be shown this way. Any sort operation running currently allocates it. So it is not identical with the number of current queries, because queries can allocate it several times.
Am 31. März 2021 16:04:07 MESZ schrieb "Campbell, Lance" <lance@illinois.edu>:
PostgreSQL 12
Is there a query that will tell us at any given time what amount of PostgreSQL memory is being used for work_mem?
Thanks,
LANCE CAMPBELL
Web Services
Public Affairs
Under the Illinois Freedom of Information Act any written communication to or from university employees regarding university business is a public record and may be subject to public disclosure.
--
Holger Jakobs, Bergisch Gladbach
+49 178 9759012
- sent from mobile, therefore short -
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: sashikumard@yahoo.com, MichaelDBA@sqlexec.com, holger@jakobs.com, pgsql-admin@lists.postgresql.org
Subject: Re: work_mem
In-Reply-To: <1654783699.2333997.1617367552583@mail.yahoo.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox