Possible values are:
-
'c' = CHAR alignment, ie no alignment needed.+
'c' = CHAR alignment, i.e., no alignment needed.
's' = SHORT alignment (2 bytes on most machines).
Deprecated
- The money is now deprecated. Use
+ The money type is deprecated. Use
numeric or decimal instead, in
combination with the to_char function. The
money type may become a locale-aware layer over the
Estimated start-up cost (time expended before output scan can start,
- eg, time to do the sorting in a SORT node).
+ e.g., time to do the sorting in a SORT node).
A warning message has been issued in relation to the query.
- Notices are in addition to other responses, ie. the backend
+ Notices are in addition to other responses, i.e., the backend
will continue processing the command.
A warning message has been issued in relation to the function
call.
- Notices are in addition to other responses, ie. the backend
+ Notices are in addition to other responses, i.e., the backend
will continue processing the command.
-
+
Queries
-T1 { INNER | { LEFT | RIGHT | FULL } OUTER } JOIN T2 ON boolean expression
+T1 { INNER | { LEFT | RIGHT | FULL } OUTER } JOIN T2 ON boolean_expression
T1 { INNER | { LEFT | RIGHT | FULL } OUTER } JOIN T2 USING ( join column list )
T1 NATURAL { INNER | { LEFT | RIGHT | FULL } OUTER } JOIN T2
The syntax of the WHERE clause is
-WHERE search condition
+WHERE search_condition
- where search condition is any value
+ where search_condition is any value
expression as defined in that
returns a value of type boolean.
Select Lists
- The table expression in the SELECT command
+ As shown in the previous section,
+ the table expression in the SELECT command
constructs an intermediate virtual table by possibly combining
tables, views, eliminating rows, grouping, etc. This table is
- finally passed on to processing by the select list. The select
+ finally passed on to processing by the select list. The select
list determines which columns of the
intermediate table are actually output. The simplest kind of select list
is * which emits all columns that the table
Observe the correct number of backslashes (6)! You can resolve it this way: After
psql has parsed this line, it passes
sed -e "s/'/\\\'/g" < my_file.txt to the shell. The shell
- will do it's own thing inside the double quotes and execute sed
+ will do its own thing inside the double quotes and execute sed
with the arguments -e and s/'/\\'/g.
When
sed parses this it will replace the two
backslashes with a single one and then do the substitution. Perhaps at
LEFT OUTER JOIN returns all rows in the qualified Cartesian product
- (ie, all combined rows that pass its ON condition), plus one copy of each
+ (i.e., all combined rows that pass its ON condition), plus one copy of each
row in the left-hand table for which there was no right-hand row that
passed the ON condition. This left-hand row is extended to the full
width of the joined table by inserting NULLs for the right-hand columns.
Also observe that it makes no sense to ask for an aggregate of an
- aggregate, eg, AVG(MAX(sno)), because a SELECT only does one pass
+ aggregate, e.g., AVG(MAX(sno)), because a SELECT only does one pass
of grouping and aggregation. You can get a result of this kind by
using a temporary table or a sub-SELECT in the FROM clause to
do the first level of aggregation.
the state variable and then start applying the transition function
at the second non-null input value.
Postgres will do that automatically if the initial condition is NULL and
- the transition function is marked "strict" (ie, not to be called
+ the transition function is marked "strict" (i.e., not to be called
for NULL inputs).
impose a strict ordering on keys, lesser to greater. Since
Postgres allows the user to define operators,
Postgres cannot look at the name of an operator
- (eg, ">" or "<") and tell what kind of comparison it is. In fact,
+ (e.g., ">" or "<") and tell what kind of comparison it is. In fact,
some access methods don't impose any ordering at all. For example,
R-trees express a rectangle-containment relationship,
whereas a hashed data structure expresses only bitwise similarity based
The
PostgreSQL Global Development Group provides
the
PostgreSQL software code tree as a public service,
- without warranty and without liability for it's behavior or performance.
+ without warranty and without liability for its behavior or performance.
However, at the time of writing:
projects / postgresql.git / commitdiff