Re: [HACKERS] HISTORY file
S'alright, I can do the package together tomorrow morning to let you wrap up the loose ends :) On Tue, 3 Sep 2002, Bruce Momjian wrote: I am still working on the 7.3 HISTORY file. I have extracted the items, but I have to worksmith them and write an introduction. It is midnight here now. I don't think I can finish before ~3am and at that point, I am not sure I will know what I am writing. Basically, one day of feature freeze wasn't enough time for me to get this together. I could have worked on it earlier, but I didn't have time then either --- only the feature freeze has given me time to work on this. Should we ship beta1 without a HISTORY or delay one day? People should probably review this HISTORY file too, and there isn't time for that either unless we delay. If all our beta testers are on Hackers, I can post the list when I am done so you can package. I don't know of any other items holding up the packaging. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [HACKERS] HISTORY file
On Tue, 3 Sep 2002, Tom Lane wrote: Bruce Momjian [EMAIL PROTECTED] writes: Yes, I haven't gotten to the release checklist yet. Let's delay a day. Or at least late in the day tomorrow. I have some loose ends to clean up yet as well, but I'm beat and am going to bed. But I assume we are now officially in feature freeze, right? Yes, definitely ... and unless any of you have any showstoppers, I'll do the beta1 packaging first thing Wed morning instead of today ;); ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
[HACKERS] HISTORY file
I am still working on the 7.3 HISTORY file. I have extracted the items, but I have to worksmith them and write an introduction. It is midnight here now. I don't think I can finish before ~3am and at that point, I am not sure I will know what I am writing. Basically, one day of feature freeze wasn't enough time for me to get this together. I could have worked on it earlier, but I didn't have time then either --- only the feature freeze has given me time to work on this. Should we ship beta1 without a HISTORY or delay one day? People should probably review this HISTORY file too, and there isn't time for that either unless we delay. If all our beta testers are on Hackers, I can post the list when I am done so you can package. I don't know of any other items holding up the packaging. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] HISTORY file
Bruce Momjian [EMAIL PROTECTED] writes: I don't know of any other items holding up the packaging. Gotta brand the thing as 7.3beta1 not 7.3devel, no? regards, tom lane ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] HISTORY file
Tom Lane wrote: Bruce Momjian [EMAIL PROTECTED] writes: I don't know of any other items holding up the packaging. Gotta brand the thing as 7.3beta1 not 7.3devel, no? Yes, I haven't gotten to the release checklist yet. Let's delay a day. I have a 17k line log file down to 3.5k lines, but it will end up around ~250 lines. That will take some time. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] HISTORY file
Bruce Momjian [EMAIL PROTECTED] writes: Yes, I haven't gotten to the release checklist yet. Let's delay a day. Or at least late in the day tomorrow. I have some loose ends to clean up yet as well, but I'm beat and am going to bed. But I assume we are now officially in feature freeze, right? regards, tom lane ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
[HACKERS] HISTORY file
I find the HISTORY file to be distressingly poor to peruse. Reasons: A large proportion of the items don't convey any useful information. Examples: | PLpgSQL fix for SELECT... FOR UPDATE (Tom) What did this fix? Does SELECT FOR UDPATE now work whereas it didn't use to? = SELECT ... FOR UPDATE now works in PL/pgSQL | Fix for PL/pgSQL PERFORM returning multiple rows (Tom) What did this fix? Can you return multiple rows now or does it merely give an error message that you cannot where it used to crash? | Fix for inherited CHECK constraints (Stephan Szabo) ditto | PL/pgSQL Allow IS and FOR in cursors (Bruce) If I didn't happen to know exactly what this meant, I wouldn't have a clue. | Allow NULL to appear at beginning/end based on ORDER BY (Tom) It doesn't allow, it just does. | Pltcl add spi_lastoid capability ([EMAIL PROTECTED]) Capability = command, function, type, ...? | Allow column renaming in views ALTER VIEW foo RENAME COLUMN -- huh? | New option to output SET SESSION AUTHORIZATION commands (Peter E) Option to what to output where? | New postgresql.conf option to enable/disable col = NULL comparisons This is not correct. | Cachability fixes (Thomas, Tom) I don't think cachability as such was fixed, or even changed. The item probably related to some iscacheable pg_proc entries which were temporarily broken. The categories Bug Fixes, Enhancements, Types, Performance, Interfaces, Source Code could be split better, and they're not used very consistently. An example from each category that doesn't fit: Bug Fixes: Disallow access to pg_statistic for non-super user (Tom) This was not a bug, but a consequence of a change. Enhancements: Fix TCL COPY TO/FROM (ljb) If it is fixed then it was broken before. Types: New function bit_length() (Peter E) No comment. Performance: Dynahash portability improvements (Tom) Interfaces: Obviously, anything done in the interfaces is also either a bug fix or an enhancement. And what exactly constitutes an interface is not clear to me. Source code: Remove OID's from some system tables (Tom) Maybe this is an enhancement. Some changes are must know, because they are incompatible, such as | Load pg_hba.conf only on startup and SIGHUP (Bruce) This should be made clear somewhere. Finally, | Remove configure --enable-pltcl-utf option There was never such an option in a previous release. -- Peter Eisentraut [EMAIL PROTECTED] http://funkturm.homeip.net/~peter ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] HISTORY file
| Fix for inherited CHECK constraints (Stephan Szabo) ditto If this is what I think it is, I think the actual fix was the following (although I don't know what a particularly good wording is) ALTER TABLE ADD CONSTRAINT now properly adds check constraints to children of the specified table, which is consistant to the behavior of check constraints in inheritance trees created at create time. ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] HISTORY file
May be it's cosmetic, but: - Migration to 7.1 right is Migration to 7.2 Fixed. Be missing: - information that some parts of interface are translated to Swedish, Russian, French, Germany nad Czech. (IMHO right place for information about Peter's NLS support is Major changes in this release paragraph :-) Added to list of major features. - support for standard encoding names and multibyte code cleanup and performance improvement (Tatsuo's test look interesting:-) Is that major? - new to_char(interval, text) function Added to list. - locale bugfix (if is used glibc-2.2) in backend and ODBC(?) Too specific for list. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup.| Drexel Hill, Pennsylvania 19026 ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
[HACKERS] HISTORY file
May be it's cosmetic, but: - Migration to 7.1 right is Migration to 7.2 Be missing: - information that some parts of interface are translated to Swedish, Russian, French, Germany nad Czech. (IMHO right place for information about Peter's NLS support is Major changes in this release paragraph :-) - support for standard encoding names and multibyte code cleanup and performance improvement (Tatsuo's test look interesting:-) - new to_char(interval, text) function - locale bugfix (if is used glibc-2.2) in backend and ODBC(?) Karel PS. A lot of people search in HISTORY file inspiration for their application improvement and also here try search answer to question why dones't work it after update?. Found answer here is better than in in mailing lists:-) -- Karel Zak [EMAIL PROTECTED] http://home.zf.jcu.cz/~zakkr/ C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
