Re: [PERFORM] another query optimization question

2004-01-31 Thread David Teran
Hi, I'm not sure ... I thought I ran it on my P4 here in the office and saw it too, albeit not near as frequently ... but, in FreeBSD's case, it is a "design issue" ... there are two different functions, once that is kinda fuzzy (but fast), and the other that is designed to be exact, but at a pe

Re: [PERFORM] another query optimization question

2004-01-31 Thread Marc G. Fournier
On Sat, 31 Jan 2004, Tom Lane wrote: > David Teran <[EMAIL PROTECTED]> writes: > > Apple provides a little tool that can enable / disable the l2 cache ... > > one CPU of a dual CPU system on the fly. When i start the testapp with > > two CPU's enabled i get this output here, when i turn off one CP

Re: [PERFORM] High Performance/High Reliability File system on SuSE64

2004-01-31 Thread Bruce Momjian
Christopher Weimann wrote: > On 01/23/2004-10:18AM, Joshua D. Drake wrote: > > > > XFS also has the interesting ability (although I have yet to test it) > > that will allow you > > to take a snapshot of the filesystem. Thus you can have filesystem level > > backups > > of the PGDATA directory th

Re: [PERFORM] another query optimization question

2004-01-31 Thread Tom Lane
David Teran <[EMAIL PROTECTED]> writes: > Apple provides a little tool that can enable / disable the l2 cache ... > one CPU of a dual CPU system on the fly. When i start the testapp with > two CPU's enabled i get this output here, when i turn off one CPU while > the app is still running the mess

Re: [PERFORM] another query optimization question

2004-01-31 Thread David Teran
Hi Tim, you are right: Interesting. I have recollected where we saw this before: http://archives.postgresql.org/pgsql-hackers/2003-11/msg01528.php Apparently gettimeofday() has a glitch on some BSD releases. OS X is a BSD derivative and it's not so surprising if it has it too. May I suggest th

Re: [PERFORM] Unique index and estimated rows.

2004-01-31 Thread Kari Lavikka
Uh oh, function indexes seem to be a bit crippled. I created a unique index without the upper() function and number of estimated rows is now just right. "users_nick" unique, btree (nick) And the plan: galleria=> explain analyze SELECT i.image_id, i.info, i.stamp, i.status, i.t_width, i.t_h