Insert vs Update

From: Robert DiFalco <robert(dot)difalco(at)gmail(dot)com>
To: "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Insert vs Update
Date: 2015-07-15 16:16:21
Message-ID: CAAXGW-wggR7sSk=hRLFHMwLH+XP9ovdjCVScZmpWSu49t1m=fw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

First off I apologize if this is question has been beaten to death. I've
looked around for a simple answer and could not find one.

Given a database that will not have it's PKEY or indices modified, is it
generally faster to INSERT or UPDATE data. And if there is a performance
difference is it substantial?

I have a situation where I can easily do one or the other to the same
effect. For example, I have a journaling schema with a limited number of
"states" for an "entry". Currently each state is it's own table so I just
insert them as they occur. But I could easily have a single "entry" table
where the row is updated with column information for states (after the
entry's initial insertion).

Not a big deal but since it's so easy for me to take either approach I was
wondering if one was more efficient (for a large DB) than another.

Thanks!

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message David G. Johnston 2015-07-15 17:10:46 Re: Insert vs Update
Previous Message Ryan King - NOAA Affiliate 2015-07-15 14:13:53 Re: could not create shared memory segment: Invalid argument