>
>
> PGOPTIONS="-c synchronous_commit=off" pgbench -T 3600 -P 10
>
>
> I am currently running all my benchmarks with synchronous_commit=off and
> will get back with my findings.
>
It seems that PGOPTIONS="-c synchronous_commit=off" has a significant
impact. However, I still can not understa
Hi Jeff,
Thank you for replying.
> wal_sync_method=fsync
>
>
Why this change?
Actually, I re-checked and noticed that this config section was left to
it's default values, which is the following. Since the commented line said
`wal_sync_method = fsync`, I _assumed_ that's the default value.
On 1/26/19 11:56 AM, Mariel Cherkassky wrote:
Update to the minor version should be an easy solution - yum update
postgresql . What did you mean by carful
Sorry, I meant, do not forget to apply update to be sure same bug do not
happen again.
Update to the minor version should be an easy solution - yum update
postgresql . What did you mean by carful
On Sat, Jan 26, 2019, 12:48 PM Adrien NAYRAT On 1/25/19 6:20 PM, Mariel Cherkassky wrote:
> > I'm getting this issue when I try to connect to a specific db. Does it
> > matters what table
On 1/25/19 6:20 PM, Mariel Cherkassky wrote:
I'm getting this issue when I try to connect to a specific db. Does it
matters what table I specify ? Should I just choose a random table from
the problematic db? If I'll dump the db and restore it it can help ?
Error message is on "db1.public.table
