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

adt

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Bruce Momjian authored
    Here's the multibyte aware version of my patch to fix the truncation
    of the rulename autogenerated during a CREATE VIEW. I've modified all
    the places in the backend that want to construct the rulename to use
    the MakeRetrieveViewRuleName(), where I put the #ifdef MULTIBYTE, so
    that's the only place that knows how to construct a view rulename. Except
    pg_dump, where I replicated the code, since it's a standalone binary.
    
    The only effect the enduser will see is that views with names len(name)
    > NAMEDATALEN-4 will fail to be created, if the derived rulename clases
    with an existing rule: i.e. the user is trying to create two views with
    long names whose first difference is past NAMEDATALEN-4 (but before
    NAMEDATALEN: that'll error out after the viewname truncation.) In no
    case will the user get left with a table without a view rule, as the
    current code does.
    
    Ross Reedstrom
    0ba0e321
    History
    Name Last commit Last update
    ..