Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-8776

Setting a read timestamp after prepare panics

    XMLWordPrintable

Details

    Description

      If you try to set a read timestamp after preparing a transaction, it is not prohibited (timestamp_transaction is allowed at this stage so the commit timestamp can be set) but fails, and this causes a panic.

      This is a silly thing to do and ideally it would be prohibited, since the number of paths that can lead to an application-triggered panic should be minimized, but the API-level infrastructure for prohibiting operations doesn't extend to examining config strings. So I'm not sure what the right approach is.

      Attachments

        Activity

          People

            keith.bostic@mongodb.com Keith Bostic (Inactive)
            dholland+wt@sauclovia.org David Holland
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: