[PERFORM] Indexing a Boolean or Null column?

2004-01-03 Thread D. Dante Lorenso
I've been debating with a collegue who argues that indexing a boolean column is a BAD idea and that is will actually slow down queries. My plan is to have a table with many rows sharing 'versions' (version/archive/history) of data where the most current row is the one where 'is_active' contains a t

Re: [PERFORM] Indexing a Boolean or Null column?

2004-01-03 Thread D. Dante Lorenso
Christopher Kings-Lynne wrote: > > Will an index on the 'data_is_active' column be used or work > > as I expect? I'm assuming that I may have a million entries > > sharing the same 'data_lookup_key' and I'll be using that to > > search for the active version of the row. > An index just on a boole

[PERFORM] Find original number of rows before applied LIMIT/OFFSET?

2004-01-07 Thread D. Dante Lorenso
00 records across the wire when I only intend to show 10 at a time. See what I'm getting at? TIA, Dante - D. Dante Lorenso [EMAIL PROTECTED] ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org

[PERFORM] Postgresql on Quad CPU machine

2004-01-11 Thread D. Dante Lorenso
I'm running PostgreSQL 7.4 on a quad Xeon attached to a beefy disk array. However, I am begining to wonder if this is a waste of CPU power. I think I read somewhere that PostgreSQL is NOT multi-threaded. But, will it be able to take advantage of multiple CPUs? Will I have to run separate postmast