byte rounds - Docs search results

bytes, Database Object Management Functions pg_size_pretty, Database Object Management Functions pg_sleep, Delaying Execution pg_sleep_for, Delaying Execution pg_sleep_until, Delaying Execution pg_snapshot_any, Debugging Functions pg_snapshot_xip, Transaction

rounded to precision of 1/256th of BLCKSZ (32 bytes with default BLCKSZ ), and they're not kept

bytes that are prefetched for BLOB , CLOB , and BFILE values. LOBs that exceed that size will require additional round

byte response to the SSL request. If the client begins the SSL negotiation immediately without waiting for the server response to be received it can reduce connection latency by one round

rounded to the nearest integer if the parameter is of integer type. Integer parameters additionally accept hexadecimal input (beginning with 0x ) and octal input (beginning with 0 ), but these formats cannot have a fraction

bytes. desc_occ # Size of the allocated structure. desc_next # Pointer to the next SQLDA structure if the result set contains more than one record. reserved # Unused pointer, contains NULL. Kept for Informix-compatibility

bytes, Database Object Management Functions pg_size_pretty, Database Object Management Functions pg_sleep, Delaying Execution pg_sleep_for, Delaying Execution pg_sleep_until, Delaying Execution pg_snapshot_any, Debugging Functions pg_snapshot_xip, Transaction

rounded to precision of 1/256th of BLCKSZ (32 bytes with default BLCKSZ ), and they're not kept

bytes that are prefetched for BLOB , CLOB , and BFILE values. LOBs that exceed that size will require additional round

rounded to the nearest integer if the parameter is of integer type. Integer parameters additionally accept hexadecimal input (beginning with 0x ) and octal input (beginning with 0 ), but these formats cannot have a fraction

bytes. desc_occ # Size of the allocated structure. desc_next # Pointer to the next SQLDA structure if the result set contains more than one record. reserved # Unused pointer, contains NULL. Kept for Informix-compatibility

bytes is equal to segment_size multiplied by block_size ; by default this is 1GB. server_encoding ( string ) # Reports the database encoding (character set). It is determined when the database is created. Ordinarily, clients need

rounded to precision of 1/256th of BLCKSZ (32 bytes with default BLCKSZ ), and they're not kept

bytes that are prefetched for BLOB , CLOB , and BFILE values. LOBs that exceed that size will require additional round

rounded to the nearest integer if the parameter is of integer type. Integer parameters additionally accept hexadecimal input (beginning with 0x ) and octal input (beginning with 0 ), but these formats cannot have a fraction

bytes. desc_occ Size of the allocated structure. desc_next Pointer to the next SQLDA structure if the result set contains more than one record. reserved Unused pointer, contains NULL. Kept for Informix-compatibility

bytes is equal to segment_size multiplied by block_size ; by default this is 1GB. server_encoding ( string ) Reports the database encoding (character set). It is determined when the database is created. Ordinarily, clients need

bytes large autoincrementing integer 1 to 9223372036854775807 The syntax of constants for the numeric types is described in Section 4.1.2 . The numeric types have a full set of corresponding arithmetic operators and functions. Refer

rounded to precision of 1/256th of BLCKSZ (32 bytes with default BLCKSZ ), and they're not kept

bytes that are prefetched for BLOB , CLOB , and BFILE values. LOBs that exceed that size will require additional round

rounded to the nearest integer if the parameter is of integer type. Integer parameters additionally accept hexadecimal input (beginning with 0x ) and octal input (beginning with 0 ), but these formats cannot have a fraction

bytes. desc_occ Size of the allocated structure. desc_next Pointer to the next SQLDA structure if the result set contains more than one record. reserved Unused pointer, contains NULL. Kept for Informix-compatibility

bytes large autoincrementing integer 1 to 9223372036854775807 The syntax of constants for the numeric types is described in Section 4.1.2 . The numeric types have a full set of corresponding arithmetic operators and functions. Refer

bytes currency amount -92233720368547758.08 to +92233720368547758.07 Since the output of this data type is locale-sensitive, it might not work to load money data into a database that has a different setting of lc_monetary

rounded to precision of 1/256th of BLCKSZ (32 bytes with default BLCKSZ ), and they're not kept

