Re: partitioning question

From: Alex Samad <alex(at)samad(dot)com(dot)au>
To: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
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 22:58:08
Message-ID: CAJ+Q1PV1X=6w4o8LYst3joPnzwtP_qF_DN-Y5i4OyxsbB0d4nw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

The comparison would be

a if then else end if .. about 8 of them 2013-> and a static insert into

v's

making a dynamic string and using execute, my presumption would be the
execute would be expensive verses a INSERT command

A

On 1 August 2017 at 07:04, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:

> 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.
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Alex Samad 2017-08-01 06:16:29 Re: Question about loading up a table
Previous Message Alex Samad 2017-07-31 22:56:20 Re: Question about loading up a table