| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
| Cc: | Postgres Hackers List <hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [HACKERS] Features for next release |
| Date: | 1999-10-08 23:14:24 |
| Message-ID: | 5156.939424464@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
It seems people are thinking winter or early spring (northern hemisphere
that is ;-)) for the next major release, and by then I think there will
be enough cool stuff done that we can call it 7.0. The only really big
to-do item that no one seems to be committed to doing in this cycle is
tuples bigger than a disk block, and maybe once the dust settles for
long queries someone will feel like tackling that...
I have another reason for calling it 7.0, which is that if we fix
the function-call interface the way I want to, we will break existing
user-written loadable modules that contain C-language functions.
Better to do that in a "7.0" than in a "6.6", no?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 1999-10-09 01:34:43 | Re: [HACKERS] Re: [GENERAL] Re: [PHP3] Re: PostgreSQL vs Mysql comparison |
| Previous Message | Tom Lane | 1999-10-08 22:53:18 | Re: [HACKERS] Re: [GENERAL] Re: [PHP3] Re: PostgreSQL vs Mysql comparison |