bytes that are prefetched for BLOB , CLOB , and BFILE values. LOBs that exceed that size will require additional round

rounded to the nearest integer if the parameter is of integer type. Integer parameters additionally accept hexadecimal input (beginning with 0x ) and octal input (beginning with 0 ), but these formats cannot have a fraction

bytes. desc_occ Size of the allocated structure. desc_next Pointer to the next SQLDA structure if the result set contains more than one record. reserved Unused pointer, contains NULL. Kept for Informix-compatibility

bytes large autoincrementing integer 1 to 9223372036854775807 The syntax of constants for the numeric types is described in Section 4.1.2 . The numeric types have a full set of corresponding arithmetic operators and functions. Refer

bytes currency amount -92233720368547758.08 to +92233720368547758.07 Since the output of this data type is locale-sensitive, it might not work to load money data into a database that has a different setting of lc_monetary

rounded to precision of 1/256th of BLCKSZ (32 bytes with default BLCKSZ ), and they're not kept

rounded to the nearest integer if the parameter is of integer type. Integer parameters additionally accept hexadecimal input (beginning with 0x ) and octal input (beginning with 0 ), but these formats cannot have a fraction

bytes. desc_occ Size of the allocated structure. desc_next Pointer to the next SQLDA structure if the result set contains more than one record. reserved Unused pointer, contains NULL. Kept for Informix-compatibility

bytes large autoincrementing integer 1 to 9223372036854775807 The syntax of constants for the numeric types is described in Section 4.1.2 . The numeric types have a full set of corresponding arithmetic operators and functions. Refer

bytes currency amount -92233720368547758.08 to +92233720368547758.07 Since the output of this data type is locale-sensitive, it might not work to load money data into a database that has a different setting of lc_monetary

bytes). max_prepared_transactions ( integer ) Sets the maximum number of transactions that can be in the “ prepared ” state simultaneously (see PREPARE TRANSACTION ). Setting this parameter to zero (which is the default) disables the prepared-transaction

rounded to precision of 1/256th of BLCKSZ (32 bytes with default BLCKSZ ), and they're not kept

bytes. desc_occ Size of the allocated structure. desc_next Pointer to the next SQLDA structure if the result set contains more than one record. reserved Unused pointer, contains NULL. Kept for Informix-compatibility

bytes large autoincrementing integer 1 to 9223372036854775807 The syntax of constants for the numeric types is described in Section 4.1.2 . The numeric types have a full set of corresponding arithmetic operators and functions. Refer

bytes). max_prepared_transactions ( integer ) Sets the maximum number of transactions that can be in the “ prepared ” state simultaneously (see PREPARE TRANSACTION ). Setting this parameter to zero (which is the default) disables the prepared-transaction

bytes currency amount -92233720368547758.08 to +92233720368547758.07 Since the output of this data type is locale-sensitive, it might not work to load money data into a database that has a different setting of lc_monetary

bytes in most cases. Fix pg_dump to dump non-global default privileges correctly (Neil Chen, Masahiko Sawada) If a global (unrestricted) ALTER DEFAULT PRIVILEGES command revoked some present-by-default privilege, for example EXECUTE

rounded to precision of 1/256th of BLCKSZ (32 bytes with default BLCKSZ ), and they're not kept

bytes. desc_occ Size of the allocated structure. desc_next Pointer to the next SQLDA structure if the result set contains more than one record. reserved Unused pointer, contains NULL. Kept for Informix-compatibility

bytes large autoincrementing integer 1 to 9223372036854775807 The syntax of constants for the numeric types is described in Section 4.1.2 . The numeric types have a full set of corresponding arithmetic operators and functions. Refer

bytes). max_prepared_transactions ( integer ) Sets the maximum number of transactions that can be in the “ prepared ” state simultaneously (see PREPARE TRANSACTION ). Setting this parameter to zero (which is the default) disables the prepared-transaction

bytes currency amount -92233720368547758.08 to +92233720368547758.07 Since the output of this data type is locale-sensitive, it might not work to load money data into a database that has a different setting of lc_monetary

