Query Optimization (GEQO) in PostgreSQL ..............................................1210 47.3.1. Future Implementation Tasks for PostgreSQL GEQO .................................1211 xxii 47.4. Further starts or ends with an underscore, so identifiers of this form are safe against possible conflict with future extensions of the standard. The system uses no more than NAMEDATALEN-1 characters of an identifier; ’Dianne”s horse’. PostgreSQL also allows single quotes to be escaped with a backslash (\’). However, future versions of PostgreSQL will not allow this, so applications using backslashes should convert to the

Query Optimization (GEQO) in PostgreSQL ..............................................1203 47.3.1. Future Implementation Tasks for PostgreSQL GEQO .................................1204 47.4. Further Reading starts or ends with an underscore, so identifiers of this form are safe against possible conflict with future extensions of the standard. The system uses no more than NAMEDATALEN-1 characters of an identifier; ’Dianne”s horse’. PostgreSQL also allows single quotes to be escaped with a backslash (\’). However, future versions of PostgreSQL will not allow this, so applications using backslashes should convert to the

Query Optimization (GEQO) in PostgreSQL ..............................................1122 46.3.1. Future Implementation Tasks for PostgreSQL GEQO .................................1123 46.4. Further Reading starts or ends with an underscore, so identifiers of this form are safe against possible conflict with future extensions of the standard. The system uses no more than NAMEDATALEN-1 characters of an identifier; • The tables in question should be created using WITH OIDS to ensure forward compatibility with future releases of PostgreSQL. It is planned that WITHOUT OIDS will become the default. Transaction identifiers

Genetic Query Optimization (GEQO) in PostgreSQL .......................................1049 46.3.1. Future Implementation Tasks for PostgreSQL GEQO ..........................1050 46.4. Further Reading.. starts or ends with an underscore, so identifiers of this form are safe against possible conflict with future extensions of the standard. The system uses no more than NAMEDATALEN-1 characters of an identifier; • The tables in question should be created using WITH OIDS to ensure forward compatibility with future releases of PostgreSQL. It is planned that WITHOUT OIDS will become the default. Transaction identifiers

Query Optimization (GEQO) in PostgreSQL ..............................................1319 48.3.1. Future Implementation Tasks for PostgreSQL GEQO .................................1320 48.4. Further Reading starts or ends with an underscore, so identifiers of this form are safe against possible conflict with future extensions of the standard. The system uses no more than NAMEDATALEN-1 characters of an identifier; Although standard_conforming_strings currently defaults to off, the default will change to on in a future release for improved standards compliance. Applications are therefore encouraged to migrate away

Generating Possible Plans with GEQO..................................................1879 53.3.2. Future Implementation Tasks for PostgreSQL GEQO ..........................1879 53.4. Further Reading.. starts or ends with an underscore, so identifiers of this form are safe against possible conflict with future extensions of the standard. The system uses no more than NAMEDATALEN-1 bytes of an identifier; longer 77; Note that this doesn’t affect any existing rows in the table, it just changes the default for future INSERT commands. To remove any default value, use: ALTER TABLE products ALTER COLUMN price DROP

Generating Possible Plans with GEQO.........................................................1997 53.3.2. Future Implementation Tasks for PostgreSQL GEQO .................................1997 53.4. Further Reading starts or ends with an underscore, so identifiers of this form are safe against possible conflict with future extensions of the standard. The system uses no more than NAMEDATALEN-1 bytes of an identifier; longer Definition Note that this doesn’t affect any existing rows in the table, it just changes the default for future INSERT commands. To remove any default value, use: ALTER TABLE products ALTER COLUMN price DROP

Query Optimization (GEQO) in PostgreSQL ..............................................1319 48.3.1. Future Implementation Tasks for PostgreSQL GEQO .................................1320 48.4. Further Reading starts or ends with an underscore, so identifiers of this form are safe against possible conflict with future extensions of the standard. The system uses no more than NAMEDATALEN-1 characters of an identifier; Although standard_conforming_strings currently defaults to off, the default will change to on in a future release for improved standards compliance. Applications are therefore encouraged to migrate away

Generating Possible Plans with GEQO..................................................1740 51.3.2. Future Implementation Tasks for PostgreSQL GEQO ..........................1740 51.4. Further Reading.. starts or ends with an underscore, so identifiers of this form are safe against possible conflict with future extensions of the standard. The system uses no more than NAMEDATALEN-1 bytes of an identifier; longer 77; Note that this doesn’t affect any existing rows in the table, it just changes the default for future INSERT commands. To remove any default value, use: ALTER TABLE products ALTER COLUMN price DROP

Generating Possible Plans with GEQO.........................................................1853 51.3.2. Future Implementation Tasks for PostgreSQL GEQO .................................1853 51.4. Further Reading starts or ends with an underscore, so identifiers of this form are safe against possible conflict with future extensions of the standard. The system uses no more than NAMEDATALEN-1 bytes of an identifier; longer 77; Note that this doesn’t affect any existing rows in the table, it just changes the default for future INSERT commands. To remove any default value, use: ALTER TABLE products ALTER COLUMN price DROP