Re: [HACKERS] SourceForge Postgres

2001-02-10 Thread Oleg Bartunov
Tim, I've found your message in postgres hackers list and wondering if sourceforge db part could be improved using our recent (7.1) GiST improvements. In short, using RD-Tree + GiST we've added index support for arrays of integers. For example, in our rather busy web site we have pool of online

Re: [HACKERS] SourceForge Postgres

2001-01-22 Thread Bruce Momjian
Tim, how is PostgreSQL working for you? -- Start of PGP signed section. I thought the hackers team would be interested in knowing that SourceForge, as of Friday evening, is running on Postgres. Some 95,000 users and 12,500 Open Source projects are depending on your stuff, so I hope it's

AW: [HACKERS] SourceForge Postgres

2000-12-12 Thread Zeugswetter Andreas SB
I have an index on group_id, one on (group_id,status_id) and one on (group_id,status_id,assigned_to) As an aside notice: you should definitely only need the last of the three indices, since it can perfectly work on group_id or group_id + status_id only restrictions. Andreas

AW: [HACKERS] SourceForge Postgres (attdispursion)

2000-12-12 Thread Zeugswetter Andreas SB
btw anyone trying this query should use: "attdispersion" I see it, yes. Was this an intended change ? I am quite sure, that it was attdisbursion in 7.0 ? Andreas

Re: AW: [HACKERS] SourceForge Postgres (attdispursion)

2000-12-12 Thread Bruce Momjian
I see it, yes. Was this an intended change ? I am quite sure, that it was attdisbursion in 7.0 ? Yes, I couldn't spell dispersion in the past. :-) -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a

Re: [HACKERS] SourceForge Postgres

2000-12-12 Thread mlw
Tom Lane wrote: mlw [EMAIL PROTECTED] writes: btw anyone trying this query should use: "attdispersion" Sorry about that --- I just copied-and-pasted the query from some notes that are obsolete as of 7.1... cdinfo=# explain select * from ztitles where artistid = 10220 ; NOTICE:

[HACKERS] SourceForge Postgres

2000-12-11 Thread Tim Perdue
I thought the hackers team would be interested in knowing that SourceForge, as of Friday evening, is running on Postgres. Some 95,000 users and 12,500 Open Source projects are depending on your stuff, so I hope it's going to be stable for us. ;-) Throughout the codebase we're making good use of

Re: [HACKERS] SourceForge Postgres

2000-12-11 Thread mlw
Bruce Momjian wrote: This is great news. As far as the optimizer, any chance of testing 7.1 to see if it is improved. I believe it has been over 7.0.3. I just did a test of my database that exhibits this behavior, using 7.1 from CVS. When postmaster is started with "-o -fs" I get this:

Re: [HACKERS] SourceForge Postgres

2000-12-11 Thread Tom Lane
Tim Perdue [EMAIL PROTECTED] writes: I thought the hackers team would be interested in knowing that SourceForge, as of Friday evening, is running on Postgres. Cool! I'm running into some places where the query optimizer is not using the right indexes, and sometimes does sequential scans on

Re: [HACKERS] SourceForge Postgres

2000-12-11 Thread The Hermit Hacker
one thing I've found to get around this is for any query that doesn't appear to use the index properly, just do: SET ENABLE_SEQSCAN=OFF; query SET ENABLE_SEQSCAN=ON; that way for those queries that do work right, ou haven't forced it a different route .. On Mon, 11 Dec 2000, mlw wrote: