PostgreSQL 12.17 Documentation
resolution algorithms. In most cases the constant will be automatically coerced to the most appropriate type de- pending on context. When necessary, you can force a numeric value to be interpreted as a specific references, always bypass row security to ensure that data integrity is maintained. Care must be taken when de- veloping schemas and row level policies to avoid “covert channel” leaks of information through such pruned during this stage will not show up in the query's EXPLAIN or EXPLAIN ANALYZE. It is possible to de- termine the number of partitions which were removed during this phase by observing the “Subplans Removed”0 码力 | 2786 页 | 12.72 MB | 1 年前3PostgreSQL 10.23 Documentation
the POSTGRES package written at the University of California at Berkeley. With over two decades of de- velopment behind it, PostgreSQL is now the most advanced open-source database available anywhere. resolution algorithms. In most cases the constant will be automatically coerced to the most appropriate type de- pending on context. When necessary, you can force a numeric value to be interpreted as a specific references, always bypass row security to ensure that data integrity is maintained. Care must be taken when de- veloping schemas and row level policies to avoid “covert channel” leaks of information through such0 码力 | 2590 页 | 12.03 MB | 1 年前3PostgreSQL 11.22 Documentation
resolution algorithms. In most cases the constant will be automatically coerced to the most appropriate type de- pending on context. When necessary, you can force a numeric value to be interpreted as a specific references, always bypass row security to ensure that data integrity is maintained. Care must be taken when de- veloping schemas and row level policies to avoid “covert channel” leaks of information through such pruned during this stage will not show up in the query's EXPLAIN or EXPLAIN ANALYZE. It is possible to de- termine the number of partitions which were removed during this phase by observing the “Subplans Removed”0 码力 | 2732 页 | 12.44 MB | 1 年前3PostgreSQL 12.17 Documentation
DEFAULT. These cause the referencing column(s) in the referencing row(s) to be set to nulls or their de- fault values, respectively, when the referenced row is deleted. Note that these do not excuse you tables All these actions are performed using the ALTER TABLE command, whose reference page contains de- tails beyond those given here. 5.6.1. Adding a Column To add a column, use a command like: ALTER constraints and default values, distinct from those of other partitions. See CREATE TABLE for more de- tails on creating partitioned tables and partitions. It is not possible to turn a regular table into0 码力 | 2943 页 | 12.61 MB | 1 年前3PostgreSQL 10.23 Documentation
DEFAULT. These cause the referencing column(s) in the referencing row(s) to be set to nulls or their de- fault values, respectively, when the referenced row is deleted. Note that these do not excuse you tables All these actions are performed using the ALTER TABLE command, whose reference page contains de- tails beyond those given here. 5.5.1. Adding a Column To add a column, use a command like: ALTER name) fied by src_en- coding. The string must be valid in this en- coding. Conver- sions can be de- fined by CREATE CONVERSION. Al- so there are some predefined conver- sions. See Ta- ble 9.10 for0 码力 | 2727 页 | 11.93 MB | 1 年前3PostgreSQL 11.22 Documentation
DEFAULT. These cause the referencing column(s) in the referencing row(s) to be set to nulls or their de- fault values, respectively, when the referenced row is deleted. Note that these do not excuse you tables All these actions are performed using the ALTER TABLE command, whose reference page contains de- tails beyond those given here. 5.5.1. Adding a Column To add a column, use a command like: 75 constraints and default values, distinct from those of other partitions. See CREATE TABLE for more de- tails on creating partitioned tables and partitions. It is not possible to turn a regular table into0 码力 | 2883 页 | 12.34 MB | 1 年前3PostgreSQL 13.13 Documentation
resolution algorithms. In most cases the constant will be automatically coerced to the most appropriate type de- 38 SQL Syntax pending on context. When necessary, you can force a numeric value to be interpreted references, always bypass row security to ensure that data integrity is maintained. Care must be taken when de- veloping schemas and row level policies to avoid “covert channel” leaks of information through such pruned during this stage will not show up in the query's EXPLAIN or EXPLAIN ANALYZE. It is possible to de- termine the number of partitions which were removed during this phase by observing the “Subplans Removed”0 码力 | 2782 页 | 13.00 MB | 1 年前3PostgreSQL 14.10 Documentation
resolution algorithms. In most cases the constant will be automatically coerced to the most appropriate type de- pending on context. When necessary, you can force a numeric value to be interpreted as a specific references, always bypass row security to ensure that data integrity is maintained. Care must be taken when de- veloping schemas and row level policies to avoid “covert channel” leaks of information through such pruned during this stage will not show up in the query's EXPLAIN or EXPLAIN ANALYZE. It is possible to de- termine the number of partitions which were removed during this phase by observing the “Subplans Removed”0 码力 | 2871 页 | 13.38 MB | 1 年前3PostgreSQL 16.1 Documentation
resolution algorithms. In most cases the constant will be automatically coerced to the most appropriate type de- pending on context. When necessary, you can force a numeric value to be interpreted as a specific references, always bypass row security to ensure that data integrity is maintained. Care must be taken when de- veloping schemas and row level policies to avoid “covert channel” leaks of information through such pruned during this stage will not show up in the query's EXPLAIN or EXPLAIN ANALYZE. It is possible to de- termine the number of partitions which were removed during this phase by observing the “Subplans Removed”0 码力 | 2974 页 | 14.22 MB | 1 年前3PostgreSQL 15.5 Documentation
resolution algorithms. In most cases the constant will be automatically coerced to the most appropriate type de- pending on context. When necessary, you can force a numeric value to be interpreted as a specific references, always bypass row security to ensure that data integrity is maintained. Care must be taken when de- veloping schemas and row level policies to avoid “covert channel” leaks of information through such pruned during this stage will not show up in the query's EXPLAIN or EXPLAIN ANALYZE. It is possible to de- termine the number of partitions which were removed during this phase by observing the “Subplans Removed”0 码力 | 2910 页 | 13.60 MB | 1 年前3
共 40 条
- 1
- 2
- 3
- 4