Skip site navigation (1) Skip section navigation (2)

Re: performance of insert/delete/update

From: Tim Gardner <tgardner(at)codeHorse(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Cc: "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>
Subject: Re: performance of insert/delete/update
Date: 2002-11-26 00:40:43
Message-ID: p05111b10ba0872da9242@[192.168.1.4] (view raw, whole thread or download thread mbox)
Thread:
Lists: pgsql-hackerspgsql-performance
>With Postgresql's implementation of MVCC, all your data are inserted in
>real time, with a transaction date that makes the other clients ignore
>them (mostly, other read committed transactions may or may not see them.)
>
>If there are indexes to update, they are updated in the same "invisible
>until committed" way.
>
>All this means that your inserts don't block anyone else's reads as well.
>
>This means that when you commit, all postgresql does is make them visible.

scott,

Exactly the kind of explanation/understanding I was hoping for!

Thank you!

Tim

In response to

Responses

pgsql-performance by date

Next:From: scott.marloweDate: 2002-11-26 00:41:09
Subject: Re: performance of insert/delete/update
Previous:From: scott.marloweDate: 2002-11-26 00:30:00
Subject: Re: performance of insert/delete/update

pgsql-hackers by date

Next:From: scott.marloweDate: 2002-11-26 00:41:09
Subject: Re: performance of insert/delete/update
Previous:From: scott.marloweDate: 2002-11-26 00:30:00
Subject: Re: performance of insert/delete/update

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group