diff options
| author | Thien-Thi Nguyen <ttn@gnuvola.org> | 2022-01-06 15:56:00 -0500 |
|---|---|---|
| committer | Thien-Thi Nguyen <ttn@gnuvola.org> | 2022-01-06 15:56:00 -0500 |
| commit | b6b96eebb81ff3daecced9b43218ba8eb3268cce (patch) | |
| tree | 1dec1e935b8d49b9453392bef26e7e59f4d847bb /taler-exchange-manual.rst | |
| parent | 9fce45f796ef8e92fc5731d1a897dd337a6f921b (diff) | |
| download | docs-b6b96eebb81ff3daecced9b43218ba8eb3268cce.tar.gz docs-b6b96eebb81ff3daecced9b43218ba8eb3268cce.tar.bz2 docs-b6b96eebb81ff3daecced9b43218ba8eb3268cce.zip | |
s/Postgres/PostgreSQL/g
Diffstat (limited to 'taler-exchange-manual.rst')
| -rw-r--r-- | taler-exchange-manual.rst | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/taler-exchange-manual.rst b/taler-exchange-manual.rst index 7beb7fb7..a9574479 100644 --- a/taler-exchange-manual.rst +++ b/taler-exchange-manual.rst @@ -63,7 +63,7 @@ etc.). This manual will not cover these aspects of operating a payment service provider. We will assume that you can operate a (high-availability, -high-assurance) Postgres database. Furthermore, we expect some moderate +high-assurance) PostgreSQL database. Furthermore, we expect some moderate familiarity with the compilation and installation of free software packages. You need to understand the cryptographic concepts of private and public keys and must be able to protect private keys stored in files @@ -181,9 +181,9 @@ components: The exchange requires a DBMS to stores the transaction history for the Taler exchange and aggregator, and a (typically separate) DBMS for the Taler auditor. For now, the GNU Taler reference implementation - only supports Postgres, but the code could be easily extended to + only supports PostgreSQL, but the code could be easily extended to support another DBMS. - .. index:: Postgres + .. index:: PostgreSQL - Auditor The auditor verifies that the transactions performed by the exchange @@ -787,7 +787,7 @@ they should use the same configuration file. For the most secure deployment, we recommend using separate users for each of these processes to minimize information disclosures should any of them be -compromised. The helpers do not need access to the Postgres database (and +compromised. The helpers do not need access to the PostgreSQL database (and thus also should not have it). The processes that require access to the bank account need to have a @@ -1066,4 +1066,4 @@ repetitions (i.e. if the operation failed the first time), total execution time (operating system and user space) and other details. Naturally, additional instrumentation (including using features of the -Postgres database itself) may help discover performance issues. +PostgreSQL database itself) may help discover performance issues. |