...................................................................... 2604 69.1. Backup Manifest Top-level Object ....................................................... 2604 69.2. Backup Manifest File string had been written as one constant. For example: SELECT 'foo' 'bar'; is equivalent to: SELECT 'foobar'; but: SELECT 'foo' 'bar'; is not valid syntax. (This slightly bizarre behavior is specified expanded to a list of the elements of the row value, just as occurs when the .* syntax is used at the top level of a SELECT list (see Section 8.16.5). For example, if table t has columns f1 and f2, these are

...................................................................... 2756 69.1. Backup Manifest Top-level Object ............................................................ 2756 69.2. Backup Manifest string had been written as one constant. For example: SELECT 'foo' 'bar'; is equivalent to: SELECT 'foobar'; but: SELECT 'foo' 'bar'; is not valid syntax. (This slightly bizarre behavior is specified expanded to a list of the elements of the row value, just as occurs when the .* syntax is used at the top level of a SELECT list (see Sec- tion 8.16.5). For example, if table t has columns f1 and f2, these

...................................................................... 2546 77.1. Backup Manifest Top-level Object ....................................................... 2546 77.2. Backup Manifest File string had been written as one constant. For example: SELECT 'foo' 'bar'; is equivalent to: SELECT 'foobar'; but: SELECT 'foo' 'bar'; is not valid syntax. (This slightly bizarre behavior is specified expanded to a list of the elements of the row value, just as occurs when the .* syntax is used at the top level of a SELECT list (see Section 8.16.5). For example, if table t has columns f1 and f2, these are

...................................................................... 2685 77.1. Backup Manifest Top-level Object ............................................................ 2685 77.2. Backup Manifest string had been written as one constant. For example: SELECT 'foo' 'bar'; is equivalent to: SELECT 'foobar'; but: SELECT 'foo' 'bar'; is not valid syntax. (This slightly bizarre behavior is specified expanded to a list of the elements of the row value, just as occurs when the .* syntax is used at the top level of a SELECT list (see Sec- tion 8.16.5). For example, if table t has columns f1 and f2, these

...................................................................... 2500 76.1. Backup Manifest Top-level Object ....................................................... 2500 76.2. Backup Manifest File string had been written as one constant. For example: SELECT 'foo' 'bar'; is equivalent to: SELECT 'foobar'; but: SELECT 'foo' 'bar'; is not valid syntax. (This slightly bizarre behavior is specified expanded to a list of the elements of the row value, just as occurs when the .* syntax is used at the top level of a SELECT list (see Section 8.16.5). For example, if table t has columns f1 and f2, these are

...................................................................... 2642 76.1. Backup Manifest Top-level Object ............................................................ 2642 76.2. Backup Manifest string had been written as one constant. For example: SELECT 'foo' 'bar'; is equivalent to: SELECT 'foobar'; but: SELECT 'foo' 'bar'; is not valid syntax. (This slightly bizarre behavior is specified expanded to a list of the elements of the row value, just as occurs when the .* syntax is used at the top level of a SELECT list (see Sec- tion 8.16.5). For example, if table t has columns f1 and f2, these

string had been written as one constant. For example: SELECT ’foo’ ’bar’; is equivalent to: SELECT ’foobar’; but: SELECT ’foo’ ’bar’; is not valid syntax. (This slightly bizarre behavior is specified expanded to a list of the ele- ments of the row value, just as occurs when the .* syntax is used at the top level of a SELECT list (see Section 8.16.5). For example, if table t has columns f1 and f2, these are a":40,"b":"foo"},{"a":"100","b":"bar"}]’) AS (a INTEGER, b TEXT), generate_series(1, 3) ) AS x (p, q, s) ORDER BY p; p | q | s -----+-----+--- 40 | foo | 1 100 | bar | 2 | | 3 It joins two functions

string had been written as one constant. For example: SELECT ’foo’ ’bar’; is equivalent to: SELECT ’foobar’; but: SELECT ’foo’ ’bar’; is not valid syntax. (This slightly bizarre behavior is specified expanded to a list of the elements of the row value, just as occurs when the .* syntax is used at the top level of a SELECT list (see Section 8.16.5). For example, if table t has columns f1 and f2, these are a":40,"b":"foo"},{"a":"100","b":"bar"}]’) AS (a INTEGER, b TEXT), generate_series(1, 3) ) AS x (p, q, s) ORDER BY p; p | q | s -----+-----+--- 40 | foo | 1 100 | bar | 2 | | 3 It joins two functions

string had been written as one constant. For example: SELECT ’foo’ ’bar’; is equivalent to: SELECT ’foobar’; but: SELECT ’foo’ ’bar’; is not valid syntax. (This slightly bizarre behavior is specified expanded to a list of the elements of the row value, just as occurs when the .* syntax is used at the top level of a SELECT list (see Section 8.16.5). For example, if table t has columns f1 and f2, these are references to columns provided by preceding FROM items in any case. A LATERAL item can appear at top level in the FROM list, or within a JOIN tree. In the latter case it can also refer to any items that

string had been written as one constant. For example: SELECT ’foo’ ’bar’; is equivalent to: SELECT ’foobar’; but: SELECT ’foo’ ’bar’; is not valid syntax. (This slightly bizarre behavior is specified expanded to a list of the ele- ments of the row value, just as occurs when the .* syntax is used at the top level of a SELECT list (see Section 8.16.5). For example, if table t has columns f1 and f2, these are references to columns provided by preceding FROM items in any case. A LATERAL item can appear at top level in the FROM list, or within a JOIN tree. In the latter case it can also refer to any items that