Date: Thu, 24 Feb 2022 06:59:45 -0600
From: Justin Pryzby <pryzby@telsasoft.com>
To: Ranier Vilela <ranier.vf@gmail.com>
Cc: ldh@laurent-hasson.com, pgsql-performance@postgresql.org
Subject: Re: An I/O error occurred while sending to the backend (PG 13.4)
Message-ID: <20220224125945.GU9008@telsasoft.com>
References: 
 <MN2PR15MB2560DC71C217FF03AC9082F5856B9@MN2PR15MB2560.namprd15.prod.outlook.com>
 <20211204175926.GC17618@telsasoft.com>
 <MN2PR15MB256038B438B8990D08B4A991856B9@MN2PR15MB2560.namprd15.prod.outlook.com>
 <MN2PR15MB256034941F279136BA555236853D9@MN2PR15MB2560.namprd15.prod.outlook.com>
 <CAEudQAot8MJSvryy_M4zD+ZMA83mKAP1-vsUKBGMkJiLHYvXUA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: 
 <CAEudQAot8MJSvryy_M4zD+ZMA83mKAP1-vsUKBGMkJiLHYvXUA@mail.gmail.com>
User-Agent: Mutt/1.9.4 (2018-02-28)
Archived-At: 
 <https://www.postgresql.org/message-id/20220224125945.GU9008%40telsasoft.com>
Precedence: bulk

On Thu, Feb 24, 2022 at 08:50:45AM -0300, Ranier Vilela wrote:
> I can't understand why you are still using 13.4?
> [1] There is a long discussion about the issue with 13.4, the project was
> made to fix a DLL bottleneck.
> 
> Why you not use 13.6?

That other problem (and its fix) were in the windows build environment, and not
an issue in some postgres version.  It's still a good idea to schedule an
update.

-- 
Justin