bytes in most cases. Fix pg_dump to dump non-global default privileges correctly (Neil Chen, Masahiko Sawada) If a global (unrestricted) ALTER DEFAULT PRIVILEGES command revoked some present-by-default privilege, for example EXECUTE

rounded to precision of 1/256th of BLCKSZ (32 bytes with default BLCKSZ ), and they're not kept

bytes. desc_occ Size of the allocated structure. desc_next Pointer to the next SQLDA structure if the result set contains more than one record. reserved Unused pointer, contains NULL. Kept for Informix-compatibility

bytes large autoincrementing integer 1 to 9223372036854775807 The syntax of constants for the numeric types is described in Section 4.1.2 . The numeric types have a full set of corresponding arithmetic operators and functions. Refer

bytes). max_prepared_transactions ( integer ) Sets the maximum number of transactions that can be in the “ prepared ” state simultaneously (see PREPARE TRANSACTION ). Setting this parameter to zero (which is the default) disables the prepared-transaction

bytes in most cases. Fix pg_dump to dump non-global default privileges correctly (Neil Chen, Masahiko Sawada) If a global (unrestricted) ALTER DEFAULT PRIVILEGES command revoked some present-by-default privilege, for example EXECUTE

bytes currency amount -92233720368547758.08 to +92233720368547758.07 Since the output of this data type is locale-sensitive, it might not work to load money data into a database that has a different setting of lc_monetary

rounded to precision of 1/256th of BLCKSZ (32 bytes with default BLCKSZ ), and they're not kept

bytes. desc_occ Size of the allocated structure. desc_next Pointer to the next SQLDA structure if the result set contains more than one record. reserved Unused pointer, contains NULL. Kept for Informix-compatibility

bytes large autoincrementing integer 1 to 9223372036854775807 The syntax of constants for the numeric types is described in Section 4.1.2 . The numeric types have a full set of corresponding arithmetic operators and functions. Refer

byte character was allowed as an escape. Add a width_bucket() variant that supports any sortable data type and non-uniform bucket widths (Petr Jelínek) Add an optional missing_ok argument to pg_read_file

bytes currency amount -92233720368547758.08 to +92233720368547758.07 Since the output of this data type is locale-sensitive, it might not work to load money data into a database that has a different setting of lc_monetary

byte, Binary String Functions and Operators get_current_ts_config, Text Search Functions and Operators get_namespace, Functions get_raw_page, Functions GIN (see index ) gin_fuzzy_search_limit configuration parameter, Other Defaults gin_leafpage

bytes, Database Object Management Functions pg_size_pretty, Database Object Management Functions pg_sleep, Delaying Execution pg_sleep_for, Delaying Execution pg_sleep_until, Delaying Execution pg_snapshot_any, Debugging Functions pg_snapshot_xip, Transaction

rounded to precision of 1/256th of BLCKSZ (32 bytes with default BLCKSZ ), and they're not kept

bytes that are prefetched for BLOB , CLOB , and BFILE values. LOBs that exceed that size will require additional round

byte response to the SSL request. If the client begins the SSL negotiation immediately without waiting for the server response to be received it can reduce connection latency by one round

rounded to the nearest integer if the parameter is of integer type. Integer parameters additionally accept hexadecimal input (beginning with 0x ) and octal input (beginning with 0 ), but these formats cannot have a fraction

bytes. desc_occ # Size of the allocated structure. desc_next # Pointer to the next SQLDA structure if the result set contains more than one record. reserved # Unused pointer, contains NULL. Kept for Informix-compatibility

round-trips between the coordinator and workers in the multi-node citus . For multi-tenant workloads, it is more efficient to run transactions in distributed functions. The efficiency gains become more apparent for larger transactions

bytes, Database Object Management Functions pg_size_pretty, Database Object Management Functions pg_sleep, Delaying Execution pg_sleep_for, Delaying Execution pg_sleep_until, Delaying Execution pg_snapshot_any, Debugging Functions pg_snapshot_xip, Transaction

rounded to precision of 1/256th of BLCKSZ (32 bytes with default BLCKSZ ), and they're not kept

bytes that are prefetched for BLOB , CLOB , and BFILE values. LOBs that exceed that size will require additional round

