pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Yaroslav Mazurak <yamazurak@Lviv.Bank.Gov.UA>
Cc: pgsql-performance@postgresql.org
Subject: Re: PostgreSQL performance problem -> tuning
Date: Wed, 06 Aug 2003 14:13:19 -0400
Message-ID: <1566.1060193599@sss.pgh.pa.us> (raw)
In-Reply-To: <3F30AF9E.2080607@lviv.bank.gov.ua>
References: <3F30AF9E.2080607@lviv.bank.gov.ua>

Yaroslav Mazurak <yamazurak@Lviv.Bank.Gov.UA> writes:
> 	Current postgresql.conf settings (some) are:

> max_locks_per_transaction = 16

This strikes me as a really bad idea --- you save little space by
reducing it from the default, and open yourself up to unexpected failures.

> wal_buffers = 256

That is almost certainly way more than you need.

> sort_mem = 131072

People have already told you that one's a bad idea.

> commit_delay = 32000

I'm unconvinced that setting this nonzero is a good idea.  Have you done
experiments to prove that you get a benefit?

> enable_seqscan = false

This is the cause of the bizarre-looking cost estimates.  I don't
recommend setting it false as a system-wide setting.  If you want
to nudge the planner towards indexscans, reducing random_page_cost
a little is probably a better way.

			regards, tom lane



view thread (24+ messages)  latest in thread

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

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, yamazurak@Lviv.Bank.Gov.UA
  Subject: Re: PostgreSQL performance problem -> tuning
  In-Reply-To: <1566.1060193599@sss.pgh.pa.us>
  References: <3F30AF9E.2080607@lviv.bank.gov.ua> <1566.1060193599@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