From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org, pgsql-release(at)postgresql(dot)org, Noah Misch <noah(at)leadboat(dot)com>, pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | Re: pgsql: Avoid race in RelationBuildDesc() affecting CREATE INDEX CONCURR |
Date: | 2022-02-09 02:24:21 |
Message-ID: | YgMl1YJ1B3n8cGMr@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On Tue, Feb 08, 2022 at 05:43:34PM -0800, Andres Freund wrote:
> It's stamped, not tagged, so we could send out new tarballs. Or we could skip
> a release number. IIRC we had to do something along those lines before.
It does not matter now, but the release is stamped and tagged.
> What do you mean with detect here?
Well, we would not be able to see that something is stuck by default,
but Noah has just answered to my question by mentioning wait_timeout
in the buildfarm configuration.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2022-02-09 03:11:59 | pgsql: Retire src/backend/utils/misc/check_guc |
Previous Message | Noah Misch | 2022-02-09 02:04:03 | Re: pgsql: Avoid race in RelationBuildDesc() affecting CREATE INDEX CONCURR |
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2022-02-09 02:24:35 | Re: [BUG]Update Toast data failure in logical replication |
Previous Message | Michael Paquier | 2022-02-09 02:21:41 | Re: is the base backup protocol used by out-of-core tools? |