rounded to the nearest integer if the parameter is of integer type. Integer parameters additionally accept hexadecimal input (beginning with 0x ) and octal input (beginning with 0 ), but these formats cannot have a fraction

bytes. desc_occ # Size of the allocated structure. desc_next # Pointer to the next SQLDA structure if the result set contains more than one record. reserved # Unused pointer, contains NULL. Kept for Informix-compatibility

bytes, Database Object Management Functions pg_size_pretty, Database Object Management Functions pg_sleep, Delaying Execution pg_sleep_for, Delaying Execution pg_sleep_until, Delaying Execution pg_snapshot_any, Debugging Functions pg_snapshot_xip, System

rounded to precision of 1/256th of BLCKSZ (32 bytes with default BLCKSZ ), and they're not kept

bytes that are prefetched for BLOB , CLOB , and BFILE values. LOBs that exceed that size will require additional round

rounded to the nearest integer if the parameter is of integer type. Integer parameters additionally accept hexadecimal input (beginning with 0x ) and octal input (beginning with 0 ), but these formats cannot have a fraction

bytes. desc_occ Size of the allocated structure. desc_next Pointer to the next SQLDA structure if the result set contains more than one record. reserved Unused pointer, contains NULL. Kept for Informix-compatibility

round the value to the specified number of fractional digits. Then, if the number of digits to the left of the decimal point exceeds the declared precision minus the declared scale, an error is raised

bytes, Database Object Management Functions pg_size_pretty, Database Object Management Functions pg_sleep, Delaying Execution pg_sleep_for, Delaying Execution pg_sleep_until, Delaying Execution pg_snapshot_any, Debugging Functions pg_snapshot_xip, System

rounded to precision of 1/256th of BLCKSZ (32 bytes with default BLCKSZ ), and they're not kept

bytes that are prefetched for BLOB , CLOB , and BFILE values. LOBs that exceed that size will require additional round

rounded to the nearest integer if the parameter is of integer type. Integer parameters additionally accept hexadecimal input (beginning with 0x ) and octal input (beginning with 0 ), but these formats cannot have a fraction

bytes. desc_occ Size of the allocated structure. desc_next Pointer to the next SQLDA structure if the result set contains more than one record. reserved Unused pointer, contains NULL. Kept for Informix-compatibility

round the value to the specified number of fractional digits. Then, if the number of digits to the left of the decimal point exceeds the declared precision minus the declared scale, an error is raised

rounded to precision of 1/256th of BLCKSZ (32 bytes with default BLCKSZ ), and they're not kept

bytes that are prefetched for BLOB , CLOB , and BFILE values. LOBs that exceed that size will require additional round

rounded to the nearest integer if the parameter is of integer type. Integer parameters additionally accept hexadecimal input (beginning with 0x ) and octal input (beginning with 0 ), but these formats cannot have a fraction

bytes. desc_occ Size of the allocated structure. desc_next Pointer to the next SQLDA structure if the result set contains more than one record. reserved Unused pointer, contains NULL. Kept for Informix-compatibility

bytes large autoincrementing integer 1 to 9223372036854775807 The syntax of constants for the numeric types is described in Section 4.1.2 . The numeric types have a full set of corresponding arithmetic operators and functions. Refer

bytes currency amount -92233720368547758.08 to +92233720368547758.07 Since the output of this data type is locale-sensitive, it might not work to load money data into a database that has a different setting of lc_monetary

rounded to precision of 1/256th of BLCKSZ (32 bytes with default BLCKSZ ), and they're not kept

rounded to the nearest integer if the parameter is of integer type. Integer parameters additionally accept hexadecimal input (beginning with 0x ) and octal input (beginning with 0 ), but these formats cannot have a fraction

bytes. desc_occ Size of the allocated structure. desc_next Pointer to the next SQLDA structure if the result set contains more than one record. reserved Unused pointer, contains NULL. Kept for Informix-compatibility

bytes large autoincrementing integer 1 to 9223372036854775807 The syntax of constants for the numeric types is described in Section 4.1.2 . The numeric types have a full set of corresponding arithmetic operators and functions. Refer

