Date: Wed, 21 Dec 2005 21:14:18 -0500
From: Stephen Frost <sfrost@snowman.net>
To: Madison Kelly <linux@alteeve.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: MySQL is faster than PgSQL but a large margin in my program...
	any ideas why?
Message-ID: <20051222021418.GB6026@ns.snowman.net>
Mail-Followup-To: Madison Kelly <linux@alteeve.com>,
	pgsql-performance@postgresql.org
References: <43AA0966.6090401@alteeve.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="zo8WNJAiJDhUkHLZ"
Content-Disposition: inline
In-Reply-To: <43AA0966.6090401@alteeve.com>
User-Agent: Mutt/1.5.9i


--zo8WNJAiJDhUkHLZ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* Madison Kelly (linux@alteeve.com) wrote:
>   If the performace difference comes from the 'COPY...' command being=20
> slower because of the automatic quoting can I somehow tell PostgreSQL=20
> that the data is pre-quoted? Could the performance difference be=20
> something else?

I doubt the issue is with the COPY command being slower than INSERTs
(I'd expect the opposite generally, actually...).  What's the table type
of the MySQL tables?  Is it MyISAM or InnoDB (I think those are the main
alternatives)?  IIRC, MyISAM doesn't do ACID and isn't transaction safe,
and has problems with data reliability (aiui, equivilant to doing 'fsync
=3D false' for Postgres).  InnoDB, again iirc, is transaction safe and
whatnot, and more akin to the default PostgreSQL setup.

I expect some others will comment along these lines too, if my response
isn't entirely clear. :)

	Stephen

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

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

iD8DBQFDqgv6rzgMPqB3kigRAmFvAJ9V3TT2/Ct5SJzRwvA4TfBfSCm5oQCeM6z7
Xf4XVaAlRT90DGAaYpvp+X4=
=n6k0
-----END PGP SIGNATURE-----

--zo8WNJAiJDhUkHLZ--