Responded to the separately cross-posted version on -www...in short this is not a big reporting list and doesn't need the same rules or expectations. Assume agnostic o/s and current release then deal with variations as they are needed.
David J. On Wednesday, January 6, 2016, Melvin Davidson <melvin6...@gmail.com> wrote: > > I would like to see the following added to the introduction to this list. > > "When submitting to this list, please include the full version of > PostgreSQL and the O/S you are using. > Also, if you are reportaing a problem, it is essential that a minimal > amount of schema & data be > provided in order to duplicate problem being reported, as well as exact > error verbage encountered and > any relevant extracts from the postgresql log file(s)." > > While some may think there are cases where this is irrelavant, there are > now in existence seveeral > versions of PostgreSQL across multiple operating systems. It it not > inconcievable that a bug (or problem) > being reported in a previous version & O/S has already been corrected in a > newer one. Likewise, something > that may occur in one version & O/S may not occur in another. > > If it is just a general query, keep in mind that new features are > constantly being added with each new > release, so something previously impossible (or done another way) in a > previous version, may now be > simplified with the implementation of a new function/feature. > > I encourage additional suggestions as to what should be included when > submitting queries to this list. > -- > *Melvin Davidson* > I reserve the right to fantasize. Whether or not you > wish to share my fantasy is entirely up to you. > > Folk Alley - All Folk - 24 Hours a day > www.folkalley.com >
