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

Re: performance of insert/delete/update

From: Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PgSQL Performance ML <pgsql-performance(at)postgresql(dot)org>
Subject: Re: performance of insert/delete/update
Date: 2002-11-26 04:27:41
Message-ID: 1038284861.26985.59.camel@haggis (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-performance
On Mon, 2002-11-25 at 21:30, Tom Lane wrote:
> Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> writes:
> > On Mon, 2002-11-25 at 18:23, scott.marlowe wrote:
> >> The next factor that makes for fast inserts of large amounts of data in a 
> >> transaction is MVCC.  With Oracle and many other databases, transactions 
> >> are written into a seperate log file, and when you commit, they are 
> >> inserted into the database as one big group.  This means you write your 
> >> data twice, once into the transaction log, and once into the database.
> > You are just deferring the pain.  Whereas others must flush from log
> > to "database files", they do not have to VACUUM or VACUUM ANALYZE.
> Sure, it's just shuffling the housekeeping work from one place to
> another.  The thing that I like about Postgres' approach is that we
> put the housekeeping in a background task (VACUUM) rather than in the
> critical path of foreground transaction commit.

If you have a quiescent point somewhere in the middle of the night...

It's all about differing philosophies, though, and there's no way
that Oracle will re-write Rdb/VMS (they bought it from DEC in 1997
for it's high-volume OLTP technolgies) and you all won't re-write

| Ron Johnson, Jr.     mailto:ron(dot)l(dot)johnson(at)cox(dot)net          |
| Jefferson, LA  USA  |
|                                                            |
| "they love our milk and honey, but preach about another    |
|  way of living"                                            |
|    Merle Haggard, "The Fighting Side Of Me"                |

In response to


pgsql-performance by date

Next:From: typeaDate: 2002-11-26 09:36:59
Subject: Full Text Index disk space requirements
Previous:From: Rod TaylorDate: 2002-11-26 03:52:51
Subject: Re: performance of insert/delete/update

pgsql-hackers by date

Next:From: Al SuttonDate: 2002-11-26 08:24:03
Subject: Re: [mail] Re: Native Win32 sources
Previous:From: Rod TaylorDate: 2002-11-26 03:52:51
Subject: Re: performance of insert/delete/update

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