|
HH
- hour of day (01-12)
+ hour of day (01–12)
|
HH12
- hour of day (01-12)
+ hour of day (01–12)
|
HH24
- hour of day (00-23)
+ hour of day (00–23)
|
MI
- minute (00-59)
+ minute (00–59)
|
SS
- second (00-59)
+ second (00–59)
|
MS
- millisecond (000-999)
+ millisecond (000–999)
|
US
- microsecond (000000-999999)
+ microsecond (000000–999999)
|
FF1
- tenth of second (0-9)
+ tenth of second (0–9)
|
FF2
- hundredth of second (00-99)
+ hundredth of second (00–99)
|
FF3
- millisecond (000-999)
+ millisecond (000–999)
|
FF4
- tenth of a millisecond (0000-9999)
+ tenth of a millisecond (0000–9999)
|
FF5
- hundredth of a millisecond (00000-99999)
+ hundredth of a millisecond (00000–99999)
|
FF6
- microsecond (000000-999999)
+ microsecond (000000–999999)
|
SSSS, SSSSS
- seconds past midnight (0-86399)
+ seconds past midnight (0–86399)
|
AM, am,
|
MM
- month number (01-12)
+ month number (01–12)
|
DAY
|
DDD
- day of year (001-366)
+ day of year (001–366)
|
IDDD
- day of ISO 8601 week-numbering year (001-371; day 1 of the year is Monday of the first ISO week)
+ day of ISO 8601 week-numbering year (001–371; day 1 of the year is Monday of the first ISO week)
|
DD
- day of month (01-31)
+ day of month (01–31)
|
D
|
W
- week of month (1-5) (the first week starts on the first day of the month)
+ week of month (1–5) (the first week starts on the first day of the month)
|
WW
- week number of year (1-53) (the first week starts on the first day of the year)
+ week number of year (1–53) (the first week starts on the first day of the year)
|
IW
- week number of ISO 8601 week-numbering year (01-53; the first Thursday of the year is in week 1)
+ week number of ISO 8601 week-numbering year (01–53; the first Thursday of the year is in week 1)
|
CC
|
RM
- month in upper case Roman numerals (I-XII; I=January)
+ month in upper case Roman numerals (I–XII; I=January)
|
rm
- month in lower case Roman numerals (i-xii; i=January)
+ month in lower case Roman numerals (i–xii; i=January)
|
TZ
For timestamp values, the day (of the month) field
- (1 - 31) ; for interval values, the number of days
+ (1–31) ; for interval values, the number of days
Result: 40
-
-
doy
- The day of the year (1 - 365/366)
+ The day of the year (1–365/366)
hour
- The hour field (0 - 23)
+ The hour field (0–23)
minute
- The minutes field (0 - 59)
+ The minutes field (0–59)
For timestamp values, the number of the month
- within the year (1 - 12) ; for interval values,
- the number of months, modulo 12 (0 - 11)
+ within the year (1–12) ; for interval values,
+ the number of months, modulo 12 (0–11)
quarter
- The quarter of the year (1 - 4) that the date is in
+ The quarter of the year (1–4) that the date is in
|
pg_notification_queue_usage()
double
- fraction of the asynchronous notification queue currently occupied (0-1)
+ fraction of the asynchronous notification queue currently occupied (0–1)
|
to. pg_notification_queue_usage returns the
fraction of the total available space for notifications currently
occupied by notifications that are waiting to be processed, as a
- double in the range 0-1.
+ double in the range 0–1.
See and
for more information.
- Query access - SELECT, COPY TO
+ Query access: SELECT, COPY TO
- Cursor commands - DECLARE, FETCH, CLOSE
+ Cursor commands: DECLARE, FETCH, CLOSE
- Parameters - SHOW, SET, RESET
+ Settings: SHOW, SET, RESET
- Transaction management commands
+ Transaction management commands:
- Plans and resources - PREPARE, EXECUTE,
+ Plans and resources: PREPARE, EXECUTE,
DEALLOCATE, DISCARD
- Plugins and extensions - LOAD
+ Plugins and extensions: LOAD
- Data Manipulation Language (DML) - INSERT,
+ Data Manipulation Language (DML): INSERT,
UPDATE, DELETE, COPY FROM,
TRUNCATE.
Note that there are no allowed actions that result in a trigger
- Data Definition Language (DDL) - CREATE,
+ Data Definition Language (DDL): CREATE,
DROP, ALTER, COMMENT.
This restriction applies even to temporary tables, because carrying
out these operations would require updating the system catalog tables.
- Two-phase commit commands - PREPARE TRANSACTION,
+ Two-phase commit commands: PREPARE TRANSACTION,
COMMIT PREPARED, ROLLBACK PREPARED
because even read-only transactions need to write WAL in the
prepare phase (the first phase of two phase commit).
- Sequence updates - nextval(), setval()
+ Sequence updates: nextval(), setval()
- Data Definition Language (DDL) - e.g. CREATE INDEX
+ Data Definition Language (DDL): e.g. CREATE INDEX
- Privilege and Ownership - GRANT, REVOKE,
+ Privilege and Ownership: GRANT, REVOKE,
REASSIGN
- Maintenance commands - ANALYZE, VACUUM,
+ Maintenance commands: ANALYZE, VACUUM,
CLUSTER, REINDEX
In normal (non-recovery) mode, if you issue DROP USER or DROP ROLE
for a role with login capability while that user is still connected then
- nothing happens to the connected user - they remain connected. The user cannot
+ nothing happens to the connected user — they remain connected. The user cannot
reconnect however. This behavior applies in recovery also, so a
DROP USER on the primary does not disconnect that user on the standby.
and trimmed in size by 25%. Many internal changes improved
performance and
maintainability.
Postgres95 release
- 1.0.x ran about 30-50% faster on the Wisconsin Benchmark compared
+ 1.0.x ran about 30–50% faster on the Wisconsin Benchmark compared
to
POSTGRES, Version 4.2. Apart from
bug fixes, the following were the major enhancements:
Author
- Germán Méndez Bravo (Kronuz), 2004 - 2006
+ Germán Méndez Bravo (Kronuz), 2004–2006
2019
- 1996-2019
+ 1996–2019
The PostgreSQL Global Development Group
Legal Notice
-
PostgreSQL is Copyright © 1996
-2019
+
PostgreSQL is Copyright © 1996
–2019
by the PostgreSQL Global Development Group.
-
Postgres95 is Copyright © 1994
-5
+
Postgres95 is Copyright © 1994
–5
by the Regents of the University of California.
-
<application>libpq</application> <span class="marked">-</span> C Library
+
<application>libpq</application> <span class="marked">—</span> C Library
into equal frequency buckets, so all we have to do is locate the bucket
that our value is in and count part of it and
all of the ones before. The value 1000 is clearly in
- the second bucket (993-1997). Assuming a linear distribution of
+ the second bucket (993–1997). Assuming a linear distribution of
values inside each bucket, we can calculate the selectivity as:
-
PL/Perl <span class="marked">-</span> Perl Procedural Language
+
PL/Perl <span class="marked">—</span> Perl Procedural Language
-
<application>PL/pgSQL</application> <span class="marked">-</span> <acronym>SQL</acronym> Procedural Language
+
<application>PL/pgSQL</application> <span class="marked">—</span> <acronym>SQL</acronym> Procedural Language
-
PL/Python <span class="marked">-</span> Python Procedural Language
+
PL/Python <span class="marked">—</span> Python Procedural Language
-
PL/Tcl <span class="marked">-</span> Tcl Procedural Language
+
PL/Tcl <span class="marked">—</span> Tcl Procedural Language
These forms control the application of row security policies belonging
to the table. If enabled and no policies exist for the table, then a
default-deny policy is applied. Note that policies can exist for a table
- even if row level security is disabled - in this case, the policies will
- NOT be applied and the policies will be ignored.
+ even if row level security is disabled. In this case, the policies will
+ not be applied and the policies will be ignored.
See also
.
are numbered from 0 (
LSB) to 31 (
MSB). Note that
this field is stored in network byte order (most significant byte first),
as are all the integer fields used in the file format. Bits
-16-31 are reserved to denote critical file format issues; a reader
-should abort if it finds an unexpected bit set in this range. Bits 0-15
+16–31 are reserved to denote critical file format issues; a reader
+should abort if it finds an unexpected bit set in this range. Bits 0–15
are reserved to signal backwards-compatible format issues; a reader
should simply ignore any unexpected bits set in this range. Currently
only one flag bit is defined, and the rest must be zero:
Do not throw an error if a relation with the same name already exists.
A notice is issued in this case. Note that there is no guarantee that
the existing relation is anything like the sequence that would have
- been created - it might not even be a sequence.
+ been created — it might not even be a sequence.
we try to move long column values into TOAST tables, and is also the
target length we try to reduce the length below once toasting begins.
This only affects columns marked as either External or Extended
- and applies only to new tuples - there is no effect on existing rows.
+ and applies only to new tuples; there is no effect on existing rows.
By default this parameter is set to allow at least 4 tuples per block,
which with the default blocksize will be 2040 bytes. Valid values are
between 128 bytes and the (blocksize - header), by default 8160 bytes.
\o,
\oo,
\ooo
- (o = 0 - 7)
+ (o = 0–7)
octal byte value
\xh,
\xhh
- (h = 0 - 9, A - F)
+ (h = 0–9, A–F)
hexadecimal byte value
\uxxxx,
\Uxxxxxxxx
- (x = 0 - 9, A - F)
+ (x = 0–9, A–F)
16 or 32-bit hexadecimal Unicode character value
- Linguistic - Ispell dictionaries try to reduce input words to a
+ Linguistic — Ispell dictionaries try to reduce input words to a
normalized form; stemmer dictionaries remove word endings
projects / postgresql.git / commitdiff