truthhurts(at)insightbb(dot)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
output = reverse("moc.enworbbc" "@" "enworbbc")
Why do we drive on parkways and park on driveways?
In response to
pgsql-performance by date
|Next:||From: Tom Lane||Date: 2005-09-26 23:00:31|
|Subject: Re: int2 vs int4 in Postgres |
|Previous:||From: Chris Browne||Date: 2005-09-26 21:45:56|
|Subject: Re: int2 vs int4 in Postgres|