Re: [ext] Re: Losing data because of problematic configuration?

2021-06-16 Thread Holtgrewe, Manuel
From: Holtgrewe, Manuel Sent: Wednesday, June 16, 2021 10:54:49 AM To: Tom Lane Cc: pgsql-general@lists.postgresql.org Subject: Re: [ext] Re: Losing data because of problematic configuration? Hi again, thank you for pinpointing the issue. I have now updated the table with "

Re: [ext] Re: Losing data because of problematic configuration?

2021-06-16 Thread Holtgrewe, Manuel
____ From: Tom Lane Sent: Tuesday, June 15, 2021 3:39:31 PM To: Holtgrewe, Manuel Cc: pgsql-general@lists.postgresql.org Subject: [ext] Re: Losing data because of problematic configuration? "Holtgrewe, Manuel" writes: > So it looks as if the database jumps back &qu

Re: [ext] Re: Losing data because of problematic configuration?

2021-06-15 Thread Holtgrewe, Manuel
ployment and (b) how that bug came about to be. Thanks a lot! From: Tom Lane Sent: Tuesday, June 15, 2021 3:39:31 PM To: Holtgrewe, Manuel Cc: pgsql-general@lists.postgresql.org Subject: [ext] Re: Losing data because of problematic configuration? "Hol

Re: [ext] Re: Losing data because of problematic configuration?

2021-06-15 Thread Holtgrewe, Manuel
m seeing in my application. Does this help? Where could I look for understanding this better? Thanks, Manuel From: Ron Sent: Tuesday, June 15, 2021 13:07 To: pgsql-general@lists.postgresql.org Subject: [ext] Re: Losing data because of problematic configurati

Losing data because of problematic configuration?

2021-06-15 Thread Holtgrewe, Manuel
Hi, I have a database that is meant to have high-performance for bulk insert operations. I've attached my postgres.conf file. However, I'm seeing the following behaviour. At around 12:04, I have started the database. Then, I did a bulk insert and that completed. I then went on to kill postgr

RE: [ext] Re: Pointers towards identifying bulk import bottleneck (walwriter tuning?)

2019-08-27 Thread Holtgrewe, Manuel
Best wishes, From: Laurenz Albe [laurenz.a...@cybertec.at] Sent: Wednesday, August 28, 2019 05:45 To: Holtgrewe, Manuel; Luca Ferrari Cc: pgsql-general Subject: Re: [ext] Re: Pointers towards identifying bulk import bottleneck (walwriter tuning?) Holtgrewe, M

RE: [ext] Re: Pointers towards identifying bulk import bottleneck (walwriter tuning?)

2019-08-27 Thread Holtgrewe, Manuel
anuel From: Jeff Janes [jeff.ja...@gmail.com] Sent: Tuesday, August 27, 2019 16:45 To: Holtgrewe, Manuel Subject: [ext] Re: Pointers towards identifying bulk import bottleneck (walwriter tuning?) On Tue, Aug 27, 2019 at 6:06 AM Holtgrewe, Manuel mailto:manuel.h

RE: [ext] Re: Pointers towards identifying bulk import bottleneck (walwriter tuning?)

2019-08-27 Thread Holtgrewe, Manuel
Hi, I also tried creating the table as "UNLOGGED" which led to walwriter I/O to drop drastically and I now get no wall-clock time increase with two import processes but it gets slower with four. Switching off fsync leads to a drastic time improvement but still higher wall-clock time for four t

Pointers towards identifying bulk import bottleneck (walwriter tuning?)

2019-08-27 Thread Holtgrewe, Manuel
Dear all, I hope that this is the right place to ask. I have trouble identifying the bottleneck in a bulk import. I'm suspecting the bottleneck to be the walwriter. I'm using PostgreSQL 11, my configuration is at [5]. I'm running on ZFS raidz3 that can write write 300MB/s+. However, I'm only s