Date: Mon, 19 Sep 2011 21:32:41 -0400
From: Stephen Frost <sfrost@snowman.net>
To: Jon Nelson <jnelson+pgsql@jamponi.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: Postgres INSERT performance and scalability
Message-ID: <20110920013241.GR12765@tamriel.snowman.net>
References: 
 <CAMhtkAb1F1SOyz1mzeeWaQehoqtzk29oLVVG=NzKEoGS9bPDNg@mail.gmail.com>
	<20110920005342.GO12765@tamriel.snowman.net>
	<CAKuK5J0-fEHVm_c_H6T6XMk9PQE6zDohBHqZ39CHu5Hz0kGC4g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="ElEgulhWJDonIdTi"
Content-Disposition: inline
In-Reply-To: 
 <CAKuK5J0-fEHVm_c_H6T6XMk9PQE6zDohBHqZ39CHu5Hz0kGC4g@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)


--ElEgulhWJDonIdTi
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

* Jon Nelson (jnelson+pgsql@jamponi.net) wrote:
> Isn't the WAL basically COW?

eh..?  No..  The WAL is used to record what changes are made to the
various files in the database, it certainly isn't an kind of
"copy-on-write" system, where we wait until a change is made to data
before copying it..

If you INSERT .. SELECT, you're going to get the real data in the WAL,
and also in the heap of the new table..

	Thanks,

		Stephen

--ElEgulhWJDonIdTi
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAk537TkACgkQrzgMPqB3kiiLDQCfdY1tAnRbN21DnEZF7tAakp1N
34EAoIDDaLwWFiVeEJ22fq+2s8wYYIzS
=ljae
-----END PGP SIGNATURE-----

--ElEgulhWJDonIdTi--