pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ron Johnson <ron.l.johnson@cox.net>
To: PgSQL Performance ML <pgsql-performance@postgresql.org>
Subject: Re: How to force Nested Loop plan?
Date: Sat, 30 Aug 2003 11:33:40 -0500
Message-ID: <1062261220.669.576.camel@haggis> (raw)
In-Reply-To: <16208.50934.351000.90704@gargle.gargle.HOWL>
References: <16208.41885.960000.12706@gargle.gargle.HOWL>
	<24637.1062255721@sss.pgh.pa.us>
	<16208.50934.351000.90704@gargle.gargle.HOWL>

On Sat, 2003-08-30 at 10:47, Rob Nagler wrote:
> Tom Lane writes:
[snip]
> enough.  When I add this index, I will slow down inserts (about
> 20K/day) and increase data size (this is the second largest table in
[snip]

Since I gather that this is a web-site, can we presume that they
are clumped into an 8 hour range?  20,000/8 = 2,500/hour, which
is 41.67/minute.  If you can't do .69 inserts/second, something
is wrong, and it ain't hardware, and it ain't Postgresql...

> > PS: does server_id really need to be NUMERIC?  Why not integer, or at
> > worst bigint?
> 
> It is a NUMERIC(18).  It could be a bigint.  What would be the change
> in performance of this query if we changed it to bigint?

http://www.postgresql.org/docs/7.3/static/datatype.html#DATATYPE-INT
http://www.postgresql.org/docs/7.3/static/datatype.html#DATATYPE-NUMERIC-DECIMAL

Scalars are faster than arbitrary precision types.  Small (32 bit)
scalars are faster than bit (64 bit) scalars on x86 h/w.

-- 
-----------------------------------------------------------------
Ron Johnson, Jr. ron.l.johnson@cox.net
Jefferson, LA USA

"Adventure is a sign of incompetence"
Stephanson, great polar explorer




view thread (13+ messages)  latest in thread

Message-ID: <1062261220.669.576.camel@haggis>
Permalink:  ../1062261220.669.576.camel@haggis/
Also on:    postgresql.org/message-id/1062261220.669.576.camel@haggis

 · 

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: ron.l.johnson@cox.net
  Subject: Re: How to force Nested Loop plan?
  In-Reply-To: <1062261220.669.576.camel@haggis>
  References: <16208.41885.960000.12706@gargle.gargle.HOWL> <24637.1062255721@sss.pgh.pa.us> <16208.50934.351000.90704@gargle.gargle.HOWL> <1062261220.669.576.camel@haggis>

* 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