Re: pgsql: Check for STATUS_DELETE_PENDING on Windows.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
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-11 21:54:10
Message-ID: 2801180.1641938050@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2022-01-12 02:24:21 Re: pgsql: Clean up error message reported after \password encryption failu
Previous Message Andrew Dunstan 2022-01-11 21:44:15 Re: pgsql: Check for STATUS_DELETE_PENDING on Windows.