/22/2003/,
were there some places that could be improved? Could you give some suggestions?
Thank you!
Best regards,
--
Chengchao Yu
Software Engineer | Microsoft | Azure Database for PostgreSQL
https://azure.microsoft.com/en-us/services/postgresql/
-Original Message-
From: Chengchao Yu
rongly registered the
additional callback.
3. Calling LWLockReleaseAll() for the second time is quite fast, it will
not bring overburden to AtProcExit_Buffers()
Thus, I have updated the patch v3 according to your suggestions. Could you help
to review again?
Please let me know should you have
* Backend-shutdown callback. Do cleanup that we want to be sure happens
* before all the supporting modules begin to nail their doors shut via
The fix proposal is also attached to this email in file "fix-deadlock.patch".
Please let us know should you have suggestions on this issue and the fix.
Thank you!
Best regards,
--
Chengchao Yu
Software Engineer | Microsoft | Azure Database for PostgreSQL
https://azure.microsoft.com/en-us/services/postgresql/
emulate-error.patch
Description: emulate-error.patch
fix-deadlock.patch
Description: fix-deadlock.patch
0 0004`80f51df3 postgres!main+0x491
[d:\orcasqlagsea10\14\s\src\backend\main\main.c @ 235]
Please let us know should you have more feedbacks. Thank you!
Best regards,
--
Chengchao Yu
Software Engineer | Microsoft | Azure Database for PostgreSQL
https://azure.microsoft.com/en-us/services
Thank you so much Amit! I have created the patch below:
https://commitfest.postgresql.org/22/2003/
Please let me know should you have more suggestions. Thank you!
Best regards,
--
Chengchao Yu
Software Engineer | Microsoft | Azure Database for PostgreSQL
https://azure.microsoft.com/en-us
Greetings,
Just would like to follow up this issue and fix proposal. We really would like
to have this issue fixed in PG. Could someone give some suggestions to the fix
proposal? Or other ideas to fix this issue?
Looking forward for your feedbacks!
Best regards,
--
Chengchao Yu
Software
Greetings,
Happy new year!
We would like to follow up again for this issue and fix proposal. Could someone
give some suggestions to the fix proposal? Or other ideas to fix this issue?
Looking forward to your feedbacks!
Best regards,
--
Chengchao Yu
Software Engineer | Microsoft | Azure