Filter:

Activity

2026202520242023202220212020201920182017201620152014201320122011201020092008
DecJanFebMarAprMayJunJulAugSepOctNovDec
Wk1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253
Mon
Tue
Wed
Thu
Fri
Sat
Sun

Messages on June 17, 2020

Threads16 messages
9Started
1Replied in own
6Replied to othersin 6 threads
Patchesnone in this period
0New patchfirst in its thread
0Follow-uprevision of an earlier one
ActivityThreadSent
Started threadpgsql: spinlock emulation: Fix bug when more than INT_MAX spinlocks areabout 6 years ago
Started threadpgsql: spinlock emulation: Fix bug when more than INT_MAX spinlocks areabout 6 years ago
Started threadpgsql: spinlock emulation: Fix bug when more than INT_MAX spinlocks areabout 6 years ago
Started threadpgsql: spinlock emulation: Fix bug when more than INT_MAX spinlocks areabout 6 years ago
Started threadpgsql: spinlock emulation: Fix bug when more than INT_MAX spinlocks areabout 6 years ago
Started threadpgsql: spinlock emulation: Fix bug when more than INT_MAX spinlocks areabout 6 years ago
Started threadpgsql: spinlock emulation: Fix bug when more than INT_MAX spinlocks areabout 6 years ago
Started threadpgsql: Avoid potential spinlock in a signal handler as part of global babout 6 years ago
Started threadpgsql: Avoid potential spinlock in a signal handler as part of global babout 6 years ago
Replied (other)Binary transfer vs Text transferabout 6 years ago
Replied (other)Atomic operations within spinlocksabout 6 years ago
Replied (own)language cleanups in code and docsabout 6 years ago
Replied (other)[patch] demoteabout 6 years ago
Replied (other)[Patch] ALTER SYSTEM READ ONLYabout 6 years ago
Replied (other)valgrind versus pg_atomic_init()about 6 years ago
Replied (other)elog(DEBUG2 in SpinLocked section.about 6 years ago