From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Neil Conway <neilc(at)samurai(dot)com>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, Ericson Smith <eric(at)did-it(dot)com>, Bruno Wolff III <bruno(at)wolff(dot)to>, Dmitry Tkach <dmitry(at)openratings(dot)com>, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: 7.4? |
Date: | 2003-03-06 18:10:34 |
Message-ID: | 200303061810.h26IAYI12650@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Yes, those are nice, but they aren't killer features like Win32 or PITR.
I was hoping for one or two killer features for 7.4.
Considering a feature freeze two weeks before beta, we are looking at
six weeks left. I don't know that I can do Win32 in six weeks. If we
go for June 1, we are looking at ten weeks.
Can I get comments from others?
---------------------------------------------------------------------------
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Tom Lane wrote:
> >> The problem there was not the feature freeze, it was that we kept
> >> slipping the beta date while we waited around for certain items
> >> to get done. The lesson I take away from the past couple releases
> >> is that you set a target beta date and then stick to it; features
> >> that aren't in on time don't get extensions.
>
> > OK, let's follow that logic. Do we have enough to justify a release
> > without any of those features? I don't think so.
>
> Sure we do. A quick scan of the CVS logs reminds me that we have
> already done a bunch of stuff:
>
> btree index space recycling
> free-space-map management improvements
> IN, NOT IN via hashtables and/or joins
> hash-based aggregation
> merge/hash on expressions more complex than simple Vars
> deduction of equality on expressions other than simple Vars
> hash joins can use more than one join key
> smarter planning of outer joins
> join syntax doesn't necessarily constrain plan
> smarter planning of nestloop inner indexscans with multiple outer relations
> new regex library
> domain CHECK constraints
> ALTER DOMAIN
> grant options, cascaded revoke
> print more information about deadlocks
> information schema
> read-only transactions
> first-class COALESCE and NULLIF constructs (no duplicate evaluation)
> IPv6 connections
> Simple SQL functions expand into inline expressions
> Eliminate memory leaks in SQL functions
> CLUSTER ALL
> transaction-safe TRUNCATE
> FOR EACH STATEMENT triggers
> ON COMMIT PRESERVE/DELETE ROWS for temp tables
>
> (plus lots more minor things) --- and we still have a couple months of
> development left. I don't see a good reason to delay releasing these
> features if other ones aren't ready.
>
> regards, tom lane
>
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Garo Hussenjian | 2003-03-06 18:17:21 | Re: Postgres and gdb: p debug_query_string RE: Query |
Previous Message | Tom Lane | 2003-03-06 18:05:51 | Re: 7.4? |