Re: [HACKERS] 7.4 status
While reviewing someone else's translation of pg_dump I noted that the phrase ACL list is used in a couple of places. However ACL stands for Access Control List, so the term ACL list seems redundant. Maybe it should be replaced with plain ACL? -- Alvaro Herrera (alvherre[a]dcc.uchile.cl) I think my standards have lowered enough that now I think 'good design' is when the page doesn't irritate the living f*ck out of me. (JWZ) ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] 7.4 status
Alvaro Herrera writes: While reviewing someone else's translation of pg_dump I noted that the phrase ACL list is used in a couple of places. However ACL stands for Access Control List, so the term ACL list seems redundant. These kinds of redundancies are pretty common for the sake of clarity and the flow of the language. Even major so-called Usage Panels accept them. The thing being parsed here is an array of datums of type aclitem, so the term ACL list is rather unclear anyway. But I hesitate to change it now because we wanted to call a string freeze. -- Peter Eisentraut [EMAIL PROTECTED] ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [HACKERS] 7.4 status
Alvaro Herrera writes: The only things left that I can see are #: commands/tablecmds.c:4093 msgid tables \%s\ already has a TOAST table tables - table Fixed. #: commands/user.c:651 commands/user.c:1357 msgid sysid %d is already assigned sysid - user ID? Not sure, maybe it can be a group ID. Changed to user ID and group ID. Sounds better to me too. -- Peter Eisentraut [EMAIL PROTECTED] ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [HACKERS] 7.4 status
Patrick Welche writes: Does this count a string change? :) Yes, but it's also a documentation bug fix. Anyway, you got it in before the freeze. :) -- Peter Eisentraut [EMAIL PROTECTED] ---(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] 7.4 status
On Mon, Sep 29, 2003 at 11:50:23PM +0200, Peter Eisentraut wrote:
Tom Lane writes:
At the very least we need to set a strings freeze soon, so the
translators can catch up. Peter, are you getting close to done with the
message revisions you've been making?
Yes, I think we're ready for a string freeze. Alvaro, do you have
anything you still want to submit in that area?
Does this count a string change? :)
Patrick
? psql
Index: help.c
===
RCS file: /projects/cvsroot/pgsql-server/src/bin/psql/help.c,v
retrieving revision 1.80
diff -u -r1.80 help.c
--- help.c 14 Sep 2003 22:37:13 - 1.80
+++ help.c 1 Oct 2003 19:58:15 -
@@ -234,8 +234,8 @@
ON(pset.popt.topt.format == PRINT_HTML));
fprintf(output, _( \\pset NAME [VALUE]\n
set table output option\n
- (NAME :=
{format|border|expanded|fieldsep|null|recordsep|\n
- tuples_only|title|tableattr|pager})\n));
+ (NAME :=
{format|border|expanded|fieldsep|footer|null|\n
+
recordsep|tuples_only|title|tableattr|pager})\n));
fprintf(output, _( \\t show only rows (currently %s)\n),
ON(pset.popt.topt.tuples_only));
fprintf(output, _( \\T [STRING]set HTML table tag attributes, or unset
if none\n));
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
Re: [HACKERS] 7.4 status
Bruce Momjian kirjutas T, 30.09.2003 kell 02:16: Tom Lane wrote: ! Faster regular expression code We could tout more functionality too, since the new regex package has a lot of advanced stuff that wasn't there before. Added more powerful This wording covers nicely possible incompatibilities too ;) -- Hannu ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] 7.4 status
Bruce Momjian [EMAIL PROTECTED] writes: Perhaps it is time to start looking at a final release date for 7.4? At the very least we need to set a strings freeze soon, so the translators can catch up. Peter, are you getting close to done with the message revisions you've been making? regards, tom lane ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [HACKERS] 7.4 status
Should we maybe get a Beta4 out now that everything is caught up code wise? Is anyone still sitting on something (other then the translations stuff) that should be in v7.4? On Mon, 29 Sep 2003, Tom Lane wrote: Bruce Momjian [EMAIL PROTECTED] writes: Perhaps it is time to start looking at a final release date for 7.4? At the very least we need to set a strings freeze soon, so the translators can catch up. Peter, are you getting close to done with the message revisions you've been making? regards, tom lane ---(end of broadcast)--- TIP 8: explain analyze is your friend ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [HACKERS] 7.4 status
Marc G. Fournier [EMAIL PROTECTED] writes: Should we maybe get a Beta4 out now that everything is caught up code wise? Is anyone still sitting on something (other then the translations stuff) that should be in v7.4? We still have several open items in Bruce's list, but maybe we can resolve them soon. Tentatively set a beta for Wed the 1st, maybe? 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])
Re: [HACKERS] 7.4 status
On Mon, 2003-09-29 at 14:57, Bruce Momjian wrote: I have emptied the patch queue, and have updated the HISTORY file for 7.4. I am looking for any improvements to that file. (I have to move it to SGML soon.) A patch that improves HISTORY is attached. I added a few bullet items to the highlights of this release section that are IMHO important, removed the mention of hash indexes (IMHO, they are still inappropriate for production use, just less so), fixed some spelling mistakes, and clarified a few entries. Please apply. -Neil Index: HISTORY === RCS file: /var/lib/cvs/pgsql-server/HISTORY,v retrieving revision 1.216 diff -c -r1.216 HISTORY *** HISTORY 29 Sep 2003 18:06:48 - 1.216 --- HISTORY 29 Sep 2003 20:26:57 - *** *** 15,52 Major changes in this release: IPv6 ! Full support for IPv6 connections and IPv6 data types. SSL ! Major SSL improvements in performance and security. Index Growth Prevention Allow free space map to efficiently reused empty index pages, ! and other free space improvements. New Client/Server Communication Protocol ! New protocol improves connection speed/reliability, and adds ! error codes, status information, a binary protocol, error ! reporting verbosity, and cleaner startup packets. Performance ! IN/NOT IN subqueries now perform as efficiently as joins ! Improved GROUP BY procesing by using hack buckets ! Hash indexes now have better concurrency/reliability/performance ! New multi-key hash join capability ! ANSI joins are now fully optimized ! Faster regular expression code !Cursors ! Allow cursors to exist outside transactions Threads ! libpq and ecpg are now fully thread-safe with --enable-thread-safety Contrib ! New version of full text indexing (tsearch2) ! New autovacuum tool ! Array handling has been improved and moved into the main server _ --- 15,57 Major changes in this release: IPv6 ! Full support for IPv6 connections and IPv6 address data types SSL ! Major improvements in SSL performance and security Index Growth Prevention Allow free space map to efficiently reused empty index pages, ! and other free space management improvements. ! !Standards Compliance ! Implement information schema ! Support for read-only transactions ! Make cursors comply more closely with the SQL standard New Client/Server Communication Protocol ! New protocol improves connection speed/reliability, and adds ! error codes, status information, a binary protocol, error ! reporting verbosity, and cleaner startup packets. Performance ! IN/NOT IN subqueries now perform as efficiently as joins ! Improved GROUP BY processing by using hash buckets ! New multi-key hash join capability ! ANSI joins are now fully optimized ! Faster regular expression code ! Function-inlining for simple SQL functions !Holdable Cursors ! Allow cursors to exist outside transactions Threads ! libpq and ecpg are now fully thread-safe with --enable-thread-safety Contrib ! New version of full text indexing (tsearch2) ! New autovacuum tool ! Array handling has been improved and moved into the main server _ *** *** 58,75 Observe the following incompatibilities: * The server-side autocommit setting was removed an reimplemented in client applications and languages. ! * Error message wording has changed dramtically in this release, and error codes have been added. * ANSI joins may behave differently because they are now fully optimized * A number of server variables have been renamed for clarity * MOVE/FETCH 0 now does nothing; return value of MOVE/FETCH 1/0 varies based on the current offset in the cursor ! * COPY now can process carriage-return/line-feed and carraige-return terminated files. Literal carriage-returns and line-feeds are no longer accepted as data values; use \r and \n instead. ! * Auto-trim spaces when converting from CHAR() to VARCHAR()/TEXT * FLOAT(p) now measures 'p' in bits, not digits * Date values now must match the ordering specified by DateStyle _ --- 63,83 Observe the following incompatibilities: * The
Re: [HACKERS] 7.4 status
Patch applied. Thanks. --- Neil Conway wrote: On Mon, 2003-09-29 at 14:57, Bruce Momjian wrote: I have emptied the patch queue, and have updated the HISTORY file for 7.4. I am looking for any improvements to that file. (I have to move it to SGML soon.) A patch that improves HISTORY is attached. I added a few bullet items to the highlights of this release section that are IMHO important, removed the mention of hash indexes (IMHO, they are still inappropriate for production use, just less so), fixed some spelling mistakes, and clarified a few entries. Please apply. -Neil [ Attachment, skipping... ] -- 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 8: explain analyze is your friend
Re: [HACKERS] 7.4 status
Tom Lane writes: At the very least we need to set a strings freeze soon, so the translators can catch up. Peter, are you getting close to done with the message revisions you've been making? Yes, I think we're ready for a string freeze. Alvaro, do you have anything you still want to submit in that area? -- Peter Eisentraut [EMAIL PROTECTED] ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] 7.4 status
On Mon, Sep 29, 2003 at 11:50:23PM +0200, Peter Eisentraut wrote: Tom Lane writes: At the very least we need to set a strings freeze soon, so the translators can catch up. Peter, are you getting close to done with the message revisions you've been making? Yes, I think we're ready for a string freeze. Alvaro, do you have anything you still want to submit in that area? The only things left that I can see are #: commands/tablecmds.c:4093 msgid tables \%s\ already has a TOAST table tables - table #: commands/user.c:651 commands/user.c:1357 msgid sysid %d is already assigned sysid - user ID? Not sure, maybe it can be a group ID. -- Alvaro Herrera (alvherre[a]dcc.uchile.cl) I think my standards have lowered enough that now I think 'good design' is when the page doesn't irritate the living f*ck out of me. (JWZ) ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [HACKERS] 7.4 status
Neil Conway [EMAIL PROTECTED] writes: SSL ! Major improvements in SSL performance and security Did we actually add any security to the SSL code? Performance and reliability, maybe, but I didn't think we'd done anything to the security algorithms per se. Did I miss something? Index Growth Prevention Allow free space map to efficiently reused empty index pages, ! and other free space management improvements. reused - reuse ! ANSI joins are now fully optimized better optimized maybe; I wouldn't say we're done with that issue yet. (In particular, I want to look into reordering outer joins sometime.) ! Faster regular expression code We could tout more functionality too, since the new regex package has a lot of advanced stuff that wasn't there before. * The server-side autocommit setting was removed an reimplemented in client applications and languages. an - and ! * Error message wording has changed dramatically in this release, and error codes have been added. Substantially might be a better term anyway? * ANSI joins may behave differently because they are now fully optimized See above * Date values now must match the ordering specified by DateStyle ... except that -MM-DD (with 3 or more digits for year) is always accepted. regards, tom lane ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] 7.4 status
Tom Lane wrote: Neil Conway [EMAIL PROTECTED] writes: SSL ! Major improvements in SSL performance and security Did we actually add any security to the SSL code? Performance and reliability, maybe, but I didn't think we'd done anything to the security algorithms per se. Did I miss something? I changed the wording to reliability. We did so some security by changing the rate of key negotiation, but it isn't substantial. Index Growth Prevention Allow free space map to efficiently reused empty index pages, ! and other free space management improvements. reused - reuse Done. ! ANSI joins are now fully optimized better optimized maybe; I wouldn't say we're done with that issue yet. (In particular, I want to look into reordering outer joins sometime.) Yep. ! Faster regular expression code We could tout more functionality too, since the new regex package has a lot of advanced stuff that wasn't there before. Added more powerful * The server-side autocommit setting was removed an reimplemented in client applications and languages. an - and Done. ! * Error message wording has changed dramatically in this release, and error codes have been added. Substantially might be a better term anyway? Yep. * ANSI joins may behave differently because they are now fully optimized See above Changed to better optimized * Date values now must match the ordering specified by DateStyle ... except that -MM-DD (with 3 or more digits for year) is always accepted. Changed to: * Ambiguous date values now must match the ordering specified by DateStyle Committed to CVS. -- 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