bytes currency amount -92233720368547758.08 to +92233720368547758.07 Since the output of this data type is locale-sensitive, it might not work to load money data into a database that has a different setting of lc_monetary

bytes). max_prepared_transactions ( integer ) Sets the maximum number of transactions that can be in the “ prepared ” state simultaneously (see PREPARE TRANSACTION ). Setting this parameter to zero (which is the default) disables the prepared-transaction

rounded to precision of 1/256th of BLCKSZ (32 bytes with default BLCKSZ ), and they're not kept

bytes. desc_occ Size of the allocated structure. desc_next Pointer to the next SQLDA structure if the result set contains more than one record. reserved Unused pointer, contains NULL. Kept for Informix-compatibility

bytes large autoincrementing integer 1 to 9223372036854775807 The syntax of constants for the numeric types is described in Section 4.1.2 . The numeric types have a full set of corresponding arithmetic operators and functions. Refer

bytes). max_prepared_transactions ( integer ) Sets the maximum number of transactions that can be in the “ prepared ” state simultaneously (see PREPARE TRANSACTION ). Setting this parameter to zero (which is the default) disables the prepared-transaction

bytes currency amount -92233720368547758.08 to +92233720368547758.07 Since the output of this data type is locale-sensitive, it might not work to load money data into a database that has a different setting of lc_monetary

bytes in most cases. Fix pg_dump to dump non-global default privileges correctly (Neil Chen, Masahiko Sawada) If a global (unrestricted) ALTER DEFAULT PRIVILEGES command revoked some present-by-default privilege, for example EXECUTE

rounded to precision of 1/256th of BLCKSZ (32 bytes with default BLCKSZ ), and they're not kept

bytes. desc_occ Size of the allocated structure. desc_next Pointer to the next SQLDA structure if the result set contains more than one record. reserved Unused pointer, contains NULL. Kept for Informix-compatibility

bytes large autoincrementing integer 1 to 9223372036854775807 The syntax of constants for the numeric types is described in Section 4.1.2 . The numeric types have a full set of corresponding arithmetic operators and functions. Refer

bytes). max_prepared_transactions ( integer ) Sets the maximum number of transactions that can be in the “ prepared ” state simultaneously (see PREPARE TRANSACTION ). Setting this parameter to zero (which is the default) disables the prepared-transaction

bytes currency amount -92233720368547758.08 to +92233720368547758.07 Since the output of this data type is locale-sensitive, it might not work to load money data into a database that has a different setting of lc_monetary

bytes in most cases. Fix pg_dump to dump non-global default privileges correctly (Neil Chen, Masahiko Sawada) If a global (unrestricted) ALTER DEFAULT PRIVILEGES command revoked some present-by-default privilege, for example EXECUTE

rounded to precision of 1/256th of BLCKSZ (32 bytes with default BLCKSZ ), and they're not kept

bytes. desc_occ Size of the allocated structure. desc_next Pointer to the next SQLDA structure if the result set contains more than one record. reserved Unused pointer, contains NULL. Kept for Informix-compatibility

bytes large autoincrementing integer 1 to 9223372036854775807 The syntax of constants for the numeric types is described in Section 4.1.2 . The numeric types have a full set of corresponding arithmetic operators and functions. Refer

bytes). max_prepared_transactions ( integer ) Sets the maximum number of transactions that can be in the “ prepared ” state simultaneously (see PREPARE TRANSACTION ). Setting this parameter to zero (which is the default) disables the prepared-transaction

bytes in most cases. Fix pg_dump to dump non-global default privileges correctly (Neil Chen, Masahiko Sawada) If a global (unrestricted) ALTER DEFAULT PRIVILEGES command revoked some present-by-default privilege, for example EXECUTE

bytes currency amount -92233720368547758.08 to +92233720368547758.07 Since the output of this data type is locale-sensitive, it might not work to load money data into a database that has a different setting of lc_monetary

rounded to precision of 1/256th of BLCKSZ (32 bytes with default BLCKSZ ), and they're not kept

byte response to the SSL request. If the client begins the SSL negotiation immediately without waiting for the server response to be received it can reduce connection latency by one round

