| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Thomas Munro <tmunro(at)postgresql(dot)org>, pgsql-committers <pgsql-committers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pgsql: Check for STATUS_DELETE_PENDING on Windows. |
| Date: | 2022-01-13 17:01:08 |
| Message-ID: | 5ff5239e-b5b2-6874-9667-e927ec55f1db@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
On 1/11/22 16:54, Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>> On 1/11/22 16:22, Thomas Munro wrote:
>>> Those scripts aren't really on my radar... would it be a good idea to
>>> run them as steps in the CompilerWarnings CI task?
>> Or in a buildfarm module (c.f. the perl checks)
> +1 for one or the other, because we break that regularly and it
> typically takes awhile to notice.
>
>
Done See
<https://github.com/PGBuildFarm/client-code/commit/51a6f79ec16de87a7eba7a66015985998311d465>
crake will now run this as part of its normal runs on HEAD.
cheers
andew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-01-13 17:13:08 | Re: pgsql: Check for STATUS_DELETE_PENDING on Windows. |
| Previous Message | Tom Lane | 2022-01-13 15:13:46 | Re: pgsql: Include permissive/enforcing state in sepgsql log messages. |