auth_delay — pause on authentication failure .......................................... 2701 F.3. auto_explain — log execution plans of slow queries ................................. 2702 F.4. basebackup_to_shell of those in its parent tables. A child table does not inherit identity columns or their properties auto- matically from the parent. During INSERT or UPDATE, a column is treated as an identity column if definition without any GENERATED clause in CREATE TABLE ... PARTITION OF, then its GENERATED clause will auto- matically be copied from the parent. ALTER TABLE ... ATTACH PARTITION will insist that parent and

auth_delay — pause on authentication failure .......................................... 2659 F.4. auto_explain — log execution plans of slow queries ................................. 2660 F.5. basebackup_to_shell definition without any GENERATED clause in CREATE TABLE ... PARTITION OF, then its GENERATED clause will auto- matically be copied from the parent. ALTER TABLE ... ATTACH PARTITION will insist that parent and types, but merely a notation- al convenience for creating unique identifier columns (similar to the AUTO_INCREMENT property supported by some other databases). In the current implementation, specifying:

auth_delay — pause on authentication failure ............................................... 2857 F.3. auto_explain — log execution plans of slow queries ...................................... 2858 F.4. basebackup_to_shell mentioned earlier, it is possible to create indexes on partitioned tables so that they are applied auto- matically to the entire hierarchy. This can be very convenient as not only will all existing partitions types, but merely a notational convenience for creating unique identifier columns (similar to the AUTO_INCREMENT property supported by some other databases). In the current implementation, specifying:

auth_delay — pause on authentication failure ............................................... 2802 F.4. auto_explain — log execution plans of slow queries ...................................... 2803 F.5. basebackup_to_shell types, but merely a notational convenience for creating unique identifier columns (similar to the AUTO_INCREMENT property supported by some other databases). In the current implementation, specifying: statistics. Actual data collection is performed by ANALYZE (either a manual command, or background auto-analyze). The collected values can be examined in the pg_statistic_ext_data catalog. ANALYZE computes

................................................. 2595 xix PostgreSQL 14.10 Documentation F.4. auto_explain ...................................................................................... 2595 types, but merely a notation- al convenience for creating unique identifier columns (similar to the AUTO_INCREMENT property supported by some other databases). In the current implementation, specifying: Section 38.2.5 and Section 8.17). anycompatible Indicates that a function accepts any data type, with auto- matic promotion of multiple arguments to a common data type (see Section 38.2.5). anycompatiblearray

....................................................................................... 2738 F.4. auto_explain ......................................................................................... types, but merely a notational convenience for creating unique identifier columns (similar to the AUTO_INCREMENT property supported by some other databases). In the current implementation, specifying: statistics. Actual data collection is performed by ANALYZE (either a manual command, or background auto-analyze). The collected values can be examined in the pg_statistic_ext_data catalog. ANALYZE computes

....................................................................................... 2508 F.4. auto_explain ...................................................................................... 2509 types, but merely a notation- al convenience for creating unique identifier columns (similar to the AUTO_INCREMENT property supported by some other databases). In the current implementation, specifying: (see Section 37.2.5). anycompatiblearray Indicates that a function accepts any array data type, with auto- matic promotion of multiple arguments to a common data type (see Section 37.2.5). anycompatiblenonarray

....................................................................................... 2650 F.4. auto_explain ......................................................................................... types, but merely a notational convenience for creating unique identifier columns (similar to the AUTO_INCREMENT property supported by some other databases). In the current implementation, specifying: tion 37.2.5). anycompatiblenonarray Indicates that a function accepts any non-array data type, with auto- matic promotion of multiple arguments to a common data type (see Section 37.2.5). anycompatiblerange

....................................................................................... 2629 F.4. auto_explain ...................................................................................... 2629 types, but merely a notation- al convenience for creating unique identifier columns (similar to the AUTO_INCREMENT property supported by some other databases). In the current implementation, specifying: Section 38.2.5 and Section 8.17). anycompatible Indicates that a function accepts any data type, with auto- matic promotion of multiple arguments to a common data type (see Section 38.2.5). anycompatiblearray

....................................................................................... 2532 F.4. auto_explain ...................................................................................... 2532 types, but merely a notation- al convenience for creating unique identifier columns (similar to the AUTO_INCREMENT property supported by some other databases). In the current implementation, specifying: disconnects ungracefully.) pg_advisory_xact_lock works the same as pg_advisory_lock, except the lock is auto- matically released at the end of the current transaction and cannot be released explicitly. pg_