# Proposal: Add postgresql server version

## What question will this help us answer?

Here are a variety of question examples we would like to answer at some point:
* If we declare a postgresql version X as a minimum, what percentage of our telemetry users would have to upgrade?
* What is the distribution of postgresql server versions in use by telemetry users?

## What is a specific example of the data to be gathered?

{
"postgres version": "9.6.24"
}

## How will this metric be stored in the database or gathered at runtime?

Gathered at runtime.

## Will the gathering and/or storage of this cause unacceptable burden/load on Pulp?

I believe it won't.

## Is this metric Personally-Identifiable-Data?

No

### How can we sanitize this output?

No need to.

## What pulpcore version will this be collected with?

3.22.0

## Alternative proposal(s)

None.

## Summarization

Sum the version strings to add to a single DailySummary event.

{
"postgresql version": {
"9.6": 22,
"12": 45,
"11": 36,
"unknown": 23
}
}

Aggregate numbers based on "new feature releases" of the [postgresql versioning policy](https://www.postgresql.org/support/versioning/).
* For 10+ this means just the X release number. bugfixes are released as x.y
* For < 10, this means x.y number. bugfixes were released as x.y.z

## Visualization

A [chart.js pie chart](https://www.chartjs.org/docs/latest/samples/other-charts/pie.html) showing the most recent DailySummary.

## Discussion notes
* have an "unknown" category for summarization of systems < 3.22 that are reporting data.
* this was added into the summarization section ^
* Only do the pie chart
* The timeseries version of this data was moved to the parking lot below

## Is this approved/not-approved?

approved for pulpcore 3.22.0

## Parking Lot for potential future/RFE work

* A timeseries chart similar to the ones we already have with each line representing a version.

###### tags: `Telemetry`