foo 'my_table' testdb=> SELECT * FROM :foo; would query the table my_table. Note that this may be unsafe: the value of the variable is copied literally, so it can contain unbalanced quotes, or even backslash such as ':foo' doesn’t work to produce a quoted literal from a variable’s value (and it would be unsafe if it did work, since it wouldn’t correctly handle quotes embedded in the value). One example use NOT ] LEAKPROOF { [EXTERNAL] SECURITY INVOKER | [EXTERNAL] SECURITY DEFINER } PARALLEL { UNSAFE | RESTRICTED | SAFE } EXECUTE ON { ANY | COORDINATOR | ALL SEGMENTS | INITPLAN } COST

maintenance release that resolves several issues and changes one feature. Changed Feature Deactivated unsafe TLS 1.0 and TLS 1.1 protocols for gpfdist. Resolved Issues VMware Greenplum 6.17.1 resolves these foo 'my_table' testdb=> SELECT * FROM :foo; would query the table my_table. Note that this may be unsafe: the value of the variable is copied literally, so it can contain unbalanced quotes, or even backslash such as ':foo' doesn't work to produce a quoted literal from a variable's value (and it would be unsafe if it did work, since it wouldn't correctly handle quotes embedded in the value). One example use

one feature. Changed Feature VMware Tanzu Greenplum 6 Documentation VMware, Inc 157 Disabled unsafe TLS 1.0 and TLS 1.1 protocols for gpfdist. Resolved Issues VMware Tanzu Greenplum 6.17.1 resolves foo 'my_table' testdb=> SELECT * FROM :foo; would query the table my_table. Note that this may be unsafe: the value of the variable is copied literally, so it can contain unbalanced quotes, or even backslash such as ':foo' doesn’t work to produce a quoted literal from a variable’s value (and it would be unsafe if it did work, since it wouldn’t correctly handle quotes embedded in the value). One example use

maintenance release that resolves several issues and changes one feature. Changed Feature Deactivated unsafe TLS 1.0 and TLS 1.1 protocols for gpfdist. Resolved Issues VMware Tanzu Greenplum 6.17.1 resolves foo 'my_table' testdb=> SELECT * FROM :foo; would query the table my_table. Note that this may be unsafe: the value of the variable is copied literally, so it can contain unbalanced quotes, or even backslash such as ':foo' doesn’t work to produce a quoted literal from a variable’s value (and it would be unsafe if it did work, since it wouldn’t correctly handle quotes embedded in the value). One example use

maintenance release that resolves several issues and changes one feature. Changed Feature Deactivated unsafe TLS 1.0 and TLS 1.1 protocols for gpfdist. Resolved Issues VMware Tanzu Greenplum 6.17.1 resolves foo 'my_table' testdb=> SELECT * FROM :foo; would query the table my_table. Note that this may be unsafe: the value of the variable is copied literally, so it can contain unbalanced quotes, or even backslash such as ':foo' doesn’t work to produce a quoted literal from a variable’s value (and it would be unsafe if it did work, since it wouldn’t correctly handle quotes embedded in the value). One example use

maintenance release that resolves several issues and changes one feature. Changed Feature Deactivated unsafe TLS 1.0 and TLS 1.1 protocols for gpfdist. Resolved Issues VMware Tanzu Greenplum 6.17.1 resolves foo 'my_table' testdb=> SELECT * FROM :foo; would query the table my_table. Note that this may be unsafe: the value of the variable is copied literally, so it can contain unbalanced quotes, or even backslash such as ':foo' doesn't work to produce a quoted literal from a variable's value (and it would be unsafe if it did work, since it wouldn't correctly handle quotes embedded in the value). One example use

maintenance release that resolves several issues and changes one feature. Changed Feature Deactivated unsafe TLS 1.0 and TLS 1.1 protocols for gpfdist. Resolved Issues VMware Greenplum 6.17.1 resolves these foo 'my_table' testdb=> SELECT * FROM :foo; would query the table my_table. Note that this may be unsafe: the value of the variable is copied literally, so it can contain unbalanced quotes, or even backslash such as ':foo' doesn't work to produce a quoted literal from a variable's value (and it would be unsafe if it did work, since it wouldn't correctly handle quotes embedded in the value). One example use

maintenance release that resolves several issues and changes one feature. Changed Feature Disabled unsafe TLS 1.0 and TLS 1.1 protocols for gpfdist. Resolved Issues VMware Tanzu Greenplum 6.17.1 resolves server. The reason for separating templates from dictionaries is that a template encapsulates the "unsafe" aspects of defining a dictionary. The parameters that can be set when defining a dictionary are foo 'my_table' testdb=> SELECT * FROM :foo; would query the table my_table. Note that this may be unsafe: the value of the variable is copied literally, so it can contain unbalanced quotes, or even backslash

server. The reason for separating templates from dictionaries is that a template encapsulates the "unsafe" aspects of defining a dictionary. The parameters that can be set when defining a dictionary are foo 'my_table' testdb=> SELECT * FROM :foo; would query the table my_table. Note that this may be unsafe: the value of the variable is copied literally, so it can contain unbalanced quotes, or even backslash such as ':foo' doesn't work to produce a quoted literal from a variable's value (and it would be unsafe if it did work, since it wouldn't correctly handle quotes embedded in the value). One example use

server. The reason for separating templates from dictionaries is that a template encapsulates the "unsafe" aspects of defining a dictionary. The parameters that can be set when defining a dictionary are foo 'my_table' testdb=> SELECT * FROM :foo; would query the table my_table. Note that this may be unsafe: the value of the variable is copied literally, so it can contain unbalanced quotes, or even backslash such as ':foo' doesn't work to produce a quoted literal from a variable's value (and it would be unsafe if it did work, since it wouldn't correctly handle quotes embedded in the value). One example use