On 2022-Mar-22, Andrew Dunstan wrote:
> Tomorrow, with the SQL/JSON constructors patch should resolve it. So
> roughly 24 hours. It's not his fault but this happened because Alvaro
> asked me to stagger the commits.
Ouch, yeah. This kind of problem can be observed by using something
like
git rebase -i origin/master -x "make install"
this will generate a rebase "todo list" that includes a "make install"
step after each individual commit, so you can verify that each commit is
warning-clean.
(By default there is no pause after each commit if there is a failure;
my strategy for dealing with that is to change each patch in the
rebase-todo-list from "pick" to "edit", so I can fix any problems, add
them to the commit, then continue the rebase.)
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"En las profundidades de nuestro inconsciente hay una obsesiva necesidad
de un universo lógico y coherente. Pero el universo real se halla siempre
un paso más allá de la lógica" (Irulan)
