'client_min_messages' 设置如何影响使用 libpq 的应用程序？
How does 'client_min_messages' setting affect an application using libpq?
client_min_messages (enum)
Controls which message levels are sent to the client. Valid values are DEBUG5, DEBUG4, DEBUG3, DEBUG2, DEBUG1, LOG, NOTICE, WARNING, ERROR, FATAL, and PANIC. Each level includes all the levels that follow it. The later the level, the fewer messages are sent. The default is NOTICE. Note that LOG has a different rank here than in log_min_messages.
我假设这些 messages 与执行的命令的 results (PQResult) 不同。如果是这样，我如何通过 libpq 读取这些消息？这些 messages 会对应用程序的性能产生影响吗？
消息在 PostgreSQL 协议上作为不同的消息类型发送，通常与结果流交织在一起。 libpq 看到它们并将它们挑出来，然后将它们添加到您可以检查的通知队列中。
client_min_messages (enum)
Controls which message levels are sent to the client. Valid values are DEBUG5, DEBUG4, DEBUG3, DEBUG2, DEBUG1, LOG, NOTICE, WARNING, ERROR, FATAL, and PANIC. Each level includes all the levels that follow it. The later the level, the fewer messages are sent. The default is NOTICE. Note that LOG has a different rank here than in log_min_messages.
我假设这些 messages 与执行的命令的 results (PQResult) 不同。如果是这样，我如何通过 libpq 读取这些消息？这些 messages 会对应用程序的性能产生影响吗？
消息在 PostgreSQL 协议上作为不同的消息类型发送，通常与结果流交织在一起。 libpq 看到它们并将它们挑出来，然后将它们添加到您可以检查的通知队列中。