Filter:

Messages in week 24 (Jun 08 - Jun 14, 2015)

Threads40 messages
5Started
0Replied in own
35Replied to othersin 17 threads
Patchesof which 1 carried a patch
0New patchfirst in its thread
1Follow-uprevision of an earlier one
ActivityThreadSent
Replied (other)On columnar storageabout 11 years ago
Replied (other)[Proposal] Progress bar for pg_dump/pg_restoreabout 11 years ago
Replied (other)BUG #13437: Seq Scan increases heap_blks_read instead of heap_blks_hit when no disk is readabout 11 years ago
Replied (other)Entities created in one query not available in another in extended protocolabout 11 years ago
Replied (other)Comfortably check BackendPID with psqlabout 11 years ago
Replied (other)s_lock() seems too aggressive for machines with many socketsabout 11 years ago
Replied (other)s_lock() seems too aggressive for machines with many socketsabout 11 years ago
Replied (other)pg_basebackup and pg_stat_tmp directoryabout 11 years ago
Replied (other)Fix logical decoding sendtime updateabout 11 years ago
Replied (other)s_lock() seems too aggressive for machines with many socketsabout 11 years ago
Replied (other)s_lock() seems too aggressive for machines with many socketsabout 11 years ago
Replied (other)replication slot restart_lsn initializationabout 11 years ago
Replied (other)s_lock() seems too aggressive for machines with many socketsabout 11 years ago
Replied (other)s_lock() seems too aggressive for machines with many socketsabout 11 years ago
Replied (other)replication slot restart_lsn initializationabout 11 years ago
Replied (other)s_lock() seems too aggressive for machines with many socketsabout 11 years ago
Replied (other)s_lock() seems too aggressive for machines with many socketsabout 11 years ago
Replied (other)s_lock() seems too aggressive for machines with many socketsabout 11 years ago
Replied (other)s_lock() seems too aggressive for machines with many socketsabout 11 years ago
Replied (other)s_lock() seems too aggressive for machines with many socketsabout 11 years ago
Started threadMissing XLOG_DEBUG check in AdvanceXLInsertBuffer()?about 11 years ago
Replied (other)postpone next week's releaseabout 11 years ago
Replied (other)Checkpoints vs restartpointsabout 11 years ago
Replied (other)Draft release notes for 9.4.4 et alabout 11 years ago
Replied (other)"could not adopt C locale" failure at startup on Windowsabout 11 years ago
Replied (other)The Future of Aggregationabout 11 years ago
Replied (other)back-branch multixact fixes & 9.5 alpha/beta: scheduleabout 11 years ago
Replied (other)back-branch multixact fixes & 9.5 alpha/beta: scheduleabout 11 years ago
Replied (other)postpone next week's releaseabout 11 years ago
Replied (other)9.4.1 -> 9.4.2 problem: could not access status of transaction 1about 11 years ago
Replied (other)9.4.1 -> 9.4.2 problem: could not access status of transaction 1about 11 years ago
Replied (other)postpone next week's releaseabout 11 years ago
Replied (other)Follow-up patch9.4.1 -> 9.4.2 problem: could not access status of transaction 1about 11 years ago
Replied (other)bugfix: incomplete implementation of errhidecontextabout 11 years ago
Replied (other)9.4.1 -> 9.4.2 problem: could not access status of transaction 1about 11 years ago
Started threadpgsql: Allow HotStandbyActiveInReplay() to be called in single user modabout 11 years ago
Started threadpgsql: Allow HotStandbyActiveInReplay() to be called in single user modabout 11 years ago
Started threadpgsql: Allow HotStandbyActiveInReplay() to be called in single user modabout 11 years ago
Started threadpgsql: Allow HotStandbyActiveInReplay() to be called in single user modabout 11 years ago
Replied (other)9.4.1 -> 9.4.2 problem: could not access status of transaction 1about 11 years ago