)]}'
{
  "commit": "e66d65ce4c900961985e8ba767fbaa8363ccfce7",
  "tree": "7b8f9504191dcb374bff8c5c0eddf6d1728049c8",
  "parents": [
    "a4d181e67d5a1a6633219206f4f17632eac0d0d8"
  ],
  "author": {
    "name": "Tomas Vondra",
    "email": "tomas.vondra@postgresql.org",
    "time": "Mon Aug 19 00:04:41 2024 +0200"
  },
  "committer": {
    "name": "reshke",
    "email": "reshkekirill@gmail.com",
    "time": "Thu Aug 27 13:10:10 2026 +0500"
  },
  "message": "Fix DROP DATABASE for databases with many ACLs\n\nCommit c66a7d75e652 modified DROP DATABASE so that if interrupted, the\ndatabase is known to be in an invalid state and can only be dropped.\nThis is done by setting a flag using an in-place update, so that it\u0027s\nnot lost in case of rollback.\n\nFor databases with many ACLs, this may however fail like this:\n\n  ERROR:  wrong tuple length\n\nThis happens because with many ACLs, the pg_database.datacl attribute\ngets TOASTed. The dropdb() code reads the tuple from the syscache, which\nmeans it\u0027s detoasted. But the in-place update expects the tuple length\nto match the on-disk tuple.\n\nFixed by reading the tuple from the catalog directly, not from syscache.\n\nReport and fix by Ayush Tiwari. Backpatch to 12. The DROP DATABASE fix\nwas backpatched to 11, but 11 is EOL at this point.\n\nReported-by: Ayush Tiwari\nAuthor: Ayush Tiwari\nReviewed-by: Tomas Vondra\nBackpatch-through: 12\nDiscussion: https://postgr.es/m/CAJTYsWWNkCt+-UnMhg\u003dBiCD3Mh8c2JdHLofPxsW3m2dkDFw8RA@mail.gmail.com\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "2afd694a967d86608fe758fe9c3296c14bb7ad53",
      "old_mode": 33188,
      "old_path": "src/backend/commands/dbcommands.c",
      "new_id": "6ad0a791a1c9705c2ba75830bd5f9efa4ede7d83",
      "new_mode": 33188,
      "new_path": "src/backend/commands/dbcommands.c"
    }
  ]
}