Horton

RE: Big performance slowdown from 11.2 to 13.3

ldh@laurent-hasson.com <ldh@laurent-hasson.com>

View thread View on postgr.es
From: "ldh@laurent-hasson.com" <ldh@laurent-hasson.com>
To: Justin Pryzby <pryzby@telsasoft.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, David Rowley <dgrowleyml@gmail.com>, Peter Geoghegan <pg@bowt.ie>, "pgsql-performance@postgresql.org" <pgsql-performance@postgresql.org>
Date: 2021-07-22T17:33:09Z
Lists: pgsql-performance 
-----Original Message-----
From: Justin Pryzby <pryzby@telsasoft.com> 
Sent: Thursday, July 22, 2021 13:29
To: ldh@laurent-hasson.com
Cc: Tom Lane <tgl@sss.pgh.pa.us>; David Rowley <dgrowleyml@gmail.com>; Peter Geoghegan <pg@bowt.ie>; pgsql-performance@postgresql.org
Subject: Re: Big performance slowdown from 11.2 to 13.3

On Thu, Jul 22, 2021 at 05:26:26PM +0000, ldh@laurent-hasson.com wrote:
> I tried this but not seeing max resident size data output.

Oh.  Apparently, that's not supported under windows..

#if defined(HAVE_GETRUSAGE)
        appendStringInfo(&str,
                                         "!\t%ld kB max resident size\n",


----------------------------

Hello,

Damn... I know Windows is a lower priority, and this is yet another issue, but in Healthcare, Windows is so prevalent everywhere...

Thank you,
Laurent.

Commits

  1. Get rid of artificial restriction on hash table sizes on Windows.