rounded to the nearest integer if the parameter is of integer type. Integer parameters additionally accept hexadecimal input (beginning with 0x ) and octal input (beginning with 0 ), but these formats cannot have a fraction

bytes. desc_occ # Size of the allocated structure. desc_next # Pointer to the next SQLDA structure if the result set contains more than one record. reserved # Unused pointer, contains NULL. Kept for Informix-compatibility

bytes is equal to segment_size multiplied by block_size ; by default this is 1GB. server_encoding ( string ) # Reports the database encoding (character set). It is determined when the database is created. Ordinarily, clients need

bytes large autoincrementing integer 1 to 9223372036854775807 The syntax of constants for the numeric types is described in Section 4.1.2 . The numeric types have a full set of corresponding arithmetic operators and functions. Refer

rounded to precision of 1/256th of BLCKSZ (32 bytes with default BLCKSZ ), and they're not kept

rounded to the nearest integer if the parameter is of integer type. Integer parameters additionally accept hexadecimal input (beginning with 0x ) and octal input (beginning with 0 ), but these formats cannot have a fraction

bytes. desc_occ # Size of the allocated structure. desc_next # Pointer to the next SQLDA structure if the result set contains more than one record. reserved # Unused pointer, contains NULL. Kept for Informix-compatibility

bytes is equal to segment_size multiplied by block_size ; by default this is 1GB. server_encoding ( string ) # Reports the database encoding (character set). It is determined when the database is created. Ordinarily, clients need

bytes large autoincrementing integer 1 to 9223372036854775807 The syntax of constants for the numeric types is described in Section 4.1.2 . The numeric types have a full set of corresponding arithmetic operators and functions. Refer

bytes currency amount -92233720368547758.08 to +92233720368547758.07 Since the output of this data type is locale-sensitive, it might not work to load money data into a database that has a different setting of lc_monetary

rounded to precision of 1/256th of BLCKSZ (32 bytes with default BLCKSZ ), and they're not kept

rounded to the nearest integer if the parameter is of integer type. Integer parameters additionally accept hexadecimal input (beginning with 0x ) and octal input (beginning with 0 ), but these formats cannot have a fraction

bytes. desc_occ Size of the allocated structure. desc_next Pointer to the next SQLDA structure if the result set contains more than one record. reserved Unused pointer, contains NULL. Kept for Informix-compatibility

bytes is equal to segment_size multiplied by block_size ; by default this is 1GB. server_encoding ( string ) Reports the database encoding (character set). It is determined when the database is created. Ordinarily, clients need

bytes large autoincrementing integer 1 to 9223372036854775807 The syntax of constants for the numeric types is described in Section 4.1.2 . The numeric types have a full set of corresponding arithmetic operators and functions. Refer

round to the nearest month (Bruce Momjian) § For example, convert 1.99 years to 2 years , not 1 year 11 months as before. Improve consistency of interval parsing with trailing periods (Tom Lane) § Numbers with trailing

rounded to precision of 1/256th of BLCKSZ (32 bytes with default BLCKSZ ), and they're not kept

rounded to the nearest integer if the parameter is of integer type. Integer parameters additionally accept hexadecimal input (beginning with 0x ) and octal input (beginning with 0 ), but these formats cannot have a fraction

bytes. desc_occ Size of the allocated structure. desc_next Pointer to the next SQLDA structure if the result set contains more than one record. reserved Unused pointer, contains NULL. Kept for Informix-compatibility

bytes large autoincrementing integer 1 to 9223372036854775807 The syntax of constants for the numeric types is described in Section 4.1.2 . The numeric types have a full set of corresponding arithmetic operators and functions. Refer

bytes currency amount -92233720368547758.08 to +92233720368547758.07 Since the output of this data type is locale-sensitive, it might not work to load money data into a database that has a different setting of lc_monetary

bytes). max_prepared_transactions ( integer ) Sets the maximum number of transactions that can be in the “ prepared ” state simultaneously (see PREPARE TRANSACTION ). Setting this parameter to zero (which is the default) disables the prepared-transaction

rounded to precision of 1/256th of BLCKSZ (32 bytes with default BLCKSZ ), and they're not kept

