Horton

Mark Stosberg

mark@summersault.com

Email: mark@summersault.com
Name: Mark Stosberg
Messages: 63
First message: 2000-12-06
Last message: 2011-10-29

Recent messages

DateSubject
2011-10-29T14:45:22Z Re: application of KNN code to US zipcode searches?
2011-02-17T20:38:30Z Re: application of KNN code to US zipcode searches?
2011-02-17T16:41:51Z Re: application of KNN code to US zipcode searches?
2011-02-17T15:55:53Z Re: application of KNN code to US zipcode searches?
2011-02-17T15:20:58Z Re: application of KNN code to US zipcode searches?
2011-02-17T14:40:56Z application of KNN code to US zipcode searches?
2011-02-04T21:18:18Z Re: getting the most of out multi-core systems for repeated complex SELECT statements
2011-02-03T16:16:15Z Re: getting the most of out multi-core systems for repeated complex SELECT statements
2011-02-03T15:08:35Z getting the most of out multi-core systems for repeated complex SELECT statements
2010-10-30T14:04:11Z BUG #5734: autovacuum_enabled input should be validated, standardized.
2010-05-07T14:10:31Z Re: debugging handle exhaustion and 15 min/ 5mil row delete
2010-05-07T13:37:42Z debugging handle exhaustion and 15 min/ 5mil row delete
2009-12-10T16:44:32Z Re: Help me put 2 Gigs of RAM to use
2009-12-10T15:50:10Z Fw: Help me put 2 Gigs of RAM to use
2008-04-10T21:28:51Z Re: recommendations for web/db connection pooling or DBD::Gofer reviews
2008-04-08T13:50:40Z Re: bulk insert performance problem
2008-04-08T13:45:07Z Re: what worked: performance improvements for geo-spatial searching on FreeBSD
2008-04-07T19:50:19Z per-review of PgBouncer / Slony design
2008-04-07T18:36:00Z recommendations for web/db connection pooling or DBD::Gofer reviews
2008-04-07T18:35:14Z what worked: performance improvements for geo-spatial searching on FreeBSD
2007-02-26T19:46:18Z Re: Writting a "search engine" for a pgsql DB
2007-02-26T18:15:07Z Re: Writting a "search engine" for a pgsql DB
2007-02-26T17:32:09Z Re: Writting a "search engine" for a pgsql DB
2007-02-26T17:26:23Z Re: low memory usage reported by 'top' indicates poor tuning?
2007-02-26T16:52:09Z low memory usage reported by 'top' indicates poor tuning?
2007-02-23T20:59:33Z Re: pg_autovacuum should allow NULL values
2007-02-23T18:51:35Z pg_autovacuum should allow NULL values
2007-02-22T21:53:52Z Using the 8.2 autovacuum values with 8.1
2007-02-21T20:28:34Z Re: Auto-Vacuum in 8.1 was ineffective for me. 8.2 may work better?
2007-02-21T18:37:10Z Auto-Vacuum in 8.1 was ineffective for me. 8.2 may work better?
2007-02-21T18:02:16Z How to avoid vacuuming a huge logging table
2007-02-21T17:49:12Z Re: How to debug performance problems
2007-02-16T19:25:21Z Re: reindex vs 'analyze'
2007-02-14T19:05:02Z Re: reindex vs 'analyze'
2007-02-14T16:28:38Z reindex vs 'analyze' (was: Re: cube operations slower than geo_distance() on production server)
2007-02-13T20:47:47Z Re: cube operations slower than geo_distance() on production server
2007-02-12T19:48:58Z Re: cube operations slower than geo_distance() on production server
2007-02-12T16:11:19Z Re: cube operations slower than geo_distance() on production server
2007-02-09T21:04:31Z Re: Can anyone make this code tighter? Too slow, Please help!
2007-02-09T19:26:01Z cube operations slower than geo_distance() on production server
2007-02-08T17:11:25Z Re: Speed up this query
2007-02-07T21:30:16Z tip: faster sorting for proximity queries by using cube_distance()
2007-02-06T14:54:59Z Re: explain analyze output: vacuuming made a big difference.
2007-02-06T14:39:54Z Re: explain analyze output for review (was: optimizing a geo_distance()...)
2007-02-05T23:01:05Z Re: optimizing a geo_distance() proximity query (example and benchmark)
2007-02-05T19:47:25Z Re: optimizing a geo_distance() proximity query
2007-02-03T19:00:26Z optimizing a geo_distance() proximity query
2007-02-01T14:10:09Z Using statement_timeout as a performance tool?
2005-09-23T21:42:02Z Re: suggestion: fix 'now' -> CURRENT_TIMESTAMP
2005-09-23T14:40:54Z suggestion: fix 'now' -> CURRENT_TIMESTAMP