The catalog pg_type stores information about data types. Base types and enum types (scalar types) are created with CREATE TYPE, and domains with CREATE DOMAIN. A composite type is automatically created for each table in the database, to represent the row structure of the table. It is also possible to create composite types with CREATE TYPE AS. Table 50-55. pg_type Columns Name Type References Description oid oid Row identifier (hidden attribute; must be explicitly selected) typname name D

The pg_ts_template catalog contains entries defining text search templates. A template is the implementation skeleton for a class of text search dictionaries. Since a template must be implemented by C-language-level functions, creation of new templates is restricted to database superusers. PostgreSQL's text search features are described at length in Chapter 12. Table 50-54. pg_ts_template Columns Name Type References Description oid oid Row identifier (hidden attribute; must be explicitly s

The pg_ts_parser catalog contains entries defining text search parsers. A parser is responsible for splitting input text into lexemes and assigning a token type to each lexeme. Since a parser must be implemented by C-language-level functions, creation of new parsers is restricted to database superusers. PostgreSQL's text search features are described at length in Chapter 12. Table 50-53. pg_ts_parser Columns Name Type References Description oid oid Row identifier (hidden attribute; must be

The pg_ts_dict catalog contains entries defining text search dictionaries. A dictionary depends on a text search template, which specifies all the implementation functions needed; the dictionary itself provides values for the user-settable parameters supported by the template. This division of labor allows dictionaries to be created by unprivileged users. The parameters are specified by a text string dictinitoption, whose format and meaning vary depending on the template. PostgreSQL's text sear

The pg_ts_config_map catalog contains entries showing which text search dictionaries should be consulted, and in what order, for each output token type of each text search configuration's parser. PostgreSQL's text search features are described at length in Chapter 12. Table 50-51. pg_ts_config_map Columns Name Type References Description mapcfg oid pg_ts_config.oid The OID of the pg_ts_config entry owning this map entry maptokentype integer A token type emitted by the configuration's parser

The pg_ts_config catalog contains entries representing text search configurations. A configuration specifies a particular text search parser and a list of dictionaries to use for each of the parser's output token types. The parser is shown in the pg_ts_config entry, but the token-to-dictionary mapping is defined by subsidiary entries in pg_ts_config_map. PostgreSQL's text search features are described at length in Chapter 12. Table 50-50. pg_ts_config Columns Name Type References Description

The catalog pg_trigger stores triggers on tables and views. See CREATE TRIGGER for more information. Table 50-49. pg_trigger Columns Name Type References Description oid oid Row identifier (hidden attribute; must be explicitly selected) tgrelid oid pg_class.oid The table this trigger is on tgname name Trigger name (must be unique among triggers of same table) tgfoid oid pg_proc.oid The function to be called tgtype int2 Bit mask identifying trigger firing conditions tgenabled char Cont

The catalog pg_transform stores information about transforms, which are a mechanism to adapt data types to procedural languages. See CREATE TRANSFORM for more information. Table 50-48. pg_transform Columns Name Type References Description trftype oid pg_type.oid OID of the data type this transform is for trflang oid pg_language.oid OID of the language this transform is for trffromsql regproc pg_proc.oid The OID of the function to use when converting the data type for input to the procedural l

The view pg_timezone_names provides a list of time zone names that are recognized by SET TIMEZONE, along with their associated abbreviations, UTC offsets, and daylight-savings status. (Technically, PostgreSQL does not use UTC because leap seconds are not handled.) Unlike the abbreviations shown in pg_timezone_abbrevs, many of these names imply a set of daylight-savings transition date rules. Therefore, the associated information changes across local DST boundaries. The displayed information is

The view pg_timezone_abbrevs provides a list of time zone abbreviations that are currently recognized by the datetime input routines. The contents of this view change when the timezone_abbreviations run-time parameter is modified. Table 50-80. pg_timezone_abbrevs Columns Name Type Description abbrev text Time zone abbreviation utc_offset interval Offset from UTC (positive means east of Greenwich) is_dst boolean True if this is a daylight-savings abbreviation While most timezone abbreviations