| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Frits Jalvingh <jal(at)etc(dot)to> |
| Cc: | John Gorman <jgorman(at)eldocomp(dot)com>, "Sunkara, Amrutha" <amrutha(at)nytimes(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Improving PostgreSQL insert performance |
| Date: | 2017-06-09 15:16:51 |
| Message-ID: | CAOR=d=2NrJ=XiU5wj-Y8mV8Fmu2sJ0FgQ902EAEYwN6-E8pKAg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Fri, Jun 9, 2017 at 9:12 AM, Frits Jalvingh <jal(at)etc(dot)to> wrote:
> Hi John,
>
> Yes, I was aware and amazed by that ;) It is actually the fetch size in
> combination with autocommit being on; that dies the sweet OOM death as soon
> as the table gets big.
>
> But Postgres read performance, with autocommit off and fetch size arond 64K,
> is quite OK. But it's good to get this mentioned a lot, because as you said
> you can spend quite some time wondering about this!
No production db server should have the oom killer enabled.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Frits Jalvingh | 2017-06-09 15:22:35 | Re: Improving PostgreSQL insert performance |
| Previous Message | Frits Jalvingh | 2017-06-09 15:12:33 | Re: Improving PostgreSQL insert performance |