> Ok, I see what you're trying to do. In looking at this it occurs to me
that one
> of the way to aid in this effort is through more tech documents. For
instance,
> I have asked before what is the recommended procedure or stategy for
recovering
> a database that has "crashed". Something like that is wide open (and
might not
> even be the correct language) but several tech notes addressing specific
> scenarios would not only aid in actually helping someone but would also
document
> real situation that could then be tested on. Extending that scenario to
other
> area would build a nice library/knowledge base for the community which was
be
> more formalize and more efficient that searching through the newsgroups.
It think this would be great not because I want some sort of certification
but rather because it would be nice to have a nice organized way of learning
(or teaching a new employee or something) both basic and advanced postgres
features.
rg
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
