tendermint

291 MiB

Tree: 540aea1030

Author	SHA1	Message	Date
mergify[bot]	260f4250b0	Fix incorrect tests using the PSQL sink. (backport #7349 ) (#7355 ) Some of our tests were creating a psql event sink and expecting it to report (or not report) certain kinds of errors. These tests were ill-founded in a couple of ways: 1. Tests that required the Postgres driver were not loading it. This led to spurious successes on tests that wanted "some error" from the sink constructor, but didn't exercise the right path. 2. Tests that wanted a Postgres sink to succeed without a database. These tests "passed" because they weren't actually establishing a connection to the database, but if they had would have failed for the lack of one. To fix this: - Load the postgres driver in tests that need it. - Verify connectivity before reporting successful creation of a PSQL event sink. - Remove tests that wanted a psql sink without a database, since that case is already tested elsewhere. (cherry picked from commit `ab1788b922`)	3 years ago
Sam Kleinman	1c4950dbd2	state: move package to internal (#6964 )	3 years ago
M. J. Fromberger	7fe3e78a38	Update the psql indexer schema and implementation (#6868 ) Update the schema and implementation of the Postgres event indexer to improve certain types of queries against the index. These changes address the use cases raised by #6843, and are partly inspired by the prototype schema in that issue. In the old schema, events were flattened, making it difficult to find all the events associated with a particular block or transaction. In addition, events with no key/value attributes were entirely lost, since entries were generated only for attributes. To address these issues, this new schema records blocks, transactions, events, and attributes in separate tables, and provides views that join these tables to give a more convenient query surface for block and transaction events. - All events for a given block can be queried from the `block_events` view. - All events for a given transaction can be queried from the `tx_events` view. - Multiple events for the same key can be indexed for both blocks and transactions. The tests have been reworked, but all of the existing test cases for the old schema still pass with the new implementation. Various other minor cleanups are included, ADR-065 is also updated to reflect the updated schema.	3 years ago
M. J. Fromberger	41a361ed8d	psql: add documentation and simplify constructor API (#6856 ) Add documentation comments to the psql event sink package, and simplify the constructor function so that it does not return the SQL database handle. The handle is needed for testing, so expose that via a separate method on the concrete type. Update the tests and existing usage for the change. This change does not affect the behaviour of the sink, so there are no functional changes, only syntactic updates.	3 years ago
JayT106	e850863296	state/indexer: close row after query (#6664 ) Closes: #6661 Note: see another error during the events indexing, guess the raw tx size exceeds the limitation? ``` 3:17PM ERR failed to index block txs err="pq: index row size 2768 exceeds btree version 4 maximum 2704 for index \"tx_results_tx_result_key\"" height=5205112 module=txindex	3 years ago
JayT106	d2b78ec09b	indexer: use INSERT ... ON CONFLICT in the psql eventsink insert functions (#6556 )	3 years ago
JayT106	711a718162	config/indexer: custom event indexing (#6411 )	4 years ago

2 Commits (540aea1030c7cabf4b710da5f6d323d8dfa00654)