| From: | Paul A Jungwirth <pj(at)illuminatedcomputing(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Performance appending to an array column |
| Date: | 2017-09-21 21:05:13 |
| Message-ID: | CA+renyVvLsfOiydvo=AZsEU9ZgavrfXH7vxOFpGb1OP8HiByDg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> It's going to suck big-time :-(.
Ha ha that's what I thought, but thank you for confirming. :-)
> We ended up keeping
> the time series data outside the DB; I doubt the conclusion would be
> different today.
Interesting. That seems a little radical to me, but I'll consider it
more seriously now. I also tried cstore_fdw for this, but my queries
(building a 2-D histogram) were taking 4+ seconds, compared to 500ms
using arrays. Putting everything into regular files gives up filtering
and other SQL built-ins, but maybe I could write my own extension to
load regular files into Postgres arrays, sort of getting the best of
both worlds.
Anyway, thanks for sharing your experience!
Yours,
Paul
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Kellerer | 2017-09-21 21:29:18 | Re: Performance appending to an array column |
| Previous Message | Igor Neyman | 2017-09-21 20:44:56 | Re: Logical decoding client has the power to crash the server |