Received: from leela.one-2-one.net (leela.one-2-one.net [217.115.142.65]) by postgresql.org (8.11.3/8.11.4) with ESMTP id fAT8jfm29149 for ; Thu, 29 Nov 2001 03:45:41 -0500 (EST) (envelope-from twanger@bluetwanger.de) Received: from [192.168.0.14] (pD9501213.dip.t-dialin.net [217.80.18.19]) by leela.one-2-one.net (8.11.0/8.11.0) with ESMTP id fAT8hCe06060 for ; Thu, 29 Nov 2001 09:43:12 +0100 Subject: date_part vs extract From: Markus Bertheau To: postgres sql list Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-YH2ftqIGFB3lbUvBz93m" X-Mailer: Evolution/0.99.2 (Preview Release) Date: 29 Nov 2001 09:45:38 +0100 Message-Id: <1007023539.4636.66.camel@entwicklung01.cenes.de> Mime-Version: 1.0 X-Archive-Number: 200111/401 X-Sequence-Number: 5783 --=-YH2ftqIGFB3lbUvBz93m Content-Type: text/plain Content-Transfer-Encoding: quoted-printable I wonder about the difference between date_part('week', ...) and extract(week from ...) not only but also from a performance point of view. I read extract is standard and date_part is not. Backwards compatibility maybe justifies the existence of date_part. Whats else? Markus Bertheau --=-YH2ftqIGFB3lbUvBz93m Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQA8BfWyKNEjAb345r4RAql2AJwJc6HjUSEfKB03CIYdswcZsdvMNQCfaznh DQq3vnAqpXl9viLAmZcKqRc= =057f -----END PGP SIGNATURE----- --=-YH2ftqIGFB3lbUvBz93m--