If you considering a skills outline, also consider dividing it two areas;
developer and dba.
My experience is mostly with Oracle (more years than I care to remember),
and with this product in many organizations, there are usually two camps;
the dba (God) and the developers (devils - always trying to break the db,
and annoy the dba)
From watching this list for the past couple of weeks it appears that many
members of this list are both developer (some of postgres itself and
others, users of postgres) and dba.
I think that the divide (with Oracle) is mostly political and cultural,
and that the best database solutions are those built by individuals or
teams that straddle both camps.
I've come to Postgres because I working with a startup that cannot afford
the Oracle web license. I suspect that a proportion of new users are also
those who have come from other databases for varying reasons (often
financial, missing feature set etc).
To cater for this "market", maybe it would be best to provide material
that caters specifically to the DBA, the developer, or those that want to
be both.
Just my $0.02 (FWIW).
John Sidney-Woollett
Bruce Momjian said:
> Chris Travers wrote:
>> I am wondering if you are interested in helping with some sort of skills
>> outline project-- what skills we as a community think are important for
>> someone to claim basic mastery over the database manager. Not as if you
>> don't have enough to do already ;-) Maybe at least as a mentor.
>
> Sure, makes sense.
>
> --
> Bruce Momjian | http://candle.pha.pa.us
> pgman@candle.pha.pa.us | (610) 359-1001
> + If your life is a hard drive, | 13 Roberts Road
> + Christ can be your backup. | Newtown Square, Pennsylvania
> 19073
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
>