On Thu, Mar 18, 2021 at 12:01:40PM +0900, Michael Paquier wrote:
> Yep, that's actually something I wrote for my own setups, with
> log_checkpoints enabled to catch all concurrent checkpoint activity
> and some LOGs. Still no luck unfortunately :(
The various reporters had more luck than myself
On Wed, Mar 17, 2021 at 07:30:04PM -0700, Andres Freund wrote:
> I suspect it might be easier to reproduce the issue with smaller WAL
> segments, a short checkpoint_timeout, and multiple jobs generating WAL
> and then sleeping for random amounts of time. Not sure if that's the
> sole ingredient,
Hi,
On 2021-03-18 09:55:46 +0900, Michael Paquier wrote:
> Let's see how it goes from this point, but, FWIW, I have not been able
> to reproduce again my similar problem with the archive command :/ --
I suspect it might be easier to reproduce the issue with smaller WAL
segments, a short
Hi,
On 2021-03-16 16:20:37 +0900, Michael Paquier wrote:
> Fujii-san has mentioned that on twitter, but one area that has changed
> during the v13 cycle is aaa3aed, where the code recycling segments has
> been switched from a pgrename() (with a retry loop) to a
> CreateHardLinkA()+pgunlink()
On Tue, Mar 16, 2021 at 11:40:12AM +0100, Magnus Hagander wrote:
> If we can provide a new .EXE built with exactly the same flags as the
> EDB downloads that they can just drop into a directory, I think it's a
> lot easier to get that done.
Yeah, multiple people have been complaining about that
>Yeah, it'd definitely be good to figure out exactly what it is that
>triggers the issue.
I think that this issue is the same at 1.
And IMHO the patch solves, but nobody is interested.
I think that "MOVEFILE_COPY_ALLOWED" that's what is missing.
At least on my machine, Postgres can rename
On Tue, Mar 16, 2021 at 11:22 AM Michael Paquier wrote:
>
> On Tue, Mar 16, 2021 at 10:02:25AM +0100, Magnus Hagander wrote:
> > If you back out that patch, does the problem you can reproduce with
> > archive_command go away?
>
> That's the first thing I did after seeing the failure, and I saw
>
On Tue, Mar 16, 2021 at 10:02:25AM +0100, Magnus Hagander wrote:
> If you back out that patch, does the problem you can reproduce with
> archive_command go away?
That's the first thing I did after seeing the failure, and I saw
nothing after 2~3 hours of pgbench :)
The second thing I did was to
On Tue, Mar 16, 2021 at 8:20 AM Michael Paquier wrote:
>
> Hi all,
>
> There has been for the last couple of weeks a collection of reports
> complaining that the renaming of WAL segments is broken:
> https://www.postgresql.org/message-id/3861ff1e-0923-7838-e826-094cc9bef...@hot.ee
>
Hi all,
There has been for the last couple of weeks a collection of reports
complaining that the renaming of WAL segments is broken:
https://www.postgresql.org/message-id/3861ff1e-0923-7838-e826-094cc9bef...@hot.ee
https://www.postgresql.org/message-id/16874-c3eecd319e36a...@postgresql.org
10 matches
Mail list logo
