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

postgres-lambda-diff

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Tom Lane authored
    When we implemented extensions, we made findDependentObjects() treat
    EXTENSION dependency links similarly to INTERNAL links.  However, that
    logic contained an implicit assumption that an object could have at most
    one INTERNAL dependency, so it did not work correctly for objects having
    both INTERNAL and DEPENDENCY links.  This led to failure to drop some
    extension member objects when dropping the extension.  Furthermore, we'd
    never actually exercised the case of recursing to an internally-referenced
    (owning) object from anything other than a NORMAL dependency, and it turns
    out that passing the incoming dependency's flags to the owning object is
    the Wrong Thing.  This led to sometimes dropping a whole extension silently
    when we should have rejected the drop command for lack of CASCADE.
    
    Since we obviously were under-testing extension drop scenarios, add some
    regression test cases.  Unfortunately, such test cases require some
    extensions (duh), so we can't test for problems in the core regression
    tests.  I chose to add them to the earthdistance contrib module, which is
    a good test case because it has a dependency on the cube contrib module.
    
    Back-patch to 9.1.  Arguably these are pre-existing bugs in INTERNAL
    dependency handling, but since it appears that the cases can never arise
    pre-9.1, I'll refrain from back-patching the logic changes further than
    that.
    cb5c2ba2
    History
    PostgreSQL Database Management System
    =====================================
    
    This directory contains the source code distribution of the PostgreSQL
    database management system.
    
    PostgreSQL is an advanced object-relational database management system
    that supports an extended subset of the SQL standard, including
    transactions, foreign keys, subqueries, triggers, user-defined types
    and functions.  This distribution also contains C language bindings.
    
    PostgreSQL has many language interfaces, many of which are listed here:
    
    	http://www.postgresql.org/download
    
    See the file INSTALL for instructions on how to build and install
    PostgreSQL.  That file also lists supported operating systems and
    hardware platforms and contains information regarding any other
    software packages that are required to build or run the PostgreSQL
    system.  Changes between all PostgreSQL releases are recorded in the
    file HISTORY.  Copyright and license information can be found in the
    file COPYRIGHT.  A comprehensive documentation set is included in this
    distribution; it can be read as described in the installation
    instructions.
    
    The latest version of this software may be obtained at
    http://www.postgresql.org/download/.  For more information look at our
    web site located at http://www.postgresql.org/.