| From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
|---|---|
| To: | Keith <keith(at)keithf4(dot)com> |
| Cc: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Read performance on Large Table |
| Date: | 2015-05-21 16:34:49 |
| Message-ID: | C591EA33-4121-454A-9ECA-A90518A5B7E2@elevated-dev.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On May 21, 2015, at 10:25 AM, Keith <keith(at)keithf4(dot)com> wrote:
>
> The problem with creating partitions on the fly via triggers, even ahead of when they're needed, is you run into BIG contention issues when you have high insert rates. One session will see it needs to create a new table, the next one comes in before the table is made but either gets put into a wait state or outright fails when it goes to try and make the new table that's already there…
No failure, I handle the exception.
> It may not be an issue for you, but it's definitely something to keep in mind if you notice performance issues. :)
>
Right. Around midnight this db has very low activity.
--
Scott Ribe
scott_ribe(at)elevated-dev(dot)com
http://www.elevated-dev.com/
https://www.linkedin.com/in/scottribe/
(303) 722-0567 voice
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas SIMON | 2015-05-21 16:56:09 | Re: Performances issues with SSD volume ? |
| Previous Message | Keith | 2015-05-21 16:25:17 | Re: Read performance on Large Table |