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

Re: Postgres insert performance and storage requirement compared to Oracle

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Jesper Krogh <jesper(at)krogh(dot)cc>
Cc: Divakar Singh <dpsmails(at)yahoo(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Mladen Gogala <mladen(dot)gogala(at)vmsinfo(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Postgres insert performance and storage requirement compared to Oracle
Date: 2010-10-28 13:13:22
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-performance
On Wed, Oct 27, 2010 at 3:47 PM, Jesper Krogh <jesper(at)krogh(dot)cc> wrote:
> On 2010-10-27 20:51, Merlin Moncure wrote:
>>> Yes, I am quite aware of how the o/s page cache works.  All else being
>>> equal, I more compact database obviously would be preferred.  However
>>> 'all else' is not necessarily equal.  I can mount my database on bzip
>>> volume, that must make it faster, right?  wrong.  I understand the
>>> postgres storage architecture pretty well, and the low hanging fruit
>>> having been grabbed further layout compression is only going to come
>>> as a result of tradeoffs.
> Or configureabillity.. Not directly related to overall space consumption
> but I have been working on a patch that would make TOAST* kick in
> earlier in the process, giving a "slimmer" main table with visibillity
> information
> and simple columns and moving larger colums more aggressively to TOAST.

Do you have any benchmarks supporting if/when such a change would be beneficial?


In response to


pgsql-performance by date

Next:From: Kenneth MarshallDate: 2010-10-28 13:34:36
Subject: Re: Select count(*), the sequel
Previous:From: André VolpatoDate: 2010-10-28 12:33:07
Subject: Re: AIX slow buffer reads

pgsql-hackers by date

Next:From: Tom LaneDate: 2010-10-28 13:36:57
Subject: Re: plan time of MASSIVE partitioning ...
Previous:From: Pavel StehuleDate: 2010-10-28 12:55:40
Subject: revision of todo: NULL for ROW variables

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