Re: [PATCHES] Runtime.SGML diff ... please expedite!
Tom, > Ah, you are right. I had confused this with another option that I did > remove during 7.4 devel (fixbtree or something like that). Yeah, the > correct fix is to document it under Developer Options as > "LOG_BTREE_BUILD_STATS". OK, have another (replacement) patch, then. -- -Josh Berkus Aglio Database Solutions San Francisco ? runtime-sgml.patch Index: runtime.sgml === RCS file: /projects/cvsroot/pgsql-server/doc/src/sgml/runtime.sgml,v retrieving revision 1.187 diff -c -r1.187 runtime.sgml *** runtime.sgml 25 Jun 2003 01:13:24 - 1.187 --- runtime.sgml 25 Jun 2003 23:00:21 - *** *** 1394,1399 --- 1394,1475 + + Query and Index Statistics Collector + + + + STATS_START_COLLECTOR (boolean) + + + Controls whether the server should start the + statistics-collection subprocess. This is on by default, but + may be turned off if you know you have no interest in + collecting statistics. This option can only be set at server + start. + + + + + + STATS_COMMAND_STRING (boolean) + + + Enables the collection of statistics on the currently + executing command of each session, along with the time at + which that command began execution. This option is off by + default. Note that even when enabled, this information is not + visible to all users, only to superusers and the user owning + the session being reported on; so it should not represent a + security risk. This data can be accessed via the + pg_stat_activity system view; refer + to for more information. + + + + + + STATS_BLOCK_LEVEL (boolean) + STATS_ROW_LEVEL (boolean) + + + These enable the collection of block-level and row-level statistics + on database activity, respectively. These options are off by + default. This data can be accessed via the + pg_stat and + pg_statio family of system views; + refer to for more information. + + + + + + STATS_RESET_ON_SERVER_START (boolean) + + + If on, collected statistics are zeroed out whenever the server + is restarted. If off, statistics are accumulated across server + restarts. The default is on. This option can only be set at + server start. + + + + + + DEFAULT_STATISTICS_TARGET (integer) + + + Sets the default statistics target for table columns that have not + had a column-specific target set via ALTER TABLE SET + STATISTICS. Larger values increase the time needed to do + ANALYZE, but may improve the quality of the planner's + estimates. The default value is 10. + + + + + + Other Query Modifiers *** *** 1806,1811 --- 1882,1908 + + + Statistics Logging + + + + LOG_STATEMENT_STATS (boolean) + LOG_PARSER_STATS (boolean) + LOG_PLANNER_STATS (boolean) + LOG_EXECUTOR_STATS (boolean) + + + For each query, write performance statistics of the respective + module to the server log. This is a crude profiling + instrument. + + + + + + *** *** 2153,2259 - - Statistics - - - Statistics Monitoring - - - - LOG_STATEMENT_STATS (boolean) - LOG_PARSER_STATS (boolean) - LOG_PLANNER_STATS (boolean) - LOG_EXECUTOR_STATS (boolean) - - - For each query, write performance statistics of the respective - module to the server log. This is a crude profiling - instrument. - - - - - - DEFAULT_STATISTICS_TARGET (integer) - - - Sets the default statistics target for table columns that have not - had a column-specific target set via ALTER TABLE SET - STATISTICS. Larger values increase the time needed to do - ANALYZE, but may improve the quality of the planner's - estimates. The default value is 10. - - - - - - - - Query and Index Statistics Collector - - - - STATS_START_COLLECTOR (boolean) - - - Controls whether the server should start the - statistics-collection subprocess. This is on by default, but - may be turned off if you know you have no interest in - collecting statistics. This option can only be set at server - start. - - - - - - ST
Re: [PATCHES] Runtime.SGML diff ... please expedite!
Josh Berkus <[EMAIL PROTECTED]> writes: >> Also, one of the Red Hat guys pointed out to me that >> SHOW_BTREE_BUILD_STATS seems to have crept back into runtime.sgml, >> although it was removed during 7.4 development. Could we have that >> out of there in the next patch? > Accoring to GUC.c this morning, the option is still there ... it's just been > re-named to "LOG_BTREE_BUILD_STATS". Is this a mistake in GUC.c, or should > I put it back in Runtime.SGML under the new name? Ah, you are right. I had confused this with another option that I did remove during 7.4 devel (fixbtree or something like that). Yeah, the correct fix is to document it under Developer Options as "LOG_BTREE_BUILD_STATS". regards, tom lane ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [PATCHES] Runtime.SGML diff ... please expedite!
Tom, > Also, one of the Red Hat guys pointed out to me that > SHOW_BTREE_BUILD_STATS seems to have crept back into runtime.sgml, > although it was removed during 7.4 development. Could we have that > out of there in the next patch? Accoring to GUC.c this morning, the option is still there ... it's just been re-named to "LOG_BTREE_BUILD_STATS". Is this a mistake in GUC.c, or should I put it back in Runtime.SGML under the new name? -- -Josh Berkus Aglio Database Solutions San Francisco ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [PATCHES] Runtime.SGML diff ... please expedite!
Tom, OK, this is the checked-by-Rod patch, which should be perfect. -- -Josh Berkus Aglio Database Solutions San Francisco Index: runtime.sgml === RCS file: /projects/cvsroot/pgsql-server/doc/src/sgml/runtime.sgml,v retrieving revision 1.187 diff -c -r1.187 runtime.sgml *** runtime.sgml 25 Jun 2003 01:13:24 - 1.187 --- runtime.sgml 25 Jun 2003 22:28:29 - *** *** 1394,1399 --- 1394,1475 + + Query and Index Statistics Collector + + + + STATS_START_COLLECTOR (boolean) + + + Controls whether the server should start the + statistics-collection subprocess. This is on by default, but + may be turned off if you know you have no interest in + collecting statistics. This option can only be set at server + start. + + + + + + STATS_COMMAND_STRING (boolean) + + + Enables the collection of statistics on the currently + executing command of each session, along with the time at + which that command began execution. This option is off by + default. Note that even when enabled, this information is not + visible to all users, only to superusers and the user owning + the session being reported on; so it should not represent a + security risk. This data can be accessed via the + pg_stat_activity system view; refer + to for more information. + + + + + + STATS_BLOCK_LEVEL (boolean) + STATS_ROW_LEVEL (boolean) + + + These enable the collection of block-level and row-level statistics + on database activity, respectively. These options are off by + default. This data can be accessed via the + pg_stat and + pg_statio family of system views; + refer to for more information. + + + + + + STATS_RESET_ON_SERVER_START (boolean) + + + If on, collected statistics are zeroed out whenever the server + is restarted. If off, statistics are accumulated across server + restarts. The default is on. This option can only be set at + server start. + + + + + + DEFAULT_STATISTICS_TARGET (integer) + + + Sets the default statistics target for table columns that have not + had a column-specific target set via ALTER TABLE SET + STATISTICS. Larger values increase the time needed to do + ANALYZE, but may improve the quality of the planner's + estimates. The default value is 10. + + + + + + Other Query Modifiers *** *** 1806,1811 --- 1882,1908 + + + Statistics Logging + + + + LOG_STATEMENT_STATS (boolean) + LOG_PARSER_STATS (boolean) + LOG_PLANNER_STATS (boolean) + LOG_EXECUTOR_STATS (boolean) + + + For each query, write performance statistics of the respective + module to the server log. This is a crude profiling + instrument. + + + + + + *** *** 2153,2259 - - Statistics - - - Statistics Monitoring - - - - LOG_STATEMENT_STATS (boolean) - LOG_PARSER_STATS (boolean) - LOG_PLANNER_STATS (boolean) - LOG_EXECUTOR_STATS (boolean) - - - For each query, write performance statistics of the respective - module to the server log. This is a crude profiling - instrument. - - - - - - DEFAULT_STATISTICS_TARGET (integer) - - - Sets the default statistics target for table columns that have not - had a column-specific target set via ALTER TABLE SET - STATISTICS. Larger values increase the time needed to do - ANALYZE, but may improve the quality of the planner's - estimates. The default value is 10. - - - - - - - - Query and Index Statistics Collector - - - - STATS_START_COLLECTOR (boolean) - - - Controls whether the server should start the - statistics-collection subprocess. This is on by default, but - may be turned off if you know you have no interest in - collecting statistics. This option can only be set at server - start. - - - - - - STATS_COMMAND_STRING (boolean) - - - Enables the collection of statistics on the currently - executing command of each session, along with the time at - which that command began execution. This opt
Re: [PATCHES] Runtime.SGML diff ... please expedite!
Folks, Actually, I've just confirmed that that last patch has some syntax problems. So please ignore it. I will send a good patch through Rod to check. Sorry! I'll get the hang of this soon, really! -- -Josh Berkus Aglio Database Solutions San Francisco ---(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: [PATCHES] Runtime.SGML diff ... please expedite!
Guys, I've just discovered that I have some sort of library corruption on this laptop in my SGML libraries. So could someone check my SGML with a "make check" before applying that last patch? -- -Josh Berkus Aglio Database Solutions San Francisco ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [PATCHES] Runtime.SGML diff ... please expedite!
Tom, > It's gone. You might want to crosscheck the docs against the CVS-tip > version of guc.c ... Well, I did 2 weeks ago when I started this process. I'll do it again before beta. In the meantime, here's a new patch for runtime.sgml, based on today's CVS: 1) drops SHOW_BTREE 2) drops HAS_RENDEZVOUS 3) Folds the redundant "Statistics" section into Logging and Query Tuning, depending on the option. -- -Josh Berkus Aglio Database Solutions San Francisco ? runtime-sgml.patch Index: runtime.sgml === RCS file: /projects/cvsroot/pgsql-server/doc/src/sgml/runtime.sgml,v retrieving revision 1.187 diff -r1.187 runtime.sgml 1396a1397,1459 > > Query and Index Statistics Collector > > > > STATS_START_COLLECTOR (boolean) > > > Controls whether the server should start the > statistics-collection subprocess. This is on by default, but > may be turned off if you know you have no interest in > collecting statistics. This option can only be set at server > start. > > > > > > STATS_COMMAND_STRING (boolean) > > > Enables the collection of statistics on the currently > executing command of each session, along with the time at > which that command began execution. This option is off by > default. Note that even when enabled, this information is not > visible to all users, only to superusers and the user owning > the session being reported on; so it should not represent a > security risk. This data can be accessed via the > pg_stat_activity system view; refer > to for more information. > > > > > > STATS_BLOCK_LEVEL (boolean) > STATS_ROW_LEVEL (boolean) > > > These enable the collection of block-level and row-level statistics > on database activity, respectively. These options are off by > default. This data can be accessed via the > pg_stat and > pg_statio family of system views; > refer to for more information. > > > > > > STATS_RESET_ON_SERVER_START (boolean) > > > If on, collected statistics are zeroed out whenever the server > is restarted. If off, statistics are accumulated across server > restarts. The default is on. This option can only be set at > server start. > > > > > > 1808a1872,1905 > > > Statistics Logging > > > > LOG_STATEMENT_STATS (boolean) > LOG_PARSER_STATS (boolean) > LOG_PLANNER_STATS (boolean) > LOG_EXECUTOR_STATS (boolean) > > > For each query, write performance statistics of the respective > module to the server log. This is a crude profiling > instrument. > > > > > > DEFAULT_STATISTICS_TARGET (integer) > > > Sets the default statistics target for table columns that have not > had a column-specific target set via ALTER TABLE SET > STATISTICS. Larger values increase the time needed to do > ANALYZE, but may improve the quality of the planner's > estimates. The default value is 10. > > > > > > 2156,2189d2252 < < Statistics < < < Statistics Monitoring < < < < LOG_STATEMENT_STATS (boolean) < LOG_PARSER_STATS (boolean) < LOG_PLANNER_STATS (boolean) < LOG_EXECUTOR_STATS (boolean) < < < For each query, write performance statistics of the respective < module to the server log. This is a crude profiling < instrument. < < < < < < DEFAULT_STATISTICS_TARGET (integer) < < < Sets the default statistics target for table columns that have not < had a column-specific target set via ALTER TABLE SET < STATISTICS. Larger values increase the time needed to do < ANALYZE, but may improve the quality of the planner's < estimates. The default value is 10. < < < < 2191,2256d2253 < < < < Query and Index Statistics Collector < < < < STATS_START_COLLECTOR (boolean) < < < Controls whether the server should start the < statistics-collection subprocess. This is on by default, but < may be turned off if you know you have no interest in < collecting statistics. This option can only be set at server < start. < < < < < < STATS_COMMAND_STRING (boolean) < < < Enables the collection of statistics on the currently < executing command of each session, along with the time at <
Re: [PATCHES] Runtime.SGML diff ... please expedite!
Josh Berkus <[EMAIL PROTECTED]> writes: >> Also, one of the Red Hat guys pointed out to me that >> SHOW_BTREE_BUILD_STATS seems to have crept back into runtime.sgml, >> although it was removed during 7.4 development. Could we have that >> out of there in the next patch? > Will do. Is SHOW_BTREE gone, or is it just a "Source Developer Option"? It's gone. You might want to crosscheck the docs against the CVS-tip version of guc.c ... regards, tom lane ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [PATCHES] Runtime.SGML diff ... please expedite!
Tom, > It should be removed from runtime.sgml then. > > Also, one of the Red Hat guys pointed out to me that > SHOW_BTREE_BUILD_STATS seems to have crept back into runtime.sgml, > although it was removed during 7.4 development. Could we have that > out of there in the next patch? Will do. Is SHOW_BTREE gone, or is it just a "Source Developer Option"? -- -Josh Berkus Aglio Database Solutions San Francisco ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [PATCHES] Runtime.SGML diff ... please expedite!
Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > >> Is the HAS_RENDEZVOUS GUC still coming? Is there docs for it? > > > I haven't gotten to it --- it may have to wait for 7.5. > > It should be removed from runtime.sgml then. > > Also, one of the Red Hat guys pointed out to me that > SHOW_BTREE_BUILD_STATS seems to have crept back into runtime.sgml, > although it was removed during 7.4 development. Could we have that > out of there in the next patch? Not sure why Rendezvous is in runtime.sgml now --- it is needed only if you are doing two postmaster, and I will either do it for 7.4 or add it to TODO. -- 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 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [PATCHES] Runtime.SGML diff ... please expedite!
Bruce Momjian <[EMAIL PROTECTED]> writes: >> Is the HAS_RENDEZVOUS GUC still coming? Is there docs for it? > I haven't gotten to it --- it may have to wait for 7.5. It should be removed from runtime.sgml then. Also, one of the Red Hat guys pointed out to me that SHOW_BTREE_BUILD_STATS seems to have crept back into runtime.sgml, although it was removed during 7.4 development. Could we have that out of there in the next patch? 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: [PATCHES] Runtime.SGML diff ... please expedite!
Josh Berkus wrote: > Bruce, > > > Patch applied. Thanks. > > Great. 'cause I need to patch the patch, due to a cut-and-paste error. Next > patch coming Friday, much less extensive than this one. > > Is the HAS_RENDEZVOUS GUC still coming? Is there docs for it? I haven't gotten to it --- it may have to wait for 7.5. -- 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: [PATCHES] Runtime.SGML diff ... please expedite!
Tom, > (But if you are not happy with the current state of runtime.sgml, > we need fixes for that ASAP.) I just yesterday realized that the STATISTICS section could be profitably folded into LOGGING and QUERY TUNING. I will send a second patch tommorrow if possible. -- Josh Berkus Aglio Database Solutions San Francisco ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [PATCHES] Runtime.SGML diff ... please expedite!
Josh Berkus <[EMAIL PROTECTED]> writes: > Is the HAS_RENDEZVOUS GUC still coming? Is there docs for it? Don't worry about it. If it gets added, it will be the adder's responsibility to update the docs too. (But if you are not happy with the current state of runtime.sgml, we need fixes for that ASAP.) regards, tom lane ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [PATCHES] Runtime.SGML diff ... please expedite!
Bruce, > Patch applied. Thanks. Great. 'cause I need to patch the patch, due to a cut-and-paste error. Next patch coming Friday, much less extensive than this one. Is the HAS_RENDEZVOUS GUC still coming? Is there docs for it? -- Josh Berkus Aglio Database Solutions San Francisco ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [PATCHES] Runtime.SGML diff ... please expedite!
Patch applied. Thanks. --- Rod Taylor wrote: -- Start of PGP signed section. > This is the other portion he is referring to. > > client-auth.sgml references a renamed ID in runtime.sgml > > On Wed, 2003-06-18 at 16:46, Tom Lane wrote: > > Josh Berkus <[EMAIL PROTECTED]> writes: > > > Attached is the fully corrected version of the re-ording patch for=20 > > > Runtime.sgml and dependant files. > > > > Dependent files? I only see a diff for runtime.sgml there ... > > > > regards, tom lane > > > > ---(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 > -- > Rod Taylor <[EMAIL PROTECTED]> > > PGP Key: http://www.rbt.ca/rbtpub.asc [ Attachment, skipping... ] -- End of PGP section, PGP failed! -- 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 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [PATCHES] Runtime.SGML diff ... please expedite!
Patch applied. Thanks. --- Josh Berkus wrote: > Bruce, > > Attached is the fully corrected version of the re-ording patch for > Runtime.sgml and dependant files. > > Can you please expedite applying this? Since it involves a grand re-ordering > of the file, any successive changes to runtime.sgml need to be merged by > hand. > > To see what I'm getting at, the first draft (NOT the final version) of the > HTML version of the file is up at: > http://www.agliodbs.com/runtime/index.html > > Thanks! > > -- > -Josh Berkus > Aglio Database Solutions > San Francisco [ Attachment, skipping... ] > > ---(end of broadcast)--- > TIP 4: Don't 'kill -9' the postmaster -- 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: [PATCHES] Runtime.SGML diff ... please expedite!
Your patch has been added to the PostgreSQL unapplied patches list at: http://momjian.postgresql.org/cgi-bin/pgpatches I will try to apply it within the next 48 hours. --- Rod Taylor wrote: -- Start of PGP signed section. > This is the other portion he is referring to. > > client-auth.sgml references a renamed ID in runtime.sgml > > On Wed, 2003-06-18 at 16:46, Tom Lane wrote: > > Josh Berkus <[EMAIL PROTECTED]> writes: > > > Attached is the fully corrected version of the re-ording patch for=20 > > > Runtime.sgml and dependant files. > > > > Dependent files? I only see a diff for runtime.sgml there ... > > > > regards, tom lane > > > > ---(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 > -- > Rod Taylor <[EMAIL PROTECTED]> > > PGP Key: http://www.rbt.ca/rbtpub.asc [ Attachment, skipping... ] -- End of PGP section, PGP failed! -- 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 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [PATCHES] Runtime.SGML diff ... please expedite!
Your patch has been added to the PostgreSQL unapplied patches list at: http://momjian.postgresql.org/cgi-bin/pgpatches I will try to apply it within the next 48 hours. --- Josh Berkus wrote: > Bruce, > > Attached is the fully corrected version of the re-ording patch for > Runtime.sgml and dependant files. > > Can you please expedite applying this? Since it involves a grand re-ordering > of the file, any successive changes to runtime.sgml need to be merged by > hand. > > To see what I'm getting at, the first draft (NOT the final version) of the > HTML version of the file is up at: > http://www.agliodbs.com/runtime/index.html > > Thanks! > > -- > -Josh Berkus > Aglio Database Solutions > San Francisco [ Attachment, skipping... ] > > ---(end of broadcast)--- > TIP 4: Don't 'kill -9' the postmaster -- 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 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
