MIME-Version: 1.0
In-Reply-To: <4F8CF64C.5050403@2ndQuadrant.com>
References: <96e5156e36277877d18484a5148ad516@biglumber.com>
	<4F8CF64C.5050403@2ndQuadrant.com>
Date: Tue, 17 Apr 2012 08:10:45 +0000
Message-ID: 
 <CA+OCxowaUMZx1qRd2NUiX4dbq3Y2dELW95PMye_V-VALoMmWvA@mail.gmail.com>
Subject: Re: Planet posting policy
From: Dave Page <dpage@pgadmin.org>
To: Greg Smith <greg@2ndquadrant.com>
Cc: pgsql-www@postgresql.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, Apr 17, 2012 at 4:49 AM, Greg Smith <greg@2ndquadrant.com> wrote:
>
> The line is closer for EDB and PEM. =A0I think it's possible to write a P=
EM
> blog post that fits the current rules. =A0If I were tasked with doing tha=
t,
> I'd start with some informative comments about things that are hard to
> monitor in regular PostgreSQL, and what sorts of problems the general
> management headaches related to it cause. =A0Then an ending that introduc=
es
> PEM as an example of how one company addressed those problems in a
> commercial product would be fine. =A0I'd walk away knowing something usef=
ul
> about common deployment problems, and the fact that a commercial product =
was
> suggested as one way to solve them would be helpful.

It's interesting that you think that's possible. I've thus far refused
requests from our marketing department to do exactly at as I thought
it would certainly be a violation of the policy. I'm not convinced it
wouldn't be even now, but it's interesting to know you might find
something acceptable. When I get a hour (probably a couple of years
from now as things are currently looking!) I might give it a whirl and
run it past you guys.


--=20
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company