wishlist：动态日志音量控制 [英] wishlist: dynamic log volume control
问题描述
我们通过记录每个SQL语句，持续时间等来提取很多价值，
用于调试，故障排除，监控等等。但我们有一个
似乎总是碰到磁盘I / O的集群数量
瓶颈。系统运行速度为100 QPS时，我们倾向于安静地记录
日志记录，并且只根据需要将其打开（根据定义，它将会同时显示为b
安静了）。但是很多这些生产集群都不容易重新启动;客户必须得到通知等。它会很好。如果我们
可以动态调整日志记录量（即关闭语句
日志记录等）而无需重启服务器......
---------------------------（播出结束）-------------- -------------
提示4：不要杀了-9''邮政局长
We extract great value from logging every SQL statement, its duration, etc.,
in service to debugging, troubleshooting, monitoring, etc. But we have a
number of clusters that seem to always be bumping into disk I/O
bottlenecks. With a system running at 100 QPS, we''re inclined to quiet the
logging and only turn it up as needed (which will, by definition, be while
it was quieted). But many of these production clusters are not easily
restarted; the customer has to be notified, etc. "It''d be nice" if we
could adjust the volume of logging dynamically (i.e., turn-off of statement
logging, etc) without have to restart the server...
---------------------------(end of broadcast)---------------------------
TIP 4: Don''t ''kill -9'' the postmaster
推荐答案
2004年2月18日星期三下午03:54:39 -0700，Ed L.写道：
On Wed, Feb 18, 2004 at 03:54:39PM -0700, Ed L. wrote:
我们从记录每个SQL语句，它的持续时间等，用于调试，故障排除，监控等。但是我们有一些似乎总是碰到磁盘I / O的集群。瓶颈。系统运行速度为100 QPS时，我们倾向于安静地记录
日志，并且只根据需要将其打开（根据定义，这将是安静的时候）。但是很多这些生产集群都不容易重新启动;客户必须得到通知等。它会很好。如果我们可以动态调整日志记录量（即关闭语句记录等）而无需重启服务器...
在任何特定的会话中，你可以做SET log_statement = off或者其他一些。
这样你就可以让日志变得更细。
-
Martijn van Oosterhout< kl ***** @ svana.org> http://svana.org/kleptog/ 如果天主教会能够在印刷机上生存下去，科幻小说
肯定会迎合bookwarez的出现。
http：/ /craphound.com/ebooksneitherenorbooks.txt - Cory Doctorow
We extract great value from logging every SQL statement, its duration, etc.,
in service to debugging, troubleshooting, monitoring, etc. But we have a
number of clusters that seem to always be bumping into disk I/O
bottlenecks. With a system running at 100 QPS, we''re inclined to quiet the
logging and only turn it up as needed (which will, by definition, be while
it was quieted). But many of these production clusters are not easily
restarted; the customer has to be notified, etc. "It''d be nice" if we
could adjust the volume of logging dynamically (i.e., turn-off of statement
logging, etc) without have to restart the server...
In any particular session you can do SET log_statement = off or some such.
That way you can make logging more fine grained.
--
Martijn van Oosterhout <kl*****@svana.org> http://svana.org/kleptog/ If the Catholic church can survive the printing press, science fiction
will certainly weather the advent of bookwarez.
http://craphound.com/ebooksneitherenorbooks.txt - Cory Doctorow
----- BEGIN PGP SIGNATURE -----
版本：GnuPG v1.0.6（GNU / Linux）
评论：有关信息，请参阅 http://www.gnupg.org
iD8DBQFAM / IWY5Twig3Ge + YRAglXAKDEOF4T5ur1i5CU4 / pvStnOTfdivwCfdUlk
QkeX9bhH1BemN / yRK6 + m8wQ =
= KI / R
-----结束PGP签名-----
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQFAM/IWY5Twig3Ge+YRAglXAKDEOF4T5ur1i5CU4/pvStnOTfdivwCfdUlk
QkeX9bhH1BemN/yRK6+m8wQ=
=KI/R
-----END PGP SIGNATURE-----
Martijn van Oosterhout写道：
- 开始PGP签名部分。
Martijn van Oosterhout wrote:
-- Start of PGP signed section.
2004年2月18日星期三，03：54：39 PM -0700，Ed L.写道：
On Wed, Feb 18, 2004 at 03:54:39PM -0700, Ed L. wrote:
我们通过记录每个SQL语句，它的持续时间等来提取很多价值，
服务于调试，故障排除，监控等。但我们有一个
号码群集似乎总是碰到磁盘I / O瓶颈。系统运行速度为100 QPS时，我们倾向于安静地记录
日志，并且只根据需要将其打开（根据定义，这将是安静的时候）。但是很多这些生产集群都不容易重新启动;客户必须得到通知等。它会很好。如果我们可以动态调整日志记录量（即关闭语句记录等）而无需重启服务器......
We extract great value from logging every SQL statement, its duration, etc.,
in service to debugging, troubleshooting, monitoring, etc. But we have a
number of clusters that seem to always be bumping into disk I/O
bottlenecks. With a system running at 100 QPS, we''re inclined to quiet the
logging and only turn it up as needed (which will, by definition, be while
it was quieted). But many of these production clusters are not easily
restarted; the customer has to be notified, etc. "It''d be nice" if we
could adjust the volume of logging dynamically (i.e., turn-off of statement
logging, etc) without have to restart the server...
在任何特定的会话中，你可以做SET log_statement = off或者其他一些。
这样你就可以让日志更精细。
In any particular session you can do SET log_statement = off or some such.
That way you can make logging more fine grained.
您也可以更改postgresql.conf文件和SIGHUP postmaster
让它生效。它没有重新启动服务器。
-
Bruce Momjian | http://candle.pha.pa.us
pg *** @ candle.pha.pa.us | （610）359-1001
+如果你的生活是硬盘，|罗伯茨路13号
+基督可以成为你的备份。 |宾夕法尼亚州新城广场19073年
---------------------------（播出结束） - --------------------------
提示1：订阅和取消订阅命令转到 ma ******* @ postgresql.org
You can also change the postgresql.conf file and SIGHUP the postmaster
for it to take affect. It doesn''t restart the server.
--
Bruce Momjian | http://candle.pha.pa.us
pg***@candle.pha.pa.us | (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 ma*******@postgresql.org
On 2004年2月18日星期三7:13，Bruce Momjian写道：
On Wednesday February 18 2004 7:13, Bruce Momjian wrote:
Martijn van Oosterhout写道：
- 开始PGP签名部分。
Martijn van Oosterhout wrote:
-- Start of PGP signed section.
On 2004年2月18日星期三03:54:39 PM -0700，Ed L.写道：
On Wed, Feb 18, 2004 at 03:54:39PM -0700, Ed L. wrote:
我们通过记录每个SQL语句，它的
持续时间等，在服务中提取很大的价值调试，故障排除，监控，等等。但是我们有许多集群似乎总是碰到磁盘I / O瓶颈。系统运行速度为100 QPS时，我们倾向于安静记录，只能根据需要将其打开（根据定义，它将在安静时进行）。但是很多这些生产集群都不容易重启;客户必须得到通知等等。它会很好。如果我们可以动态调整日志记录量（即关闭语句记录等），而不必重新启动服务器......
We extract great value from logging every SQL statement, its
duration, etc., in service to debugging, troubleshooting, monitoring,
etc. But we have a number of clusters that seem to always be bumping
into disk I/O bottlenecks. With a system running at 100 QPS, we''re
inclined to quiet the logging and only turn it up as needed (which
will, by definition, be while it was quieted). But many of these
production clusters are not easily restarted; the customer has to be
notified, etc. "It''d be nice" if we could adjust the volume of
logging dynamically (i.e., turn-off of statement logging, etc)
without have to restart the server...
在任何特定的会话中，您可以执行SET log_statement = off或某些
等。通过这种方式，您可以使日志记录更加精细。
In any particular session you can do SET log_statement = off or some
such. That way you can make logging more fine grained.
您还可以更改postgresql.conf文件并使邮件管理员更新SIGHUP以使其生效。它没有重新启动服务器。
You can also change the postgresql.conf file and SIGHUP the postmaster
for it to take affect. It doesn''t restart the server.
非常快速的编码，简单的补丁分发。 ;-)
Thx。
------------------------- - （广播结束）---------------------------
提示9：规划人员会忽略你的如果您的
加入列的数据类型不匹配，则希望选择索引扫描
Very fast coding, and simply amazing patch distribution. ;-)
Thx.
---------------------------(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
这篇关于wishlist：动态日志音量控制的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
