Hackorum
Menu
Theme
Topics
Search
Statistics
Reports
Help
Sign in
Register
PostgreSQL Hackers Archive
Topics
Search
Reports
Sign in
Register
Statistics
Help
Sign in
Register
Filter:
Started threads
Replied (own)
Replied (other)
Sent first patch
Sent follow-up patch
Activity
2026
2025
2024
2023
2022
2021
2020
2019
2018
2017
2016
2015
2014
2013
2012
2011
2010
2009
2008
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
Wk
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
Mon
Tue
Wed
Thu
Fri
Sat
Sun
Messages on June 22, 2017
Threads
13
messages
1
Started
1
Replied in own
11
Replied to others
in 6 threads
Patches
of which
1
carried a patch
0
New patch
first in its thread
1
Follow-up
revision of an earlier one
Activity
Thread
Sent
Started thread
Dynamic instrumentation of lwlock wait times (lwlock flamegraphs)
about 9 years ago
Replied (other)
possible self-deadlock window after bad ProcessStartupPacket
about 9 years ago
Replied (other)
possible self-deadlock window after bad ProcessStartupPacket
about 9 years ago
Replied (own)
Fast promotion not used when doing a recovery_target PITR restore?
about 9 years ago
Replied (other)
pglogical vs. built-in logical replication in pg-10
about 9 years ago
Replied (other)
pglogical vs. built-in logical replication in pg-10
about 9 years ago
Replied (other)
lseek/read/write overhead becomes visible at scale ..
about 9 years ago
Replied (other)
PATCH: Batch/pipelining support for libpq
about 9 years ago
Replied (other)
pg_terminate_backend can terminate background workers and autovacuum launchers
about 9 years ago
Replied (other)
An attempt to reduce WALWriteLock contention
about 9 years ago
Replied (other)
Follow-up patch
PATCH: Batch/pipelining support for libpq
about 9 years ago
Replied (other)
PATCH: Batch/pipelining support for libpq
about 9 years ago
Replied (other)
PATCH: Batch/pipelining support for libpq
about 9 years ago