aboutsummaryrefslogtreecommitdiff
path: root/src/backend/commands/trigger.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>1999-10-24 20:42:27 +0000
committerTom Lane <tgl@sss.pgh.pa.us>1999-10-24 20:42:27 +0000
commiteae456cd7fcdc5de759b38ef1d114f7770775483 (patch)
tree90eca5dde475dba1366ab7f770109272b86fc9b6 /src/backend/commands/trigger.c
parent9efee18a28ddacaf63d2fec3f1ea93325e8b6792 (diff)
downloadpostgresql-eae456cd7fcdc5de759b38ef1d114f7770775483.tar.gz
postgresql-eae456cd7fcdc5de759b38ef1d114f7770775483.zip
Add a notion of a 'catalog version number' that can indicate
when an initdb-forcing change has been applied within a development cycle. PG_VERSION serves this purpose for official releases, but we can't bump the PG_VERSION number every time we make a change to the catalogs during development. Instead, increase the catalog version number to warn other developers that you've made an incompatible change. See my mail to pghackers for more info.
Diffstat (limited to 'src/backend/commands/trigger.c')
0 files changed, 0 insertions, 0 deletions