Skip to content
Snippets Groups Projects
Select Git revision
  • benchmark-tools
  • postgres-lambda
  • master default
  • REL9_4_25
  • REL9_5_20
  • REL9_6_16
  • REL_10_11
  • REL_11_6
  • REL_12_1
  • REL_12_0
  • REL_12_RC1
  • REL_12_BETA4
  • REL9_4_24
  • REL9_5_19
  • REL9_6_15
  • REL_10_10
  • REL_11_5
  • REL_12_BETA3
  • REL9_4_23
  • REL9_5_18
  • REL9_6_14
  • REL_10_9
  • REL_11_4
23 results

commands

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Tom Lane authored
    The original implementation simply did nothing when replacing an existing
    object during CREATE EXTENSION.  The folly of this was exposed by a report
    from Marc Munro: if the existing object belongs to another extension, we
    are left in an inconsistent state.  We should insist that the object does
    not belong to another extension, and then add it to the current extension
    if not already a member.
    988cccc6
    History
    Name Last commit Last update
    ..