Skip to navigation
Register for our live webinar on July 30: Optimizing Postgres with Claude Code and the pganalyze MCP Server.
pganalyze
  • Docs
  • Our Key Features
    Query AdvisorDetect and fix Postgres query plan problemsIndex AdvisorFaster queries, less guessworkVACUUM AdvisorOptimize bloat, freezing and VACUUM performanceWorkbooksDedicated environment for query optimization
    All features
  • Fix Slow QueriesEnterprise Scale
  • Pricing
  • Blog
  • WebinarseBooksToolsCustomer StoriesBlogNewsletter
  • About usCareers
  • Contact
LoginFree Trial
pganalyze
Docs
Query AdvisorDetect and fix Postgres query plan problemsIndex AdvisorFaster queries, less guessworkVACUUM AdvisorOptimize bloat, freezing and VACUUM performanceWorkbooksDedicated environment for query optimization
See all features
Fix Slow QueriesEnterprise Scale
PricingBlog
WebinarseBooksToolsCustomer StoriesBlogNewsletter
About usCareers
Contact
Free TrialLog in
    • Overview
    • Installation Guide
    • pganalyze Collector
    • Query Performance
    • Query Advisor
    • EXPLAIN Plans
    • Workbooks
    • Index Advisor
    • Indexing Engine
    • VACUUM Advisor
    • Schema Statistics
    • Log Insights
      • Overview
      • Tuning Log Config Settings
      • Limits
      • Classifications
        • Server
        • Connections
          • C20: Connection received
          • C21: Connection authorized
          • C22: Authentication failed
          • C23: Disconnection
          • C24: Client failed to connect
          • C25: Connection to client lost
          • C26: Connection with open transaction lost
          • C27: Terminating connection
          • C28: Too many connections
          • C29: Too many connections for role
          • C30: Could not accept SSL connection
          • C31: Unsupported frontend protocol
          • C32: Incomplete message from client
          • C33: Too many connections for database
        • WAL & Checkpoints
        • Autovacuum
        • Locks
        • Statements
        • Standby Servers
        • Constraint Violations
        • Application Errors
    • Connections
    • Alerts & Check-Up
    • Account Management
    • MCP Server (Preview)
    • OpenTelemetry Integration
    • pganalyze Enterprise Server
    • pganalyze GraphQL API
    • Open-Source Components
❮ Log Insights: Connections

C23: Disconnection

Work in Progress

This documentation page is currently being worked on. We apologize for the page being incomplete or not available yet.

Category: Connections
SQLSTATE: n/a
Urgency: low

Example Postgres Log Output:

LOG: disconnection: session time: 1:53:01.198 user=myuser database=mydb host=172.30.0.165 port=56902

Explanation:

…

Recommended Action:

…

Learn More:

No additional resources available.


Download Free eBook: The Top 6 Postgres Log Events
Couldn't find what you were looking for or want to talk about something specific?
Start a conversation with us →

Logo
  • Contact
  • Plans & Pricing
  • Resources
  • Enterprise
  • Documentation
  • Customer Stories
  • Careers
  • Index Advisor
  • Security
  • Status
  • Postgres Query Formatter
  • Compare pganalyze
  • Terms of Service
  • Privacy Policy
  • Newsletter
  • SOC 2 Type 2
  • Do Not Sell My Personal Information

Get in touch

Use the contact us form or email sales:
 sales@pganalyze.com

SOC 2 certification

pganalyze is SOC 2 Type 2 certified

pganalyze is SOC 2 Type 2 certified
© 2026 Duboce Labs, Inc.