Find more info on this site .
Postgres Work Mem
If sorting or hash table needs more memory than permitted by work_mem , then PostgreSQL will use temp files on disk to perform such operations. I know I can use SHOW WORK_MEM; in psql to view the value of the connection currently used. Sets the base maximum amount of memory to be used by a query operation (such as a sort or hash table) before writing to temporary disk files. If a single query execution plan contains more than one memory-hungry execution steps, this query can use. PostgreSQL uses the value of work_mem setting as the limit on how much memory each query may use for each sorting operation or hash table. Fine-tune work_mem in PostgreSQL to get the best performance. In Amazon Relational Database Service (Amazon RDs) for PostgreSQL and Amazon Aurora PostgreSQL-Compatible Edition, the parameter that dictates how much of memory can be allocated for a sort is work_mem. Our Support Team is here to demonstrate how to use work_mem to get the most out of it. If sorting requires more than the allocated work_mem, it leads to physical I. work_mem (integer) Specifies the amount of memory to be used by internal sort operations and hash tables before writing to temporary disk files. Note that for a complex query, several sort or hash operations might be running in parallel; each operation will be allowed to use as much memory as this.
`
Postgres Work Mem Info
Setting the larger value might improve performance for vacuuming and restoring database dumps. work_mem tells Postgres how much RAM can be allocated by a query before a file on disk is created. Our Support Team is here to demonstrate how to use work_mem to get the most out of it. Not all operations require such a 'buffer' to work on, but it is important to let the system know that some amount of memory can be used when needed. PostgreSQL uses the value of work_mem setting as the limit on how much memory each query may use for each sorting operation or hash table. The server is dedicated to this database. The logical_decoding_work_mem parameter can be set in postgresql.conf, where it serves as the default for all publishers on that instance. If this value is specified without units, it is taken as kilobytes. It limits the amount of memory available for a single step in an execution plan (sort, hash or bitmap). I know I can use SHOW WORK_MEM; in psql to view the value of the connection currently used. This size is applied to each and every sort done by each user, and complex queries can use multiple working memory sort.
