From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Ярослав Пашинский <yarik97(dot)6(at)gmail(dot)com> |
Cc: | Postgres bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: BUG #16927: Postgres can`t access WAL files |
Date: | 2021-03-19 11:36:19 |
Message-ID: | YFSMsxc8w2eqUHHR@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Fri, Mar 19, 2021 at 11:04:14AM +0200, Ярослав Пашинский wrote:
> I didn't quite understand you here, is " aaaef7a " stands for patch name?
There was a typo in one of my previous messages. What I was referring
to is aaa3aedd. That's a commit of the Postgres code tree, if you are
not familiar with git, here is a link to the code change:
https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=aaa3aedd
>> " How much did you test the unpatched builds by the way? "
> On cluster where load was caused by pgbench I met wal file access error
> after about 1 hour, but on developer server with real load (usually up to
> 100 connections) the error occurred after 2.5-3 hours.
OK, thanks. My environments are not that sensitive to the issue,
unfortunately.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Ярослав Пашинский | 2021-03-19 11:45:24 | Re: BUG #16927: Postgres can`t access WAL files |
Previous Message | Ярослав Пашинский | 2021-03-19 09:04:14 | Re: BUG #16927: Postgres can`t access WAL files |