Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: High update activity, PostgreSQL vs BigDBMS
- From: Arnau <arnaulist(at)andromeiberica(dot)com>
- To: PostgreSQL Performance <pgsql-performance(at)postgresql(dot)org>
- Subject: Re: High update activity, PostgreSQL vs BigDBMS
- Date: Fri, 29 Dec 2006 15:26:15 +0100
Hi all,
A= go through each query and see what work_mem needs to be for that query to be as RAM resident as possible. If you have enough RAM, set work_mem for that query that large. Remember that work_mem is =per query=, so queries running in parallel eat the sum of each of their work_mem's.
How can I know what work_mem needs a query needs? Regards -- Arnau
- References:
- High update activity, PostgreSQL vs BigDBMS
- From: Guy Rouillier
- Re: High update activity, PostgreSQL vs BigDBMS
- From: Ron
- High update activity, PostgreSQL vs BigDBMS
- Prev by Date: Re: High update activity, PostgreSQL vs BigDBMS
- Next by Date: Re: Backup/Restore too slow
- Previous by thread: Re: High update activity, PostgreSQL vs BigDBMS
- Next by thread: Re: High update activity, PostgreSQL vs BigDBMS
- Indexes: