Re: Query Performance SQL Server vs. Postgresql - Mailing list pgsql-performance

From tv@fuzzy.cz
Subject Re: Query Performance SQL Server vs. Postgresql
Date
Msg-id fe8b9f344e9575056f79658e6c639d4d.squirrel@sq.gransy.com
Whole thread Raw
In response to Re: Query Performance SQL Server vs. Postgresql  (Samuel Gendler <sgendler@ideasculptor.com>)
List pgsql-performance
> I believe you can set work_mem to a different value just for the duration
> of
> a single query, so you needn't have work_mem set so high if for every
> query
> on the system.  A single query may well use a multiple of work_mem, so you
> really probably don't want it that high all the time unless all of your
> queries are structured similarly.  Just set work_mem='2047MB'; query;
> reset
> all;

Yes, executing "set work_mem='64MB'" right before the query should be just
fine. Setting work_mem to 2GB is an overkill most of the time (99.99999%).

Tomas


pgsql-performance by date:

Previous
From: Samuel Gendler
Date:
Subject: Re: Query Performance SQL Server vs. Postgresql
Next
From: "Kevin Grittner"
Date:
Subject: Re: Slow SELECT on small table