PostgreSQL

For PostgreSQL, the useful incident signal is usually query order, duration, and enough statement context to distinguish the failing path from surrounding traffic.

Capture is strongest when:

• the client is created after SDK initialization
• query text is stable enough to be recognizable
• sensitive parameters are scrubbed or omitted

Use query summaries if raw SQL would leak tenant or user data into the package.