Re: BUG #18828: Crash when pg_get_logical_snapshot_meta() passed empty string
От | David Rowley |
---|---|
Тема | Re: BUG #18828: Crash when pg_get_logical_snapshot_meta() passed empty string |
Дата | |
Msg-id | CAApHDvpiA1Kd4Ln8h=6kxDRG9OO-CM00Md8hj-8scrDe+GsnuA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: BUG #18828: Crash when pg_get_logical_snapshot_meta() passed empty string (Masahiko Sawada <sawada.mshk@gmail.com>) |
Ответы |
Re: BUG #18828: Crash when pg_get_logical_snapshot_meta() passed empty string
|
Список | pgsql-bugs |
On Thu, 13 Mar 2025 at 10:34, Masahiko Sawada <sawada.mshk@gmail.com> wrote: > BTW how did you catch the warning? I checked before the push if the > change had passed the CI tests (completed with green status). But when > checking the build log now, I can see the warning in the build logs. My workflow is, when still working in the feature branch, to always do "perl src/tools/pgindent/pgindent --commit HEAD" once I'm ready for it to be pushed (assuming there's only 1 commit). If there's any diff I'll "git commit -a --fixup HEAD && git rebase -i master" and adjust the commit type of the fixup commit as "fixup" (or "f"). I'll then do a final "git format-patch" and "git am" that to git master and run the tests before pushing. I tend to never do any fixups in git master as I'm too scared I'll one day push one of them accidentally. If the pgindent diff has anything unexpected in it, I'll consider if I need to update typedefs.list to fix. David
В списке pgsql-bugs по дате отправления: