1. 05 Sep, 2020 1 commit
  2. 04 Sep, 2020 14 commits
  3. 03 Sep, 2020 7 commits
  4. 02 Sep, 2020 7 commits
  5. 01 Sep, 2020 6 commits
    • Tom Lane's avatar
      Improve test coverage of ginvacuum.c. · 4c51a2d1
      Tom Lane authored
      Add a test case that exercises vacuum's deletion of empty GIN
      posting pages.  Since this is a temp table, it should now work
      reliably to delete a bunch of rows and immediately VACUUM.
      Before the preceding commit, this would not have had the desired
      effect, at least not in parallel regression tests.
      
      Discussion: https://postgr.es/m/3490536.1598629609@sss.pgh.pa.us
      4c51a2d1
    • Tom Lane's avatar
      Set cutoff xmin more aggressively when vacuuming a temporary table. · a7212be8
      Tom Lane authored
      Since other sessions aren't allowed to look into a temporary table
      of our own session, we do not need to worry about the global xmin
      horizon when setting the vacuum XID cutoff.  Indeed, if we're not
      inside a transaction block, we may set oldestXmin to be the next
      XID, because there cannot be any in-doubt tuples in a temp table,
      nor any tuples that are dead but still visible to some snapshot of
      our transaction.  (VACUUM, of course, is never inside a transaction
      block; but we need to test that because CLUSTER shares the same code.)
      
      This approach allows us to always clean out a temp table completely
      during VACUUM, independently of concurrent activity.  Aside from
      being useful in its own right, that simplifies building reproducible
      test cases.
      
      Discussion: https://postgr.es/m/3490536.1598629609@sss.pgh.pa.us
      a7212be8
    • Bruce Momjian's avatar
      doc: clarify that max_wal_size is "during" checkpoints · db864c3c
      Bruce Momjian authored
      Previous wording was "between".
      
      Reported-by: Pavel Luzanov
      
      Discussion: https://postgr.es/m/26906a54-d7cb-2f8e-eed7-e31660024694@postgrespro.ru
      
      Backpatch-through: 9.5
      db864c3c
    • Alvaro Herrera's avatar
      Raise error on concurrent drop of partitioned index · afc7e0ad
      Alvaro Herrera authored
      We were already raising an error for DROP INDEX CONCURRENTLY on a
      partitioned table, albeit a different and confusing one:
        ERROR:  DROP INDEX CONCURRENTLY must be first action in transaction
      
      Change that to throw a more comprehensible error:
        ERROR:  cannot drop partitioned index \"%s\" concurrently
      
      Michael Paquier authored the test case for indexes on temporary
      partitioned tables.
      
      Backpatch to 11, where indexes on partitioned tables were added.
      Reported-by: default avatarJan Mussler <jan.mussler@zalando.de>
      Reviewed-by: default avatarMichael Paquier <michael@paquier.xyz>
      Discussion: https://postgr.es/m/16594-d2956ca909585067@postgresql.org
      afc7e0ad
    • Tom Lane's avatar
      Teach libpq to handle arbitrary-length lines in .pgpass files. · b55b4dad
      Tom Lane authored
      Historically there's been a hard-wired assumption here that no line of
      a .pgpass file could be as long as NAMEDATALEN*5 bytes.  That's a bit
      shaky to start off with, because (a) there's no reason to suppose that
      host names fit in NAMEDATALEN, and (b) this figure fails to allow for
      backslash escape characters.  However, it fails completely if someone
      wants to use a very long password, and we're now hearing reports of
      people wanting to use "security tokens" that can run up to several
      hundred bytes.  Another angle is that the file is specified to allow
      comment lines, but there's no reason to assume that long comment lines
      aren't possible.
      
      Rather than guessing at what might be a more suitable limit, let's
      replace the fixed-size buffer with an expansible PQExpBuffer.  That
      adds one malloc/free cycle to the typical use-case, but that's surely
      pretty cheap relative to the I/O this code has to do.
      
      Also, add TAP test cases to exercise this code, because there was no
      test coverage before.
      
      This reverts most of commit 2eb3bc58, as there's no longer a need for
      a warning message about overlength .pgpass lines.  (I kept the explicit
      check for comment lines, though.)
      
      In HEAD and v13, this also fixes an oversight in 74a308cf: there's not
      much point in explicit_bzero'ing the line buffer if we only do so in two
      of the three exit paths.
      
      Back-patch to all supported branches, except that the test case only
      goes back to v10 where src/test/authentication/ was added.
      
      Discussion: https://postgr.es/m/4187382.1598909041@sss.pgh.pa.us
      b55b4dad
    • Amit Kapila's avatar
      Fix the SharedFileSetUnregister API. · 4ab77697
      Amit Kapila authored
      Commit 808e13b2 introduced a few APIs to extend the existing Buffile
      interface. In SharedFileSetDeleteOnProcExit, it tries to delete the list
      element while traversing the list with 'foreach' construct which makes the
      behavior of list traversal unpredictable.
      
      Author: Amit Kapila
      Reviewed-by: Dilip Kumar
      Tested-by: Dilip Kumar and Neha Sharma
      Discussion: https://postgr.es/m/CAA4eK1JhLatVcQ2OvwA_3s0ih6Hx9+kZbq107cXVsSWWukH7vA@mail.gmail.com
      4ab77697
  6. 31 Aug, 2020 5 commits