Re: pgsql: Common SQL/JSON clauses

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Andres Freund <andres(at)anarazel(dot)de>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Common SQL/JSON clauses
Date: 2022-03-23 09:47:26
Message-ID: 202203230947.rz7ll75qxp2f@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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)

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Tatsuo Ishii 2022-03-23 10:06:50 pgsql: Allow pgbench to retry in some cases.
Previous Message Thomas Munro 2022-03-23 02:20:45 pgsql: Try to stabilize vacuum test.