Replace our traditional initial-catalog-data format with a better design.
Historically, the initial catalog data to be installed during bootstrap
has been written in DATA() lines in the catalog header files. This had
lots of disadvantages: the format was badly underdocumented, it was
very difficult to edit the data in any mechanized way, and due to the
lack of any abstraction the data was verbose, hard to read/understand,
and easy to get wrong.
Hence, move this data into separate ".dat" files and represent it in a way
that can easily be read and rewritten by Perl scripts. The new format is
essentially "key => value" for each column; while it's a bit repetitive,
explicit labeling of each value makes the data far more readable and less
error-prone. Provide a way to abbreviate entries by omitting field values
that match a specified default value for their column. This allows removal
of a large amount of repetitive boilerplate and also lowers the barrier to
adding new columns.
Also teach genbki.pl how to translate symbolic OID references into
numeric OIDs for more cases than just "regproc"-like pg_proc references.
It can now do that for regprocedure-like references (thus solving the
problem that regproc is ambiguous for overloaded functions), operators,
types, opfamilies, opclasses, and access methods. Use this to turn
nearly all OID cross-references in the initial data into symbolic form.
This represents a very large step forward in readability and error
resistance of the initial catalog data. It should also reduce the
difficulty of renumbering OID assignments in uncommitted patches.
Also, solve the longstanding problem that frontend code that would like to
use OID macros and other information from the catalog headers often had
difficulty with backend-only code in the headers. To do this, arrange for
all generated macros, plus such other declarations as we deem fit, to be
placed in "derived" header files that are safe for frontend inclusion.
(Once clients migrate to using these pg_*_d.h headers, it will be possible
to get rid of the pg_*_fn.h headers, which only exist to quarantine code
away from clients. That is left for follow-on patches, however.)
The now-automatically-generated macros include the Anum_xxx and Natts_xxx
constants that we used to have to update by hand when adding or removing
catalog columns.
Replace the former manual method of generating OID macros for pg_type
entries with an automatic method, ensuring that all built-in types have
OID macros. (But note that this patch does not change the way that
OID macros for pg_proc entries are built and used. It's not clear that
making that match the other catalogs would be worth extra code churn.)
Add SGML documentation explaining what the new data format is and how to
work with it.
Despite being a very large change in the catalog headers, there is no
catversion bump here, because postgres.bki and related output files
haven't changed at all.
John Naylor, based on ideas from various people; review and minor
additional coding by me; previous review by Alvaro Herrera
Discussion: https://postgr.es/m/CAJVSVGWO48JbbwXkJz_yBFyGYW-M9YWxnPdxJBUosDC9ou_F0Q@mail.gmail.com
2018-04-08 19:16:50 +02:00
|
|
|
#-------------------------------------------------------------------------
|
|
|
|
|
#
|
|
|
|
|
# Makefile for src/include/catalog
|
|
|
|
|
#
|
2024-01-04 02:49:05 +01:00
|
|
|
# Portions Copyright (c) 1996-2024, PostgreSQL Global Development Group
|
Replace our traditional initial-catalog-data format with a better design.
Historically, the initial catalog data to be installed during bootstrap
has been written in DATA() lines in the catalog header files. This had
lots of disadvantages: the format was badly underdocumented, it was
very difficult to edit the data in any mechanized way, and due to the
lack of any abstraction the data was verbose, hard to read/understand,
and easy to get wrong.
Hence, move this data into separate ".dat" files and represent it in a way
that can easily be read and rewritten by Perl scripts. The new format is
essentially "key => value" for each column; while it's a bit repetitive,
explicit labeling of each value makes the data far more readable and less
error-prone. Provide a way to abbreviate entries by omitting field values
that match a specified default value for their column. This allows removal
of a large amount of repetitive boilerplate and also lowers the barrier to
adding new columns.
Also teach genbki.pl how to translate symbolic OID references into
numeric OIDs for more cases than just "regproc"-like pg_proc references.
It can now do that for regprocedure-like references (thus solving the
problem that regproc is ambiguous for overloaded functions), operators,
types, opfamilies, opclasses, and access methods. Use this to turn
nearly all OID cross-references in the initial data into symbolic form.
This represents a very large step forward in readability and error
resistance of the initial catalog data. It should also reduce the
difficulty of renumbering OID assignments in uncommitted patches.
Also, solve the longstanding problem that frontend code that would like to
use OID macros and other information from the catalog headers often had
difficulty with backend-only code in the headers. To do this, arrange for
all generated macros, plus such other declarations as we deem fit, to be
placed in "derived" header files that are safe for frontend inclusion.
(Once clients migrate to using these pg_*_d.h headers, it will be possible
to get rid of the pg_*_fn.h headers, which only exist to quarantine code
away from clients. That is left for follow-on patches, however.)
The now-automatically-generated macros include the Anum_xxx and Natts_xxx
constants that we used to have to update by hand when adding or removing
catalog columns.
Replace the former manual method of generating OID macros for pg_type
entries with an automatic method, ensuring that all built-in types have
OID macros. (But note that this patch does not change the way that
OID macros for pg_proc entries are built and used. It's not clear that
making that match the other catalogs would be worth extra code churn.)
Add SGML documentation explaining what the new data format is and how to
work with it.
Despite being a very large change in the catalog headers, there is no
catversion bump here, because postgres.bki and related output files
haven't changed at all.
John Naylor, based on ideas from various people; review and minor
additional coding by me; previous review by Alvaro Herrera
Discussion: https://postgr.es/m/CAJVSVGWO48JbbwXkJz_yBFyGYW-M9YWxnPdxJBUosDC9ou_F0Q@mail.gmail.com
2018-04-08 19:16:50 +02:00
|
|
|
# Portions Copyright (c) 1994, Regents of the University of California
|
|
|
|
|
#
|
|
|
|
|
# src/include/catalog/Makefile
|
|
|
|
|
#
|
|
|
|
|
#-------------------------------------------------------------------------
|
|
|
|
|
|
|
|
|
|
subdir = src/include/catalog
|
|
|
|
|
top_builddir = ../../..
|
|
|
|
|
include $(top_builddir)/src/Makefile.global
|
|
|
|
|
|
2024-03-14 06:57:16 +01:00
|
|
|
# Note: the order of this list determines the order in which the catalog
|
|
|
|
|
# header files are assembled into postgres.bki. BKI_BOOTSTRAP catalogs
|
|
|
|
|
# must appear first, and pg_statistic before pg_statistic_ext_data, and
|
|
|
|
|
# there are reputedly other, undocumented ordering dependencies.
|
|
|
|
|
CATALOG_HEADERS := \
|
|
|
|
|
pg_proc.h \
|
|
|
|
|
pg_type.h \
|
|
|
|
|
pg_attribute.h \
|
|
|
|
|
pg_class.h \
|
|
|
|
|
pg_attrdef.h \
|
|
|
|
|
pg_constraint.h \
|
|
|
|
|
pg_inherits.h \
|
|
|
|
|
pg_index.h \
|
|
|
|
|
pg_operator.h \
|
|
|
|
|
pg_opfamily.h \
|
|
|
|
|
pg_opclass.h \
|
|
|
|
|
pg_am.h \
|
|
|
|
|
pg_amop.h \
|
|
|
|
|
pg_amproc.h \
|
|
|
|
|
pg_language.h \
|
|
|
|
|
pg_largeobject_metadata.h \
|
|
|
|
|
pg_largeobject.h \
|
|
|
|
|
pg_aggregate.h \
|
|
|
|
|
pg_statistic.h \
|
|
|
|
|
pg_statistic_ext.h \
|
|
|
|
|
pg_statistic_ext_data.h \
|
|
|
|
|
pg_rewrite.h \
|
|
|
|
|
pg_trigger.h \
|
|
|
|
|
pg_event_trigger.h \
|
|
|
|
|
pg_description.h \
|
|
|
|
|
pg_cast.h \
|
|
|
|
|
pg_enum.h \
|
|
|
|
|
pg_namespace.h \
|
|
|
|
|
pg_conversion.h \
|
|
|
|
|
pg_depend.h \
|
|
|
|
|
pg_database.h \
|
|
|
|
|
pg_db_role_setting.h \
|
|
|
|
|
pg_tablespace.h \
|
|
|
|
|
pg_authid.h \
|
|
|
|
|
pg_auth_members.h \
|
|
|
|
|
pg_shdepend.h \
|
|
|
|
|
pg_shdescription.h \
|
|
|
|
|
pg_ts_config.h \
|
|
|
|
|
pg_ts_config_map.h \
|
|
|
|
|
pg_ts_dict.h \
|
|
|
|
|
pg_ts_parser.h \
|
|
|
|
|
pg_ts_template.h \
|
|
|
|
|
pg_extension.h \
|
|
|
|
|
pg_foreign_data_wrapper.h \
|
|
|
|
|
pg_foreign_server.h \
|
|
|
|
|
pg_user_mapping.h \
|
|
|
|
|
pg_foreign_table.h \
|
|
|
|
|
pg_policy.h \
|
|
|
|
|
pg_replication_origin.h \
|
|
|
|
|
pg_default_acl.h \
|
|
|
|
|
pg_init_privs.h \
|
|
|
|
|
pg_seclabel.h \
|
|
|
|
|
pg_shseclabel.h \
|
|
|
|
|
pg_collation.h \
|
|
|
|
|
pg_parameter_acl.h \
|
|
|
|
|
pg_partitioned_table.h \
|
|
|
|
|
pg_range.h \
|
|
|
|
|
pg_transform.h \
|
|
|
|
|
pg_sequence.h \
|
|
|
|
|
pg_publication.h \
|
|
|
|
|
pg_publication_namespace.h \
|
|
|
|
|
pg_publication_rel.h \
|
|
|
|
|
pg_subscription.h \
|
|
|
|
|
pg_subscription_rel.h
|
|
|
|
|
|
|
|
|
|
GENERATED_HEADERS := $(CATALOG_HEADERS:%.h=%_d.h)
|
|
|
|
|
|
|
|
|
|
POSTGRES_BKI_SRCS := $(addprefix $(top_srcdir)/src/include/catalog/, $(CATALOG_HEADERS))
|
|
|
|
|
|
|
|
|
|
# The .dat files we need can just be listed alphabetically.
|
|
|
|
|
POSTGRES_BKI_DATA = \
|
|
|
|
|
pg_aggregate.dat \
|
|
|
|
|
pg_am.dat \
|
|
|
|
|
pg_amop.dat \
|
|
|
|
|
pg_amproc.dat \
|
|
|
|
|
pg_authid.dat \
|
|
|
|
|
pg_cast.dat \
|
|
|
|
|
pg_class.dat \
|
|
|
|
|
pg_collation.dat \
|
|
|
|
|
pg_conversion.dat \
|
|
|
|
|
pg_database.dat \
|
|
|
|
|
pg_language.dat \
|
|
|
|
|
pg_namespace.dat \
|
|
|
|
|
pg_opclass.dat \
|
|
|
|
|
pg_operator.dat \
|
|
|
|
|
pg_opfamily.dat \
|
|
|
|
|
pg_proc.dat \
|
|
|
|
|
pg_range.dat \
|
|
|
|
|
pg_tablespace.dat \
|
|
|
|
|
pg_ts_config.dat \
|
|
|
|
|
pg_ts_config_map.dat \
|
|
|
|
|
pg_ts_dict.dat \
|
|
|
|
|
pg_ts_parser.dat \
|
|
|
|
|
pg_ts_template.dat \
|
|
|
|
|
pg_type.dat
|
|
|
|
|
|
|
|
|
|
GENBKI_OUTPUT_FILES = \
|
|
|
|
|
$(GENERATED_HEADERS) \
|
|
|
|
|
postgres.bki \
|
|
|
|
|
system_constraints.sql \
|
|
|
|
|
schemapg.h \
|
|
|
|
|
syscache_ids.h \
|
|
|
|
|
syscache_info.h \
|
|
|
|
|
system_fk_info.h
|
|
|
|
|
|
|
|
|
|
all: generated-headers
|
|
|
|
|
|
|
|
|
|
.PHONY: generated-headers
|
|
|
|
|
|
|
|
|
|
generated-headers: bki-stamp
|
|
|
|
|
|
|
|
|
|
# bki-stamp records the last time we ran genbki.pl. We don't rely on
|
|
|
|
|
# the timestamps of the individual output files, because the Perl script
|
|
|
|
|
# won't update them if they didn't change (to avoid unnecessary recompiles).
|
|
|
|
|
# Technically, this should depend on Makefile.global which supplies
|
|
|
|
|
# $(MAJORVERSION); but then genbki.pl would need to be re-run after every
|
|
|
|
|
# configure run, even in distribution tarballs. So depending on configure.ac
|
|
|
|
|
# instead is cheating a bit, but it will achieve the goal of updating the
|
|
|
|
|
# version number when it changes.
|
|
|
|
|
bki-stamp: $(top_srcdir)/src/backend/catalog/genbki.pl $(top_srcdir)/src/backend/catalog/Catalog.pm $(POSTGRES_BKI_SRCS) $(POSTGRES_BKI_DATA) $(top_srcdir)/configure.ac $(top_srcdir)/src/include/access/transam.h
|
|
|
|
|
$(PERL) $< --include-path=$(top_srcdir)/src/include/ \
|
|
|
|
|
--set-version=$(MAJORVERSION) $(POSTGRES_BKI_SRCS)
|
|
|
|
|
touch $@
|
|
|
|
|
|
|
|
|
|
install: all installdirs
|
|
|
|
|
$(INSTALL_DATA) postgres.bki '$(DESTDIR)$(datadir)/postgres.bki'
|
|
|
|
|
$(INSTALL_DATA) system_constraints.sql '$(DESTDIR)$(datadir)/system_constraints.sql'
|
|
|
|
|
# In non-vpath builds, src/include/Makefile already installs all headers.
|
|
|
|
|
ifeq ($(vpath_build),yes)
|
|
|
|
|
$(INSTALL_DATA) schemapg.h '$(DESTDIR)$(includedir_server)'/catalog/schemapg.h
|
|
|
|
|
$(INSTALL_DATA) syscache_ids.h '$(DESTDIR)$(includedir_server)'/catalog/syscache_ids.h
|
|
|
|
|
$(INSTALL_DATA) system_fk_info.h '$(DESTDIR)$(includedir_server)'/catalog/system_fk_info.h
|
|
|
|
|
for file in $(GENERATED_HEADERS); do \
|
|
|
|
|
$(INSTALL_DATA) $$file '$(DESTDIR)$(includedir_server)'/catalog/$$file || exit; \
|
|
|
|
|
done
|
|
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
installdirs:
|
|
|
|
|
$(MKDIR_P) '$(DESTDIR)$(datadir)' '$(DESTDIR)$(includedir_server)'
|
|
|
|
|
|
|
|
|
|
uninstall:
|
|
|
|
|
rm -f $(addprefix '$(DESTDIR)$(datadir)'/, postgres.bki system_constraints.sql)
|
|
|
|
|
rm -f $(addprefix '$(DESTDIR)$(includedir_server)'/catalog/, schemapg.h syscache_ids.h system_fk_info.h $(GENERATED_HEADERS))
|
|
|
|
|
|
|
|
|
|
clean:
|
|
|
|
|
rm -f bki-stamp $(GENBKI_OUTPUT_FILES)
|
|
|
|
|
|
Replace our traditional initial-catalog-data format with a better design.
Historically, the initial catalog data to be installed during bootstrap
has been written in DATA() lines in the catalog header files. This had
lots of disadvantages: the format was badly underdocumented, it was
very difficult to edit the data in any mechanized way, and due to the
lack of any abstraction the data was verbose, hard to read/understand,
and easy to get wrong.
Hence, move this data into separate ".dat" files and represent it in a way
that can easily be read and rewritten by Perl scripts. The new format is
essentially "key => value" for each column; while it's a bit repetitive,
explicit labeling of each value makes the data far more readable and less
error-prone. Provide a way to abbreviate entries by omitting field values
that match a specified default value for their column. This allows removal
of a large amount of repetitive boilerplate and also lowers the barrier to
adding new columns.
Also teach genbki.pl how to translate symbolic OID references into
numeric OIDs for more cases than just "regproc"-like pg_proc references.
It can now do that for regprocedure-like references (thus solving the
problem that regproc is ambiguous for overloaded functions), operators,
types, opfamilies, opclasses, and access methods. Use this to turn
nearly all OID cross-references in the initial data into symbolic form.
This represents a very large step forward in readability and error
resistance of the initial catalog data. It should also reduce the
difficulty of renumbering OID assignments in uncommitted patches.
Also, solve the longstanding problem that frontend code that would like to
use OID macros and other information from the catalog headers often had
difficulty with backend-only code in the headers. To do this, arrange for
all generated macros, plus such other declarations as we deem fit, to be
placed in "derived" header files that are safe for frontend inclusion.
(Once clients migrate to using these pg_*_d.h headers, it will be possible
to get rid of the pg_*_fn.h headers, which only exist to quarantine code
away from clients. That is left for follow-on patches, however.)
The now-automatically-generated macros include the Anum_xxx and Natts_xxx
constants that we used to have to update by hand when adding or removing
catalog columns.
Replace the former manual method of generating OID macros for pg_type
entries with an automatic method, ensuring that all built-in types have
OID macros. (But note that this patch does not change the way that
OID macros for pg_proc entries are built and used. It's not clear that
making that match the other catalogs would be worth extra code churn.)
Add SGML documentation explaining what the new data format is and how to
work with it.
Despite being a very large change in the catalog headers, there is no
catversion bump here, because postgres.bki and related output files
haven't changed at all.
John Naylor, based on ideas from various people; review and minor
additional coding by me; previous review by Alvaro Herrera
Discussion: https://postgr.es/m/CAJVSVGWO48JbbwXkJz_yBFyGYW-M9YWxnPdxJBUosDC9ou_F0Q@mail.gmail.com
2018-04-08 19:16:50 +02:00
|
|
|
# 'make reformat-dat-files' is a convenience target for rewriting the
|
|
|
|
|
# catalog data files in our standard format. This includes collapsing
|
|
|
|
|
# out any entries that are redundant with a BKI_DEFAULT annotation.
|
|
|
|
|
reformat-dat-files:
|
2019-03-08 17:48:49 +01:00
|
|
|
$(PERL) $(srcdir)/reformat_dat_file.pl --output $(srcdir) $(srcdir)/pg_*.dat
|
Replace our traditional initial-catalog-data format with a better design.
Historically, the initial catalog data to be installed during bootstrap
has been written in DATA() lines in the catalog header files. This had
lots of disadvantages: the format was badly underdocumented, it was
very difficult to edit the data in any mechanized way, and due to the
lack of any abstraction the data was verbose, hard to read/understand,
and easy to get wrong.
Hence, move this data into separate ".dat" files and represent it in a way
that can easily be read and rewritten by Perl scripts. The new format is
essentially "key => value" for each column; while it's a bit repetitive,
explicit labeling of each value makes the data far more readable and less
error-prone. Provide a way to abbreviate entries by omitting field values
that match a specified default value for their column. This allows removal
of a large amount of repetitive boilerplate and also lowers the barrier to
adding new columns.
Also teach genbki.pl how to translate symbolic OID references into
numeric OIDs for more cases than just "regproc"-like pg_proc references.
It can now do that for regprocedure-like references (thus solving the
problem that regproc is ambiguous for overloaded functions), operators,
types, opfamilies, opclasses, and access methods. Use this to turn
nearly all OID cross-references in the initial data into symbolic form.
This represents a very large step forward in readability and error
resistance of the initial catalog data. It should also reduce the
difficulty of renumbering OID assignments in uncommitted patches.
Also, solve the longstanding problem that frontend code that would like to
use OID macros and other information from the catalog headers often had
difficulty with backend-only code in the headers. To do this, arrange for
all generated macros, plus such other declarations as we deem fit, to be
placed in "derived" header files that are safe for frontend inclusion.
(Once clients migrate to using these pg_*_d.h headers, it will be possible
to get rid of the pg_*_fn.h headers, which only exist to quarantine code
away from clients. That is left for follow-on patches, however.)
The now-automatically-generated macros include the Anum_xxx and Natts_xxx
constants that we used to have to update by hand when adding or removing
catalog columns.
Replace the former manual method of generating OID macros for pg_type
entries with an automatic method, ensuring that all built-in types have
OID macros. (But note that this patch does not change the way that
OID macros for pg_proc entries are built and used. It's not clear that
making that match the other catalogs would be worth extra code churn.)
Add SGML documentation explaining what the new data format is and how to
work with it.
Despite being a very large change in the catalog headers, there is no
catversion bump here, because postgres.bki and related output files
haven't changed at all.
John Naylor, based on ideas from various people; review and minor
additional coding by me; previous review by Alvaro Herrera
Discussion: https://postgr.es/m/CAJVSVGWO48JbbwXkJz_yBFyGYW-M9YWxnPdxJBUosDC9ou_F0Q@mail.gmail.com
2018-04-08 19:16:50 +02:00
|
|
|
|
|
|
|
|
# 'make expand-dat-files' is a convenience target for expanding out all
|
|
|
|
|
# default values in the catalog data files. This should be run before
|
|
|
|
|
# altering or removing any BKI_DEFAULT annotation.
|
|
|
|
|
expand-dat-files:
|
2019-03-08 17:48:49 +01:00
|
|
|
$(PERL) $(srcdir)/reformat_dat_file.pl --output $(srcdir) $(srcdir)/pg_*.dat --full-tuples
|
Replace our traditional initial-catalog-data format with a better design.
Historically, the initial catalog data to be installed during bootstrap
has been written in DATA() lines in the catalog header files. This had
lots of disadvantages: the format was badly underdocumented, it was
very difficult to edit the data in any mechanized way, and due to the
lack of any abstraction the data was verbose, hard to read/understand,
and easy to get wrong.
Hence, move this data into separate ".dat" files and represent it in a way
that can easily be read and rewritten by Perl scripts. The new format is
essentially "key => value" for each column; while it's a bit repetitive,
explicit labeling of each value makes the data far more readable and less
error-prone. Provide a way to abbreviate entries by omitting field values
that match a specified default value for their column. This allows removal
of a large amount of repetitive boilerplate and also lowers the barrier to
adding new columns.
Also teach genbki.pl how to translate symbolic OID references into
numeric OIDs for more cases than just "regproc"-like pg_proc references.
It can now do that for regprocedure-like references (thus solving the
problem that regproc is ambiguous for overloaded functions), operators,
types, opfamilies, opclasses, and access methods. Use this to turn
nearly all OID cross-references in the initial data into symbolic form.
This represents a very large step forward in readability and error
resistance of the initial catalog data. It should also reduce the
difficulty of renumbering OID assignments in uncommitted patches.
Also, solve the longstanding problem that frontend code that would like to
use OID macros and other information from the catalog headers often had
difficulty with backend-only code in the headers. To do this, arrange for
all generated macros, plus such other declarations as we deem fit, to be
placed in "derived" header files that are safe for frontend inclusion.
(Once clients migrate to using these pg_*_d.h headers, it will be possible
to get rid of the pg_*_fn.h headers, which only exist to quarantine code
away from clients. That is left for follow-on patches, however.)
The now-automatically-generated macros include the Anum_xxx and Natts_xxx
constants that we used to have to update by hand when adding or removing
catalog columns.
Replace the former manual method of generating OID macros for pg_type
entries with an automatic method, ensuring that all built-in types have
OID macros. (But note that this patch does not change the way that
OID macros for pg_proc entries are built and used. It's not clear that
making that match the other catalogs would be worth extra code churn.)
Add SGML documentation explaining what the new data format is and how to
work with it.
Despite being a very large change in the catalog headers, there is no
catversion bump here, because postgres.bki and related output files
haven't changed at all.
John Naylor, based on ideas from various people; review and minor
additional coding by me; previous review by Alvaro Herrera
Discussion: https://postgr.es/m/CAJVSVGWO48JbbwXkJz_yBFyGYW-M9YWxnPdxJBUosDC9ou_F0Q@mail.gmail.com
2018-04-08 19:16:50 +02:00
|
|
|
|
|
|
|
|
.PHONY: reformat-dat-files expand-dat-files
|
