Обсуждение: Release 8.2.0 done, 8.3 development starts
The 8.2.0 release went well. We spent a month more in beta than we planned, but that time helped to eliminate many bugs, and many that had existed in previous PostgreSQL major releases as well. We have had very few bug reports for 8.2.0, and will be doing a minor release in 1-2 weeks to get those fixes out to the user community. The development community is now focused on 8.3, and discussion and patch application has already started. This is scheduled to be a shorter release cycle then normal, with feature freeze on April 1, with major functionality discussed and hopefully reviewed by the community at least a month before that. This would put beta in mid-May, and final release perhaps mid-July. Of course, this all might change based on community feedback. -- Bruce Momjian bruce@momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
> The 8.2.0 release went well. We spent a month more in beta than we > planned, but that time helped to eliminate many bugs, and many that had > existed in previous PostgreSQL major releases as well. We have had very > few bug reports for 8.2.0, and will be doing a minor release in 1-2 > weeks to get those fixes out to the user community. any chance of having the win32 relation file permission bug looked at again for the minor release? this still worries us quite a bit here... best regards, thomas
I'm not sure, but as far as I remember, it will be a short release cycle for 8.3 in order to finish some big items that couldn't be ready in time for 8.2. But which items are more or less expected for 8.3? I recall - Hierarchical Queries - On disk bitmap index - Clustered/replication solutions being discussed. What are on people's minds? -- Med venlig hilsen Kaare Rasmussen, Jasonic Jasonic Telefon: +45 3816 2582 Nordre Fasanvej 12 2000 Frederiksberg Email: kaare@jasonic.dk
On Wed, Dec 20, 2006 at 05:49:15PM +0100, Kaare Rasmussen wrote: > I'm not sure, but as far as I remember, it will be a short release > cycle for 8.3 in order to finish some big items that couldn't be > ready in time for 8.2. > > But which items are more or less expected for 8.3? I recall > - Hierarchical Queries > - On disk bitmap index These two are happening > - Clustered/replication solutions This one's stalled because no two replication solutions appear to need anything in the core. Instead, lots of things are going on outside the core in the clustering/replication/HA arena. > being discussed. What are on people's minds? Other things coming down the pike are: * SQL/XML support per SQL:2003 * SQL/PSM support per SQL:2003 Hrm. While two things isn't much of a pattern, it's suggestive. Personally, I'd like to see MERGE, windowing functions, and better integration of (INSERT|UPDATE|DELETE) ... RETURNING. Cheers, D (SQL/MED, anybody?) -- David Fetter <david@fetter.org> http://fetter.org/ phone: +1 415 235 3778 AIM: dfetter666 Skype: davidfetter Remember to vote!
kaare@jasonic.dk (Kaare Rasmussen) writes: > I'm not sure, but as far as I remember, it will be a short release cycle for > 8.3 in order to finish some big items that couldn't be ready in time for 8.2. > > But which items are more or less expected for 8.3? I recall > - Hierarchical Queries > - On disk bitmap index > - Clustered/replication solutions > > being discussed. What are on people's minds? - WITH (recursive) queries - Better handling of partitioning - SQL:2003 windowing queries - Discussion is under way on improvements to autovac - Simon Riggs has "reuse of index tuples" under way -- let name="cbbrowne" and tld="acm.org" in name ^ "@" ^ tld;; http://linuxfinances.info/info/advocacy.html "I think there is a world market for maybe five computers" -- Tom Watson, CEO of IBM, 1943
Kaare Rasmussen wrote: > I'm not sure, but as far as I remember, it will be a short release cycle for > 8.3 in order to finish some big items that couldn't be ready in time for 8.2. > > But which items are more or less expected for 8.3? I recall > - Hierarchical Queries > - On disk bitmap index > - Clustered/replication solutions > > being discussed. What are on people's minds? > > Items on my personal agenda for this time frame - all have been previously discussed: . notification payload messages . fix permissions properly on custom GUC vars . create a mechanism for plperl to load modules safely I am committed to getting the first of these done to meet a businees need. The last two will be best effort. cheers andrew
Hi, I just collected all the items mentioned in this thread as well as what people quickly came up with on IRC and put it on a list in the developer wiki [1]. I tried to put names and links behind the items where ever possible. Let me know if there is something missing or if you know any other information (links, names) etc. that should be mentioned. The list is kinda scary long .. regards Lukas [1] http://developer.postgresql.org/index.php/Todo:WishlistFor83
Lukas Kahwe Smith wrote: > Hi, > > I just collected all the items mentioned in this thread as well as what > people quickly came up with on IRC and put it on a list in the developer > wiki [1]. I tried to put names and links behind the items where ever > possible. Let me know if there is something missing or if you know any > other information (links, names) etc. that should be mentioned. > > The list is kinda scary long .. > > regards > Lukas > > [1] http://developer.postgresql.org/index.php/Todo:WishlistFor83 That looks helpful. -- Bruce Momjian bruce@momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
On 12/20/06, Lukas Kahwe Smith <smith@pooteeweet.org> wrote: > wiki [1]. I tried to put names and links behind the items where ever > possible. Let me know if there is something missing or if you know any > other information (links, names) etc. that should be mentioned. I know Mark Cave-Ayland was interested in taking over hierarchical queries... let me see where he stands on it and whether he was going to complete it on an 8.3 deadline. If not, I'll do it. -- Jonah H. Harris, Software Architect | phone: 732.331.1324 EnterpriseDB Corporation | fax: 732.331.1301 33 Wood Ave S, 3rd Floor | jharris@enterprisedb.com Iselin, New Jersey 08830 | http://www.enterprisedb.com/
On Wed, Dec 20, 2006 at 17:49:15 +0100, Kaare Rasmussen <kaare@jasonic.dk> wrote: > I'm not sure, but as far as I remember, it will be a short release cycle for > 8.3 in order to finish some big items that couldn't be ready in time for 8.2. I believe the point of the short release cycle was more to change the timing of the release to avoid lots of people being on holiday during a critical period. After the short release cycle, the tentative plan was to go back to yearly releases shifted a few months from where they typically used to occur in the past. Whether or not this actually works out, remains to be seen.
On Wed, 20 Dec 2006 17:49:15 +0100, Kaare Rasmussen <kaare@jasonic.dk> wrote: > I'm not sure, but as far as I remember, it will be a short release cycle > for > 8.3 in order to finish some big items that couldn't be ready in time for > 8.2. > > But which items are more or less expected for 8.3? I recall > - Hierarchical Queries > - On disk bitmap index > - Clustered/replication solutions > > being discussed. What are on people's minds? > I still have updatable views on my radar. I'm currently out of office, but i'm preparing to put a project page into our wiki tomorrow, so people could get a slight overview about current implementation and open items. Bernd
Bruce Momjian wrote: >> [1] http://developer.postgresql.org/index.php/Todo:WishlistFor83 > > That looks helpful. Ok good :) Seriously though, please slap me when things are wrong, not assigned yet to the correct person .. there was a bit of guess work involved with some of the points .. especially with the names. I will let things sit like they are for 1-2 weeks and I will probably try to get a hold off each of the people still assigned to items then to confirm that they are actually targeting the feature for 8.3 .. or am I duplicating Bruce's efforts when I do this? regards, Lukas
Lukas Kahwe Smith wrote: > Bruce Momjian wrote: > >>> [1] http://developer.postgresql.org/index.php/Todo:WishlistFor83 >> >> That looks helpful. > > Ok good :) > > Seriously though, please slap me when things are wrong, not assigned > yet to the correct person .. there was a bit of guess work involved > with some of the points .. especially with the names. > > I will let things sit like they are for 1-2 weeks and I will probably > try to get a hold off each of the people still assigned to items then > to confirm that they are actually targeting the feature for 8.3 .. or > am I duplicating Bruce's efforts when I do this? > > To the best of my understanding, the current PSM effort is a pgFoundry project to create it as a loadable language. I am not aware of anything that would get it to where we could include it in 8.3, so this item should probably not be on the list. Also, "clustered/replication solutions" seems way too vague. It is not clear to me what if anything is in prospect on this front for 8.3. cheers andrew
Lukas Kahwe Smith wrote: > Bruce Momjian wrote: > > >> [1] http://developer.postgresql.org/index.php/Todo:WishlistFor83 > > > > That looks helpful. > > Ok good :) > > Seriously though, please slap me when things are wrong, not assigned yet > to the correct person .. there was a bit of guess work involved with > some of the points .. especially with the names. > > I will let things sit like they are for 1-2 weeks and I will probably > try to get a hold off each of the people still assigned to items then to > confirm that they are actually targeting the feature for 8.3 .. or am I > duplicating Bruce's efforts when I do this? What I did for the 8.2 open items tracking during feature freeze was to list the item description, status, and person's name and email in a table that could be easily reviewed. Let me know if you need help setting that up. -- Bruce Momjian bruce@momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +