Re: [HACKERS] RI status report #2 - Mailing list pgsql-hackers

From Lamar Owen
Subject Re: [HACKERS] RI status report #2
Date
Msg-id 37F385B9.91BDA5F8@wgcr.org
Whole thread Raw
In response to Re: [HACKERS] RI status report #2  (Bruce Momjian <maillist@candle.pha.pa.us>)
List pgsql-hackers
Bruce Momjian wrote:
> Lamr Owen wrote:
> > And that surprises you??  Even in the short two years I've used
> > PostgreSQL, I have grown accustomed to major changes every major
[snip]
> Yes, it still shocks me.  I was telling Thomas, every release I think,
> man, this is so great, no reason anyone should be using a prior release.
> And then the next release is the same thing.
> 
> The basic issue for me is that each of the new features requsted looks
> so hard, I can't imagine how it could be done, but by release time, it
> does get done.  Amazing.

I find the enthusiasm of this particular development quite infectious. 
While I'm only doing a very small part in packaging RPM's (thus far), I
feel quite good about it (it conjures back the same feeling that I had
at 15 years old when my Z80 disassembler first correctly disassembled
the opcodes of three-quarters of the instruction set -- no operands at
that time, but the opcode logic was WORKING... It felt uniquely
gratifying).  

Just reading the web page and the release notes doesn't do this
development justice -- until I subscribed to this hackers list, I had no
idea that PostgreSQL development was so dynamic.

This beats following the linux kernel development, IMO.

Lamar Owen
WGCR Internet Radio


pgsql-hackers by date:

Previous
From: wieck@debis.com (Jan Wieck)
Date:
Subject: RI status report #3
Next
From: Vince Vielhaber
Date:
Subject: RE: [HACKERS] Win32 pЭort of libpq