rounded to the nearest integer if the parameter is of integer type. Integer parameters additionally accept hexadecimal input (beginning with 0x ) and octal input (beginning with 0 ), but these formats cannot have a fraction

bytes. desc_occ Size of the allocated structure. desc_next Pointer to the next SQLDA structure if the result set contains more than one record. reserved Unused pointer, contains NULL. Kept for Informix-compatibility

bytes large autoincrementing integer 1 to 9223372036854775807 The syntax of constants for the numeric types is described in Section 4.1.2 . The numeric types have a full set of corresponding arithmetic operators and functions. Refer

bytes currency amount -92233720368547758.08 to +92233720368547758.07 Since the output of this data type is locale-sensitive, it might not work to load money data into a database that has a different setting of lc_monetary

bytes). max_prepared_transactions ( integer ) Sets the maximum number of transactions that can be in the “ prepared ” state simultaneously (see PREPARE TRANSACTION ). Setting this parameter to zero (which is the default) disables the prepared-transaction

rounded to precision of 1/256th of BLCKSZ (32 bytes with default BLCKSZ ), and they're not kept

rounded to the nearest integer if the parameter is of integer type. Integer parameters additionally accept hexadecimal input (beginning with 0x ) and octal input (beginning with 0 ), but these formats cannot have a fraction

bytes. desc_occ Size of the allocated structure. desc_next Pointer to the next SQLDA structure if the result set contains more than one record. reserved Unused pointer, contains NULL. Kept for Informix-compatibility

bytes large autoincrementing integer 1 to 9223372036854775807 The syntax of constants for the numeric types is described in Section 4.1.2 . The numeric types have a full set of corresponding arithmetic operators and functions. Refer

bytes currency amount -92233720368547758.08 to +92233720368547758.07 Since the output of this data type is locale-sensitive, it might not work to load money data into a database that has a different setting of lc_monetary

bytes). max_prepared_transactions ( integer ) Sets the maximum number of transactions that can be in the “ prepared ” state simultaneously (see PREPARE TRANSACTION ). Setting this parameter to zero (which is the default) disables the prepared-transaction

rounded to precision of 1/256th of BLCKSZ (32 bytes with default BLCKSZ ), and they're not kept

bytes. desc_occ Size of the allocated structure. desc_next Pointer to the next SQLDA structure if the result set contains more than one record. reserved Unused pointer, contains NULL. Kept for Informix-compatibility

bytes large autoincrementing integer 1 to 9223372036854775807 The syntax of constants for the numeric types is described in Section 4.1.2 . The numeric types have a full set of corresponding arithmetic operators and functions. Refer

bytes). max_prepared_transactions ( integer ) Sets the maximum number of transactions that can be in the “ prepared ” state simultaneously (see PREPARE TRANSACTION ). Setting this parameter to zero (which is the default) disables the prepared-transaction

bytes currency amount -92233720368547758.08 to +92233720368547758.07 Since the output of this data type is locale-sensitive, it might not work to load money data into a database that has a different setting of lc_monetary

bytes in most cases. Fix pg_dump to dump non-global default privileges correctly (Neil Chen, Masahiko Sawada) If a global (unrestricted) ALTER DEFAULT PRIVILEGES command revoked some present-by-default privilege, for example EXECUTE

rounded to precision of 1/256th of BLCKSZ (32 bytes with default BLCKSZ ), and they're not kept

bytes. desc_occ Size of the allocated structure. desc_next Pointer to the next SQLDA structure if the result set contains more than one record. reserved Unused pointer, contains NULL. Kept for Informix-compatibility

bytes large autoincrementing integer 1 to 9223372036854775807 The syntax of constants for the numeric types is described in Section 4.1.2 . The numeric types have a full set of corresponding arithmetic operators and functions. Refer

bytes). max_prepared_transactions ( integer ) Sets the maximum number of transactions that can be in the “ prepared ” state simultaneously (see PREPARE TRANSACTION ). Setting this parameter to zero (which is the default) disables the prepared-transaction

bytes currency amount -92233720368547758.08 to +92233720368547758.07 Since the output of this data type is locale-sensitive, it might not work to load money data into a database that has a different setting of lc_monetary

