-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, 27 Nov 2007 17:32:49 +0000
Simon Riggs <simon@2ndquadrant.com> wrote:
> Maybe we should give each Beta a name, such as "Initial Beta",
> "Performance Beta", "Usability Beta" as a way of encouraging folk to
> focus onto particular aspects of quality at what we consider to be
> appropriate times to do so. Not sure whether thats a good idea, but
> I'd love to hear about ways to include performance as one of the
> essential behaviours of PostgreSQL.
>
> Your thoughts are welcome,
Well I think that we do take performance into account. I agree
that we should *never* have a regression in performance from release
to release, which is what I believe has inspired this thread.
However if you look at a lot of the items that have gone into this
release they were all about performance:
HOT -- has a direct correlation to performance because without it
we vacuum more. Not only more, but in a lot of cases it resolves a
serious PostgreSQL limitation for high velocity tables.
Phantom Xid - less vacuuming
The sequential scan thing Jeff Davis did
The reduced size of the tuple headers
Sincerely,
Joshua D. Drake
- --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com/ UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHTF0XATb/zqfZUUQRAul2AKCfKToFWWkdNWYZTCLmjJJeDQpysQCfTKnI
kURZp3SdAoyRLScxG5PizDo=
=PTcF
-----END PGP SIGNATURE-----
