Re: [Windows,PATCH] Use faster, higher precision timer API - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [Windows,PATCH] Use faster, higher precision timer API
Date
Msg-id CA+TgmoajJvruv-yytkihJuhq0mChn_zK3-2yGMQd9NtB8ZcQrw@mail.gmail.com
Whole thread Raw
In response to Re: [Windows,PATCH] Use faster, higher precision timer API  (David Rowley <dgrowleyml@gmail.com>)
Responses Re: [Windows,PATCH] Use faster, higher precision timer API
List pgsql-hackers
On Thu, Oct 23, 2014 at 5:41 AM, David Rowley <dgrowleyml@gmail.com> wrote:
> On Thu, Oct 23, 2014 at 1:27 AM, Craig Ringer <craig@2ndquadrant.com> wrote:
>> Here's an updated patch addressing David's points.
>> I haven't had a chance to test it yet, on win2k8 or win2k12 due to
>> pgconf.eu .
>>
> Hi Craig, thanks for the fast turnaround.
>
> I've just had a look over the patch again:
>
> +               DWORD errcode = GetLastError();
> +               Assert(errcode == ERROR_PROC_NOT_FOUND);
>
> I'm not a big fan of this. It seems quite strange to be using Assert in this
> way.

Agreed - I think if you want an error check here it should use elog()
or ereport(), not Assert().

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Dag-Erling Smørgrav
Date:
Subject: Re: [PATCH] add ssl_protocols configuration option
Next
From: Tom Lane
Date:
Subject: Re: [BUGS] ltree::text not immutable?