Re: [HACKERS] 6.6 items

From: Don Baccus <dhogaza(at)pacifier(dot)com>
To: Vadim Mikheev <vadim(at)krs(dot)ru>
Cc: ZEUGSWETTER Andreas IZ5 <Andreas(dot)Zeugswetter(at)telecom(dot)at>, pgsql-hackers(at)postgreSQL(dot)org, "'kar(at)webline(dot)dk'" <kar(at)webline(dot)dk>
Subject: Re: [HACKERS] 6.6 items
Date: 1999-06-08 14:32:41
Message-ID: 3.0.1.32.19990608073241.00e09f58@mail.pacifier.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At 10:11 PM 6/8/99 +0800, Vadim Mikheev wrote:

>We discussed this issue recently and decided to follow this way,
>so I didn't post message when pg_dump was changed, assuming
>that it's known by all -:)

I don't mean to this group, or any of the postgres groups,
I mean to the world at large, in which Postgres has a very
negative image for web work. Consistent dumps, killing
of one very bad memory leak (and a bunch of not-so-bad
ones), and moving to mvcc from table-locking - these are
three huge improvements for people building web sites.
Folks outside the normal Postgres community deserve to
know this.

And the latest download executes my "group by" clauses rather
than killing the backend, as I found out last night. I've
just sped up a page that returns a bar graph of monthly
data by an order of magnitude, woo-hoo! Before I was
forced to do a separate select for each month (against
about 100,000 records, boo-hiss), now one nice select
grouping data by month just like real databases let me
do, I'm happy!

- Don Baccus, Portland OR <dhogaza(at)pacifier(dot)com>
Nature photos, on-line guides, and other goodies at
http://donb.photo.net

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 1999-06-08 14:47:12 Re: [HACKERS] PL/Lang (was: Priorities for 6.6)
Previous Message Thomas Lockhart 1999-06-08 14:28:42 Re: [HACKERS] 6.6 items