PostgreSQL examples included in example overrides
& PostgreSQL doc improvements
#20
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This includes some PostgreSQL (i.e.
pgsql
) examples in theoverrides
file.Whilst the general nature of the existing MySQL/MariaDB override examples also apply to PostgreSQL, it's not immediately clear what the limits usage for PostgreSQL is. Whilst I imagine many might assume
pgsql
, PostgreSQL is also often abbreviated topgsql
. IMO it's better be explicit.Closes turnkeylinux/tracker#1948
This PR also includes improvement of the
tklbam-backup
&tklbam-restore
docs:mysql
limits also relates to MariaDBpgsql
postgres
database. See bug: TKLBAM: On PostgreSQL appliance - not includingpostgres
DB by default, or even if explictly noted as a "limit" tracker#1943The relevant website doc pages have already been updated to be consistent with the changes in this PR..