pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Tom Lane <tgl@sss.pgh.pa.us>
To: gpd@gpdnet.co.uk
Cc: pgsql-performance@postgresql.org
Subject: Re: [HACKERS] qsort again (was Re: Strange Create Index behaviour)
Date: Thu, 16 Feb 2006 09:42:40 -0500
Message-ID: <27898.1140100960@sss.pgh.pa.us> (raw)
In-Reply-To: <2417.84.92.210.49.1140087992.squirrel@www.gpdnet.co.uk>
References: <43F38867.6010701@gpdnet.co.uk>
	<19510.1140036968@sss.pgh.pa.us>
	<19779.1140038874@sss.pgh.pa.us>
	<43F39E53.1020009@gpdnet.co.uk>
	<20781.1140046109@sss.pgh.pa.us>
	<43F3BF72.6000202@gpdnet.co.uk>
	<21152.1140049020@sss.pgh.pa.us>
	<21455.1140051584@sss.pgh.pa.us>
	<2417.84.92.210.49.1140087992.squirrel@www.gpdnet.co.uk>

"Gary Doades" <gpd@gpdnet.co.uk> writes:
> I think the reason I wasn't seeing performance issues with normal sort
> operations is because they use work_mem not maintenance_work_mem which was
> only set to 2048 anyway. Does that sound right?

Very probable.  Do you want to test the theory by jacking that up?  ;-)

			regards, tom lane

Message-ID: <27898.1140100960@sss.pgh.pa.us>
Permalink:  ../27898.1140100960@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/27898.1140100960@sss.pgh.pa.us

copy link · copy postgr.es

reply

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-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, gpd@gpdnet.co.uk
  Subject: Re: [HACKERS] qsort again (was Re: Strange Create Index behaviour)
  In-Reply-To: <27898.1140100960@sss.pgh.pa.us>

* 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