)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":28691,"name":"Bo Tran","email":"ministry.96.nd@gmail.com","username":"ministry"},"change_message_id":"70d8f0055fd149000210e8d0c961d72a8a3db520","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"138b4558_ed3d12ec","updated":"2025-02-25 09:28:20.000000000","message":"Can you reference with this patch: https://review.opendev.org/c/openstack/trove/+/925054\n\nI think we shouldn\u0027t comment this option because it\u0027s will break this compatible with old version, that can\u0027t upgrade database version.","commit_id":"ee59fd2fbe6261f1dbf71542f7cab1bb01247810"},{"author":{"_account_id":37598,"name":"Ivan Anfimov","display_name":"Ivan Anfimov","email":"lazekteam@gmail.com","username":"anfimovir"},"change_message_id":"3bd89f01100c3015b2105a81cb92a37bc3385338","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"f6a0d1af_c32869d2","in_reply_to":"138b4558_ed3d12ec","updated":"2025-02-25 09:31:54.000000000","message":"@ministry.96.nd@gmail.com\n\nHello,\n\nPostgreSQL 12 reached its End of Life (EOL) on November 14, 2024.\n\nI don\u0027t think we should provide support for legacy software.","commit_id":"ee59fd2fbe6261f1dbf71542f7cab1bb01247810"},{"author":{"_account_id":28619,"name":"Dmitriy Rabotyagov","email":"noonedeadpunk@gmail.com","username":"noonedeadpunk"},"change_message_id":"848f9d3e6496361c7f23b3fef8adba34f40aaf5f","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"6999abe5_872e3bc1","in_reply_to":"41d43eca_c51476d1","updated":"2025-02-26 16:54:55.000000000","message":"Ok, yeah, I agree that it worth to be more flexible. Eventually that was a very fast patch I made without deep thinking about it.\n\nBut I also don\u0027t like approach of https://review.opendev.org/c/openstack/trove/+/925054 as it would require too much maintenance.\n\nI think reasonable middle ground between our approaches would be passing a version to the template (I don\u0027t know - maybe it\u0027s already available there), and then compare version inside of the template.\n\nThis would minimize maintenance efforts and provide flexability which is required to support different versions.","commit_id":"ee59fd2fbe6261f1dbf71542f7cab1bb01247810"},{"author":{"_account_id":28691,"name":"Bo Tran","email":"ministry.96.nd@gmail.com","username":"ministry"},"change_message_id":"bcf96e672af75199e828b0c4ecf779ecb0082919","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"41d43eca_c51476d1","in_reply_to":"f6a0d1af_c32869d2","updated":"2025-02-26 01:26:13.000000000","message":"of course, but I don\u0027t think someone else can upgrade version of database in product environment, this isn\u0027t simple and it\u0027s requirements of softwares that they running.\n\nWe need make flexible to can run in more environments.","commit_id":"ee59fd2fbe6261f1dbf71542f7cab1bb01247810"}]}