Remove the incomplete postgres storage backend.

CHANGELOG.md

@@ -16,6 +16,7 @@
    - `TrillianLog.GetLeavesByHash`
    - `TrillianLog.GetLeavesByIndex`
    - `TrillianLog.QueueLeaves`
+ * Removed the incomplete Postgres storage backend (#1298).
 
 ### Storage refactoring
  * `NodeReader.GetMerkleNodes` does not accept revisions anymore. The

docs/Feature_Implementation_Matrix.md

@@ -60,7 +60,6 @@ The Log storage implementations supporting the original Trillian log.
 | Spanner          | GA      | ✓                   | Google internal-only, see CloudSpanner for external use.                    |
 | CloudSpanner    | Beta     |                     | Google maintains continuous-integration environment based on CloudSpanner.  |
 | MySQL            | GA      | ✓                   |                                                                             |
-| Postgres        | In dev. |                     | [#1298](https://github.com/google/trillian/issues/1298)                     |
 
 ##### Spanner
 This is a Google-internal implementation, and is used by all of Google's current Trillian deployments.
@@ -80,9 +79,6 @@ It's currently in production use by at least one CT log operator.
 
 Write throughput of 4-500 entries/s has been observed.
 
-##### Postgres
-The postgres implementation is currently under development, and is not ready for use.
-
 ### Monitoring
 
 Supported monitoring frameworks, allowing for production monitoring and alerting.
@@ -111,7 +107,6 @@ Supported frameworks for quota management.
 | etcd            | GA      | ✓                   |                                                                             |
 | MySQL           | Beta    | ?                   |                                                                             |
 | Redis           | Alpha   | ✓                   |                                                                             |
-| Postgres        | NI      |                     |                                                                             |
 
 ### Key management
 

storage/README.md

@@ -13,9 +13,6 @@ The MySQL / MariaDB implementation includes support for Maps. This has not yet
 been implemented by Cloud Spanner. There may be other storage implementations
 available from third parties.
 
-These implementations are under development and are not yet ready for use.
-   * Postgres, in the [postgres](postgres) package.
-
 These implementations are for test purposes only and should not be used by real
 applications:
    * In-memory Storage, in the [memory](memory) package.