| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | "Saul, Jean Paolo" <paolo(dot)saul(at)verizonconnect(dot)com> |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #15609: synchronous_commit=off insert performance regression with secondary indexes |
| Date: | 2019-01-30 04:32:25 |
| Message-ID: | CAH2-Wz=uVWYekJP4Wey2A35jLSjoc8BeLCj+UEnD7ZSh4158Sg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi,
On Tue, Jan 29, 2019 at 8:27 PM Saul, Jean Paolo
<paolo(dot)saul(at)verizonconnect(dot)com> wrote:
> That seems to have narrowed down the regression to Boolean data types only.
> I will run the test now against the most common base types that we use and report back.
>
> Is this a known regression/bug on PG10+? Sorry I could not find any reference to this bug.
I can't think of a reason why the problem would be any worse on recent
releases right now. However, the behavior I'm describing is
complicated. I could have missed something.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Toshi Harada | 2019-01-30 05:06:29 | Re: BUG #15610: Performance problem of PostgreSQL 11.1 Windowsversion (EDB created version) |
| Previous Message | Saul, Jean Paolo | 2019-01-30 04:26:49 | Re: BUG #15609: synchronous_commit=off insert performance regression with secondary indexes |