bytes in most cases. Fix pg_dump to dump non-global default privileges correctly (Neil Chen, Masahiko Sawada) If a global (unrestricted) ALTER DEFAULT PRIVILEGES command revoked some present-by-default privilege, for example EXECUTE

rounded to precision of 1/256th of BLCKSZ (32 bytes with default BLCKSZ ), and they're not kept

bytes. desc_occ Size of the allocated structure. desc_next Pointer to the next SQLDA structure if the result set contains more than one record. reserved Unused pointer, contains NULL. Kept for Informix-compatibility

bytes large autoincrementing integer 1 to 9223372036854775807 The syntax of constants for the numeric types is described in Section 4.1.2 . The numeric types have a full set of corresponding arithmetic operators and functions. Refer

bytes). max_prepared_transactions ( integer ) Sets the maximum number of transactions that can be in the “ prepared ” state simultaneously (see PREPARE TRANSACTION ). Setting this parameter to zero (which is the default) disables the prepared-transaction

bytes in most cases. Fix pg_dump to dump non-global default privileges correctly (Neil Chen, Masahiko Sawada) If a global (unrestricted) ALTER DEFAULT PRIVILEGES command revoked some present-by-default privilege, for example EXECUTE

bytes currency amount -92233720368547758.08 to +92233720368547758.07 Since the output of this data type is locale-sensitive, it might not work to load money data into a database that has a different setting of lc_monetary

rounded to precision of 1/256th of BLCKSZ (32 bytes with default BLCKSZ ), and they're not kept

bytes. desc_occ Size of the allocated structure. desc_next Pointer to the next SQLDA structure if the result set contains more than one record. reserved Unused pointer, contains NULL. Kept for Informix-compatibility

bytes large autoincrementing integer 1 to 9223372036854775807 The syntax of constants for the numeric types is described in Section 4.1.2 . The numeric types have a full set of corresponding arithmetic operators and functions. Refer

byte character was allowed as an escape. Add a width_bucket() variant that supports any sortable data type and non-uniform bucket widths (Petr Jelínek) Add an optional missing_ok argument to pg_read_file

bytes currency amount -92233720368547758.08 to +92233720368547758.07 Since the output of this data type is locale-sensitive, it might not work to load money data into a database that has a different setting of lc_monetary

byte, Binary String Functions and Operators get_current_ts_config, Text Search Functions and Operators get_raw_page, Functions GIN (see index ) gin_fuzzy_search_limit configuration parameter, Other Defaults gin_leafpage_items, Functions

rounded to precision of 1/256th of BLCKSZ (32 bytes with default BLCKSZ ), and they're not kept

bytes. desc_occ Size of the allocated structure. desc_next Pointer to the next SQLDA structure if the result set contains more than one record. reserved Unused pointer, contains NULL. Kept for Informix-compatibility

bytes large autoincrementing integer 1 to 9223372036854775807 The syntax of constants for the numeric types is described in Section 4.1.2 . The numeric types have a full set of corresponding arithmetic operators and functions. Refer

bytes currency amount -92233720368547758.08 to +92233720368547758.07 Since the output of this data type is locale-sensitive, it might not work to load money data into a database that has a different setting of lc_monetary

rounding instead of truncating. Make to_char() 's localized month/day names depend on LC_TIME , not LC_MESSAGES (Euler Taveira de Oliveira) Cause to_date() and to_timestamp() to more consistently report errors for invalid

round when reducing precision of fractional seconds (Tom Lane) The code always acted this way for integer-based dates/times. Now float-based dates/times behave similarly. E.56.2.4. Object Renaming Tighten enforcement of column name consistency during

rounding issues with the extra decimals, you should preserve the same numeric(p,s) Postgres Pro data type. Do that only if you need exactness because using numeric(p,s) is slower than using real

round(((100.0 * ((count(*)))::numeric) / sum((count(*))) OVER (?)), 2)) DESC Sort Method: quicksort Memory: 3076kB Network: FDW bytes

round_robin , and shortest_job_first . Added the shardman.pg_stat_foreign_stat_bytes view

bytes. Note that this parameter does not limit the maximum size of the result returned by the query. It only affects messages sent to workers. Increasing this parameter value will result in a proportional memory