Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id A4C352E00CF for ; Wed, 5 Mar 2008 14:31:03 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 51653-02 for ; Wed, 5 Mar 2008 14:31:00 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by postgresql.org (Postfix) with ESMTP id A7E932E1BF9 for ; Wed, 5 Mar 2008 14:31:00 -0400 (AST) Received: from jd-laptop (or-65-40-176-144.dyn.embarqhsd.net [65.40.176.144]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id m25IVAs8005237 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Mar 2008 10:31:12 -0800 Date: Wed, 5 Mar 2008 10:30:43 -0800 From: "Joshua D. Drake" To: David Fetter Cc: Tom Lane , Bruce Momjian , Richard Huxton , PostgreSQL Docs Subject: Re: FAQ on Embedding Postgres Message-ID: <20080305103043.233761e8@jd-laptop> In-Reply-To: <20080305182500.GN19860@fetter.org> References: <200803051502.m25F2fm03349@momjian.us> <718.1204738553@sss.pgh.pa.us> <20080305174126.GM19860@fetter.org> <1029.1204739761@sss.pgh.pa.us> <20080305182500.GN19860@fetter.org> Organization: Joshua D. Drake X-Mailer: Claws Mail 3.3.1 (GTK+ 2.12.0; i486-pc-linux-gnu) Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/pEdjZjoWtr=4tJSekN=+4J8"; protocol="application/pgp-signature"; micalg=PGP-SHA1 X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Wed, 05 Mar 2008 10:31:12 -0800 (PST) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200803/19 X-Sequence-Number: 4831 --Sig_/pEdjZjoWtr=4tJSekN=+4J8 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Wed, 5 Mar 2008 10:25:00 -0800 David Fetter wrote: > It's good to explain why PG does what it does how it does it, and that > should be in that section of the FAQ, but continuing, even by silence, > with an answer equivalent to, "We don't do that. You shouldn't > either. Tough $#!+" only makes us look bad, where suggesting > alternatives for the use cases we don't cover makes us look good. I believe there is wording that could be used that would not convey that sentiment. Sincerely, Joshua D. Drake >=20 > Cheers, > David. --=20 The PostgreSQL Company since 1997: http://www.commandprompt.com/=20 PostgreSQL Community Conference: http://www.postgresqlconference.org/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate PostgreSQL SPI Liaison | SPI Director | PostgreSQL political pundit --Sig_/pEdjZjoWtr=4tJSekN=+4J8 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHzubTATb/zqfZUUQRAiQnAJ0SBQICWi9VmfN0bZxCd42rA7IFBwCfaiA4 WeevGUtrov1LvWlJ39iPpHc= =SUn4 -----END PGP SIGNATURE----- --Sig_/pEdjZjoWtr=4tJSekN=+4J8--