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

trigger.c

Blame
    • Robert Haas's avatar
      8e18d04d
      Refine our definition of what constitutes a system relation. · 8e18d04d
      Robert Haas authored
      Although user-defined relations can't be directly created in
      pg_catalog, it's possible for them to end up there, because you can
      create them in some other schema and then use ALTER TABLE .. SET SCHEMA
      to move them there.  Previously, such relations couldn't afterwards
      be manipulated, because IsSystemRelation()/IsSystemClass() rejected
      all attempts to modify objects in the pg_catalog schema, regardless
      of their origin.  With this patch, they now reject only those
      objects in pg_catalog which were created at initdb-time, allowing
      most operations on user-created tables in pg_catalog to proceed
      normally.
      
      This patch also adds new functions IsCatalogRelation() and
      IsCatalogClass(), which is similar to IsSystemRelation() and
      IsSystemClass() but with a slightly narrower definition: only TOAST
      tables of system catalogs are included, rather than *all* TOAST tables.
      This is currently used only for making decisions about when
      invalidation messages need to be sent, but upcoming logical decoding
      patches will find other uses for this information.
      
      Andres Freund, with some modifications by me.
      8e18d04d
      History
      Refine our definition of what constitutes a system relation.
      Robert Haas authored
      Although user-defined relations can't be directly created in
      pg_catalog, it's possible for them to end up there, because you can
      create them in some other schema and then use ALTER TABLE .. SET SCHEMA
      to move them there.  Previously, such relations couldn't afterwards
      be manipulated, because IsSystemRelation()/IsSystemClass() rejected
      all attempts to modify objects in the pg_catalog schema, regardless
      of their origin.  With this patch, they now reject only those
      objects in pg_catalog which were created at initdb-time, allowing
      most operations on user-created tables in pg_catalog to proceed
      normally.
      
      This patch also adds new functions IsCatalogRelation() and
      IsCatalogClass(), which is similar to IsSystemRelation() and
      IsSystemClass() but with a slightly narrower definition: only TOAST
      tables of system catalogs are included, rather than *all* TOAST tables.
      This is currently used only for making decisions about when
      invalidation messages need to be sent, but upcoming logical decoding
      patches will find other uses for this information.
      
      Andres Freund, with some modifications by me.