Filter:

Messages in week 15 (Apr 09 - Apr 15, 2018)

Threads41 messages
0Started
0Replied in own
41Replied to othersin 19 threads
Patchesnone in this period
0New patchfirst in its thread
0Follow-uprevision of an earlier one
ActivityThreadSent
Replied (other)Proposal: Adding json loggingover 8 years ago
Replied (other)Proposal: Adding json loggingover 8 years ago
Replied (other)Setting rpath on llvmjit.so?over 8 years ago
Replied (other)Setting rpath on llvmjit.so?over 8 years ago
Replied (other)Proposal: Adding json loggingover 8 years ago
Replied (other)Setting rpath on llvmjit.so?over 8 years ago
Replied (other)crash with sql language partition support functionover 8 years ago
Replied (other)Postgres stucks in deadlock detectionover 8 years ago
Replied (other)Postgres stucks in deadlock detectionover 8 years ago
Replied (other)Make description of heap records more talkative for flagsover 8 years ago
Replied (other)wal_consistency_checking reports an inconsistency on master branchover 8 years ago
Replied (other)submake-errcodesover 8 years ago
Replied (other)Creation of wiki page for open items of v11over 8 years ago
Replied (other)relispartition for index partitionsover 8 years ago
Replied (other)pgsql: Fix interference between cavering indexes and partitioned tablesover 8 years ago
Replied (other)missing support of named convention for proceduresover 8 years ago
Replied (other)es_query_dsa is brokenover 8 years ago
Replied (other)WARNING in parallel index creation.over 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)ERROR: found multixact from before relminmxidover 8 years ago
Replied (other)PATCH: Keep one postmaster monitoring pipe per processover 8 years ago
Replied (other)PATCH: Keep one postmaster monitoring pipe per processover 8 years ago
Replied (other)ERROR: found multixact from before relminmxidover 8 years ago
Replied (other)ERROR: found multixact from before relminmxidover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)Excessive PostmasterIsAlive calls slow down WAL redoover 8 years ago
Replied (other)Excessive PostmasterIsAlive calls slow down WAL redoover 8 years ago
Replied (other)Excessive PostmasterIsAlive calls slow down WAL redoover 8 years ago
Replied (other)Excessive PostmasterIsAlive calls slow down WAL redoover 8 years ago
Replied (other)Optional message to user when terminating/cancelling backendover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)Verbosity of genbki.plover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago