From: Chris Browne <cbbrowne@acm.org>
To: pgsql-performance@postgresql.org
Subject: Re: int2 vs int4 in Postgres
Date: Mon, 26 Sep 2005 17:47:19 -0400
Message-ID: <607jd3lcwo.fsf@dba2.int.libertyrms.com> (raw)
References: <KBEKKNMFLELKGIADDEPEGEOKCAAA.truthhurts@insightbb.com>
truthhurts@insightbb.com ("Announce") writes:
> I KNOW that I am not going to have anywhere near 32,000+ different
> genres in my genre table so why use int4? Would that squeeze a few
> more milliseconds of performance out of a LARGE song table query
> with a genre lookup?
By the way, I see a lot of queries on tables NOT optimized in this
fashion that run in less than a millisecond, so it would seem
remarkable to me if there were milliseconds to be squeezed out in the
first place...
--
output = reverse("moc.enworbbc" "@" "enworbbc")
http://www.ntlug.org/~cbbrowne/sap.html
Why do we drive on parkways and park on driveways?
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: cbbrowne@acm.org
Subject: Re: int2 vs int4 in Postgres
In-Reply-To: <607jd3lcwo.fsf@dba2.int.libertyrms.com>
* 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