33 messages8 people2 patchsets11 commitsApr 2018 - Apr 2019

23 Apr 20189 Apr 2019
Week of 23 Apr 2018
#1Tom LaneMon 23 Apr · 21:10#2Stephen FrostMon 23 Apr · 23:18#3Thomas MunroMon 23 Apr · 23:37#4Noah MischTue 24 Apr · 07:06#5Magnus Hagander↳ #2Tue 24 Apr · 07:18#6Craig RingerThu 26 Apr · 10:48#7Stephen Frost↳ #5Fri 27 Apr · 12:26
CommittedTry to get some info about Windows can't-reattach-to-shared-memory errors.Sat 28 Apr · 01:59
#8Tom Lane↳ #4Sat 28 Apr · 02:06#9Stephen FrostSat 28 Apr · 13:59
CommittedGet more info about Windows can't-reattach-to-shared-memory errors.Sun 29 Apr · 20:02
Week of 30 Apr 2018
CommittedGet still more info about Windows can't-reattach-to-shared-memory errors.Mon 30 Apr · 00:41
CommittedDump full memory maps around failing Windows reattach code.Mon 30 Apr · 15:16
#10Tom Lane↳ #4Mon 30 Apr · 17:07
CommittedRemove Windows module-list-dumping code.Mon 30 Apr · 17:20
#11Stephen FrostMon 30 Apr · 18:34#12Heath LordMon 30 Apr · 19:25#13Stephen FrostMon 30 Apr · 19:29#14Tom Lane↳ #12Mon 30 Apr · 19:45
CommittedFurther effort at preventing memory map dump from affecting the results.Mon 30 Apr · 20:19
CommittedMap and unmap the shared memory block before risking VirtualFree.Mon 30 Apr · 21:07
#15Tom Lane↳ #10Tue 1 May · 00:01
CommittedDoes it help to wait before reattaching?Tue 1 May · 00:09
#16Andres FreundTue 1 May · 00:24#17Noah Misch↳ #15Tue 1 May · 02:59#18Tom LaneTue 1 May · 03:33#19Thomas Munro↳ #17Tue 1 May · 03:52#20Tom Lane↳ #16Tue 1 May · 04:13#21Tom LaneTue 1 May · 15:31
CommittedRemove investigative code for can't-reattach-to-shared-memory errors.Tue 1 May · 17:06
Week of 1 Apr 2019
#29Noah Mischpatch↳ #25Tue 2 Apr · 13:54#30Tom LaneTue 2 Apr · 14:09
CommittedAssert that pgwin32_signal_initialize() has been called early enough.Thu 4 Apr · 00:11
#31Noah MischSun 7 Apr · 04:32#32Tom LaneSun 7 Apr · 04:43
Week of 8 Apr 2019
CommittedAvoid "could not reattach" by providing space for concurrent allocation.Tue 9 Apr · 04:39
#33Noah MischTue 9 Apr · 04:54