Once a query fails as part of a transaction Postgres (unlike Mysql, SQLite and Oracle) will prevent further queries from using the transaction. See https://stackoverflow.com/questions/10399727/psqlexception-current-trans... for more information about how postgres behaves. Allowing inserts to fail within a transaction is especially important because of the way we automatically create cache bins on demand - see \Drupal\Core\Cache\DatabaseBackend for how this works.
Add a savepoint to the postgres insert query - this is already done for other query types, for example, updates and selects.
None
None
None
PDO randomly throws errors for any table (mostly seen for queue and flood during normal site operation) when using PGBouncer in transaction mode on PostgreSQL:
PDOException: SQLSTATE[55000]: Object not in prerequisite state: 7 ERROR: currval of sequence "queue_item_id_seq" is not yet defined in this session: INSERT INTO queue (name, data, created) VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2);
When doing lots of inserts (e.g. setting up a new site) it will break the installation.
Fixed
8.0 ⚰️
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I have created a D7 issue for backporting this: 🐛 [D7] PostgreSQL queries that fail in a transaction break the entire transaction Needs review
Closing as Fixed for D8, so that credits get assigned.
Automatically closed - issue fixed for 2 weeks with no activity.