| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Alex Samad <alex(at)samad(dot)com(dot)au> |
| Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: partitioning question |
| Date: | 2017-07-31 21:04:11 |
| Message-ID: | CAOR=d=3zgcvKXtVs51q+kes7oecKMVNK+1JPKAaWO3Fa2aVt-g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, Jul 30, 2017 at 7:13 PM, Alex Samad <alex(at)samad(dot)com(dot)au> wrote:
> How expensive is dynamic over static. I'm looking at storing yearly now, so
> I figure if my if then clause has the latest year at the top it should be
> very quick.
Assuming you're not doing anything particularly crazy it's minimal.
But what is good performance for one application may not be acceptable
for others. Generally the cost of inserting is MUCH higher than the
cost of dynamically setting the target, esp if you stick to plpgsql
and don't try to use rules to accomplish it.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2017-07-31 21:06:57 | Re: Schemas and serials |
| Previous Message | Scott Marlowe | 2017-07-31 20:59:50 | Re: Question about loading up a table |