Re: Postgres INSERT performance and scalability

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Igor Chudov <ichudov(at)gmail(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Postgres INSERT performance and scalability
Date: 2011-09-20 00:53:42
Message-ID: 20110920005342.GO12765@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Igor,

* Igor Chudov (ichudov(at)gmail(dot)com) wrote:
> Would the time that it takes, differ a great deal, depending on whether the
> table has only 100,000 or 5,000,000 records?

Yes, because PostgreSQL is going to copy the data. If you don't need or
want it to be copied, just use a view. I've never heard of any
relational database implementing 'copy on write' type semantics, if
that's what you're asking about. Databases, unlike applications with
code in memory that's constantly copied, are typically focused around
minimizing duplication of data (since it all has to end up on disk at
some point). Not much point in having the overhead of COW for that kind
of environment, I wouldn't think.

Thanks,

Stephen

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Igor Chudov 2011-09-20 01:11:44 Re: Postgres INSERT performance and scalability
Previous Message Scott Marlowe 2011-09-19 23:32:29 Re: Postgres INSERT performance and scalability