Thread: Assimilation of these "versus" and hardware threads
All of these recent threads about fastest hardware and "who's better than who" has inspired me to create a new website: http://www.dbtuning.org I snipped a few bits from recent posts to get some pages started - hope the innocent don't mind. It's a bit postgres biased at the moment, since well, so am I (though FireBird is now mounting a strong showing...) This site uses a wiki so anyone interested can make contributions. We are all short on time, so I would love any help. I haven't entered any hardware info yet. I'll also take a minute to plug a postgres saavy open-source project used for this site - http://www.tikipro.org - It's a very flexible web framework with a very powerful and extendible CMS engine. It just hit Alpha 4, and we hope to go beta very soon. If you have feedback (or bugs), please send me a note. (and of course dbtuning is running on postgres ;-) [ \ / [ >X< Christian Fowler | spider AT viovio.com [ / \ http://www.viovio.com | http://www.tikipro.org
People: > All of these recent threads about fastest hardware and "who's better than > who" has inspired me to create a new website: > > http://www.dbtuning.org Well, time to plug my web site, too, I guess: http://www.powerpostgresql.com I've got a configuration primer up there, and the 8.0 Annotated .Conf file will be coming this week. That web site runs on Framewerk, a PostgreSQL-based CMS developed by our own Gavin Roy. -- --Josh Josh Berkus Aglio Database Solutions San Francisco ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo@postgresql.org so that your message can get through to the mailing list cleanly
Matt, > I had one comment on the pg_autovacuum section. Near the bottom it > lists some of it's limitations, and I want to clarify the 1st one: "Does > not reset the transaction counter". I assume this is talking about the > xid wraparound problem? If so, then that bullet can be removed. > pg_autovacuum does check for xid wraparound and perform a database wide > vacuum analyze when it's needed. Keen. That's an 8.0 fix? -- Josh Berkus Aglio Database Solutions San Francisco
Josh Berkus wrote: >Matt, > > >>I had one comment on the pg_autovacuum section. Near the bottom it >>lists some of it's limitations, and I want to clarify the 1st one: "Does >>not reset the transaction counter". I assume this is talking about the >>xid wraparound problem? If so, then that bullet can be removed. >>pg_autovacuum does check for xid wraparound and perform a database wide >>vacuum analyze when it's needed. >> >> > >Keen. That's an 8.0 fix? > Nope, been there since before 7.4 was released.
People: > All of these recent threads about fastest hardware and "who's better than > who" has inspired me to create a new website: > > http://www.dbtuning.org Well, time to plug my web site, too, I guess: http://www.powerpostgresql.com I've got a configuration primer up there, and the 8.0 Annotated .Conf file will be coming this week. That web site runs on Framewerk, a PostgreSQL-based CMS developed by our own Gavin Roy. -- --Josh Josh Berkus Aglio Database Solutions San Francisco ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo@postgresql.org so that your message can get through to the mailing list cleanly