1 <!-- $PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.486 2009/08/10 18:29:26 tgl Exp $ -->
3 <chapter id="functions">
4 <title>Functions and Operators</title>
6 <indexterm zone="functions">
7 <primary>function</primary>
10 <indexterm zone="functions">
11 <primary>operator</primary>
15 <productname>PostgreSQL</productname> provides a large number of
16 functions and operators for the built-in data types. Users can also
17 define their own functions and operators, as described in
18 <xref linkend="server-programming">. The
19 <application>psql</application> commands <command>\df</command> and
20 <command>\do</command> can be used to list all
21 available functions and operators, respectively.
25 If you are concerned about portability then note that most of
26 the functions and operators described in this chapter, with the
27 exception of the most trivial arithmetic and comparison operators
28 and some explicitly marked functions, are not specified by the
29 <acronym>SQL</acronym> standard. Some of this extended functionality
30 is present in other <acronym>SQL</acronym> database management
31 systems, and in many cases this functionality is compatible and
32 consistent between the various implementations. This chapter is also
33 not exhaustive; additional functions appear in relevant sections of
38 <sect1 id="functions-logical">
39 <title>Logical Operators</title>
41 <indexterm zone="functions-logical">
42 <primary>operator</primary>
43 <secondary>logical</secondary>
47 <primary>Boolean</primary>
48 <secondary>operators</secondary>
49 <see>operators, logical</see>
53 The usual logical operators are available:
56 <primary>AND (operator)</primary>
60 <primary>OR (operator)</primary>
64 <primary>NOT (operator)</primary>
68 <primary>conjunction</primary>
72 <primary>disjunction</primary>
76 <primary>negation</primary>
80 <member><literal>AND</></member>
81 <member><literal>OR</></member>
82 <member><literal>NOT</></member>
85 <acronym>SQL</acronym> uses a three-valued Boolean logic where the null value represents
86 <quote>unknown</quote>. Observe the following truth tables:
92 <entry><replaceable>a</replaceable></entry>
93 <entry><replaceable>b</replaceable></entry>
94 <entry><replaceable>a</replaceable> AND <replaceable>b</replaceable></entry>
95 <entry><replaceable>a</replaceable> OR <replaceable>b</replaceable></entry>
149 <entry><replaceable>a</replaceable></entry>
150 <entry>NOT <replaceable>a</replaceable></entry>
175 The operators <literal>AND</literal> and <literal>OR</literal> are
176 commutative, that is, you can switch the left and right operand
177 without affecting the result. But see <xref
178 linkend="syntax-express-eval"> for more information about the
179 order of evaluation of subexpressions.
183 <sect1 id="functions-comparison">
184 <title>Comparison Operators</title>
186 <indexterm zone="functions-comparison">
187 <primary>comparison</primary>
188 <secondary>operators</secondary>
192 The usual comparison operators are available, shown in <xref
193 linkend="functions-comparison-table">.
196 <table id="functions-comparison-table">
197 <title>Comparison Operators</title>
201 <entry>Operator</entry>
202 <entry>Description</entry>
208 <entry> <literal><</literal> </entry>
209 <entry>less than</entry>
213 <entry> <literal>></literal> </entry>
214 <entry>greater than</entry>
218 <entry> <literal><=</literal> </entry>
219 <entry>less than or equal to</entry>
223 <entry> <literal>>=</literal> </entry>
224 <entry>greater than or equal to</entry>
228 <entry> <literal>=</literal> </entry>
233 <entry> <literal><></literal> or <literal>!=</literal> </entry>
234 <entry>not equal</entry>
242 The <literal>!=</literal> operator is converted to
243 <literal><></literal> in the parser stage. It is not
244 possible to implement <literal>!=</literal> and
245 <literal><></literal> operators that do different things.
250 Comparison operators are available for all relevant data types.
251 All comparison operators are binary operators that
252 return values of type <type>boolean</type>; expressions like
253 <literal>1 < 2 < 3</literal> are not valid (because there is
254 no <literal><</literal> operator to compare a Boolean value with
255 <literal>3</literal>).
260 <primary>BETWEEN</primary>
262 In addition to the comparison operators, the special
263 <token>BETWEEN</token> construct is available:
265 <replaceable>a</replaceable> BETWEEN <replaceable>x</replaceable> AND <replaceable>y</replaceable>
269 <replaceable>a</replaceable> >= <replaceable>x</replaceable> AND <replaceable>a</replaceable> <= <replaceable>y</replaceable>
271 Notice that <token>BETWEEN</token> treats the endpoint values as included
273 <literal>NOT BETWEEN</literal> does the opposite comparison:
275 <replaceable>a</replaceable> NOT BETWEEN <replaceable>x</replaceable> AND <replaceable>y</replaceable>
279 <replaceable>a</replaceable> < <replaceable>x</replaceable> OR <replaceable>a</replaceable> > <replaceable>y</replaceable>
282 <primary>BETWEEN SYMMETRIC</primary>
284 <literal>BETWEEN SYMMETRIC</> is the same as <literal>BETWEEN</>
285 except there is no requirement that the argument to the left of
286 <literal>AND</> be less than or equal to the argument on the right.
287 If it is not, those two arguments are automatically swapped, so that
288 a nonempty range is always implied.
293 <primary>IS NULL</primary>
296 <primary>IS NOT NULL</primary>
299 <primary>ISNULL</primary>
302 <primary>NOTNULL</primary>
304 To check whether a value is or is not null, use the constructs:
306 <replaceable>expression</replaceable> IS NULL
307 <replaceable>expression</replaceable> IS NOT NULL
309 or the equivalent, but nonstandard, constructs:
311 <replaceable>expression</replaceable> ISNULL
312 <replaceable>expression</replaceable> NOTNULL
314 <indexterm><primary>null value</primary><secondary>comparing</secondary></indexterm>
318 Do <emphasis>not</emphasis> write
319 <literal><replaceable>expression</replaceable> = NULL</literal>
320 because <literal>NULL</> is not <quote>equal to</quote>
321 <literal>NULL</>. (The null value represents an unknown value,
322 and it is not known whether two unknown values are equal.) This
323 behavior conforms to the SQL standard.
328 Some applications might expect that
329 <literal><replaceable>expression</replaceable> = NULL</literal>
330 returns true if <replaceable>expression</replaceable> evaluates to
331 the null value. It is highly recommended that these applications
332 be modified to comply with the SQL standard. However, if that
333 cannot be done the <xref linkend="guc-transform-null-equals">
334 configuration variable is available. If it is enabled,
335 <productname>PostgreSQL</productname> will convert <literal>x =
336 NULL</literal> clauses to <literal>x IS NULL</literal>.
342 If the <replaceable>expression</replaceable> is row-valued, then
343 <literal>IS NULL</> is true when the row expression itself is null
344 or when all the row's fields are null, while
345 <literal>IS NOT NULL</> is true when the row expression itself is non-null
346 and all the row's fields are non-null. Because of this behavior,
347 <literal>IS NULL</> and <literal>IS NOT NULL</> do not always return
348 inverse results for row-valued expressions, i.e., a row-valued
349 expression that contains both NULL and non-null values will return false
351 This definition conforms to the SQL standard, and is a change from the
352 inconsistent behavior exhibited by <productname>PostgreSQL</productname>
353 versions prior to 8.2.
359 <primary>IS DISTINCT FROM</primary>
362 <primary>IS NOT DISTINCT FROM</primary>
364 Ordinary comparison operators yield null (signifying <quote>unknown</>),
365 not true or false, when either input is null. For example,
366 <literal>7 = NULL</> yields null. When this behavior is not suitable,
368 <literal>IS <optional> NOT </> DISTINCT FROM</literal> constructs:
370 <replaceable>expression</replaceable> IS DISTINCT FROM <replaceable>expression</replaceable>
371 <replaceable>expression</replaceable> IS NOT DISTINCT FROM <replaceable>expression</replaceable>
373 For non-null inputs, <literal>IS DISTINCT FROM</literal> is
374 the same as the <literal><></> operator. However, if both
375 inputs are null it returns false, and if only one input is
376 null it returns true. Similarly, <literal>IS NOT DISTINCT
377 FROM</literal> is identical to <literal>=</literal> for non-null
378 inputs, but it returns true when both inputs are null, and false when only
379 one input is null. Thus, these constructs effectively act as though null
380 were a normal data value, rather than <quote>unknown</>.
385 <primary>IS TRUE</primary>
388 <primary>IS NOT TRUE</primary>
391 <primary>IS FALSE</primary>
394 <primary>IS NOT FALSE</primary>
397 <primary>IS UNKNOWN</primary>
400 <primary>IS NOT UNKNOWN</primary>
402 Boolean values can also be tested using the constructs
404 <replaceable>expression</replaceable> IS TRUE
405 <replaceable>expression</replaceable> IS NOT TRUE
406 <replaceable>expression</replaceable> IS FALSE
407 <replaceable>expression</replaceable> IS NOT FALSE
408 <replaceable>expression</replaceable> IS UNKNOWN
409 <replaceable>expression</replaceable> IS NOT UNKNOWN
411 These will always return true or false, never a null value, even when the
413 A null input is treated as the logical value <quote>unknown</>.
414 Notice that <literal>IS UNKNOWN</> and <literal>IS NOT UNKNOWN</> are
415 effectively the same as <literal>IS NULL</literal> and
416 <literal>IS NOT NULL</literal>, respectively, except that the input
417 expression must be of Boolean type.
420 <!-- IS OF does not conform to the ISO SQL behavior, so it is undocumented here
423 <primary>IS OF</primary>
426 <primary>IS NOT OF</primary>
428 It is possible to check the data type of an expression using the
431 <replaceable>expression</replaceable> IS OF (typename, ...)
432 <replaceable>expression</replaceable> IS NOT OF (typename, ...)
434 They return a boolean value based on whether the expression's data
435 type is one of the listed data types.
441 <sect1 id="functions-math">
442 <title>Mathematical Functions and Operators</title>
445 Mathematical operators are provided for many
446 <productname>PostgreSQL</productname> types. For types without
447 standard mathematical conventions
448 (e.g., date/time types) we
449 describe the actual behavior in subsequent sections.
453 <xref linkend="functions-math-op-table"> shows the available mathematical operators.
456 <table id="functions-math-op-table">
457 <title>Mathematical Operators</title>
462 <entry>Operator</entry>
463 <entry>Description</entry>
464 <entry>Example</entry>
465 <entry>Result</entry>
471 <entry> <literal>+</literal> </entry>
472 <entry>addition</entry>
473 <entry><literal>2 + 3</literal></entry>
474 <entry><literal>5</literal></entry>
478 <entry> <literal>-</literal> </entry>
479 <entry>subtraction</entry>
480 <entry><literal>2 - 3</literal></entry>
481 <entry><literal>-1</literal></entry>
485 <entry> <literal>*</literal> </entry>
486 <entry>multiplication</entry>
487 <entry><literal>2 * 3</literal></entry>
488 <entry><literal>6</literal></entry>
492 <entry> <literal>/</literal> </entry>
493 <entry>division (integer division truncates the result)</entry>
494 <entry><literal>4 / 2</literal></entry>
495 <entry><literal>2</literal></entry>
499 <entry> <literal>%</literal> </entry>
500 <entry>modulo (remainder)</entry>
501 <entry><literal>5 % 4</literal></entry>
502 <entry><literal>1</literal></entry>
506 <entry> <literal>^</literal> </entry>
507 <entry>exponentiation</entry>
508 <entry><literal>2.0 ^ 3.0</literal></entry>
509 <entry><literal>8</literal></entry>
513 <entry> <literal>|/</literal> </entry>
514 <entry>square root</entry>
515 <entry><literal>|/ 25.0</literal></entry>
516 <entry><literal>5</literal></entry>
520 <entry> <literal>||/</literal> </entry>
521 <entry>cube root</entry>
522 <entry><literal>||/ 27.0</literal></entry>
523 <entry><literal>3</literal></entry>
527 <entry> <literal>!</literal> </entry>
528 <entry>factorial</entry>
529 <entry><literal>5 !</literal></entry>
530 <entry><literal>120</literal></entry>
534 <entry> <literal>!!</literal> </entry>
535 <entry>factorial (prefix operator)</entry>
536 <entry><literal>!! 5</literal></entry>
537 <entry><literal>120</literal></entry>
541 <entry> <literal>@</literal> </entry>
542 <entry>absolute value</entry>
543 <entry><literal>@ -5.0</literal></entry>
544 <entry><literal>5</literal></entry>
548 <entry> <literal>&</literal> </entry>
549 <entry>bitwise AND</entry>
550 <entry><literal>91 & 15</literal></entry>
551 <entry><literal>11</literal></entry>
555 <entry> <literal>|</literal> </entry>
556 <entry>bitwise OR</entry>
557 <entry><literal>32 | 3</literal></entry>
558 <entry><literal>35</literal></entry>
562 <entry> <literal>#</literal> </entry>
563 <entry>bitwise XOR</entry>
564 <entry><literal>17 # 5</literal></entry>
565 <entry><literal>20</literal></entry>
569 <entry> <literal>~</literal> </entry>
570 <entry>bitwise NOT</entry>
571 <entry><literal>~1</literal></entry>
572 <entry><literal>-2</literal></entry>
576 <entry> <literal><<</literal> </entry>
577 <entry>bitwise shift left</entry>
578 <entry><literal>1 << 4</literal></entry>
579 <entry><literal>16</literal></entry>
583 <entry> <literal>>></literal> </entry>
584 <entry>bitwise shift right</entry>
585 <entry><literal>8 >> 2</literal></entry>
586 <entry><literal>2</literal></entry>
594 The bitwise operators work only on integral data types, whereas
595 the others are available for all numeric data types. The bitwise
596 operators are also available for the bit
597 string types <type>bit</type> and <type>bit varying</type>, as
598 shown in <xref linkend="functions-bit-string-op-table">.
602 <xref linkend="functions-math-func-table"> shows the available
603 mathematical functions. In the table, <literal>dp</literal>
604 indicates <type>double precision</type>. Many of these functions
605 are provided in multiple forms with different argument types.
606 Except where noted, any given form of a function returns the same
607 data type as its argument.
608 The functions working with <type>double precision</type> data are mostly
609 implemented on top of the host system's C library; accuracy and behavior in
610 boundary cases can therefore vary depending on the host system.
614 <primary>abs</primary>
617 <primary>cbrt</primary>
620 <primary>ceiling</primary>
623 <primary>degrees</primary>
626 <primary>div</primary>
629 <primary>exp</primary>
632 <primary>floor</primary>
635 <primary>ln</primary>
638 <primary>log</primary>
641 <primary>mod</primary>
644 <primary>pi</primary>
647 <primary>power</primary>
650 <primary>radians</primary>
653 <primary>random</primary>
656 <primary>round</primary>
659 <primary>setseed</primary>
662 <primary>sign</primary>
665 <primary>sqrt</primary>
668 <primary>trunc</primary>
671 <primary>width_bucket</primary>
674 <table id="functions-math-func-table">
675 <title>Mathematical Functions</title>
679 <entry>Function</entry>
680 <entry>Return Type</entry>
681 <entry>Description</entry>
682 <entry>Example</entry>
683 <entry>Result</entry>
689 <entry><literal><function>abs</>(<replaceable>x</replaceable>)</literal></entry>
690 <entry>(same as input)</entry>
691 <entry>absolute value</entry>
692 <entry><literal>abs(-17.4)</literal></entry>
693 <entry><literal>17.4</literal></entry>
697 <entry><literal><function>cbrt</function>(<type>dp</type>)</literal></entry>
698 <entry><type>dp</type></entry>
699 <entry>cube root</entry>
700 <entry><literal>cbrt(27.0)</literal></entry>
701 <entry><literal>3</literal></entry>
705 <entry><literal><function>ceil</function>(<type>dp</type> or <type>numeric</type>)</literal></entry>
706 <entry>(same as input)</entry>
707 <entry>smallest integer not less than argument</entry>
708 <entry><literal>ceil(-42.8)</literal></entry>
709 <entry><literal>-42</literal></entry>
713 <entry><literal><function>ceiling</function>(<type>dp</type> or <type>numeric</type>)</literal></entry>
714 <entry>(same as input)</entry>
715 <entry>smallest integer not less than argument (alias for <function>ceil</function>)</entry>
716 <entry><literal>ceiling(-95.3)</literal></entry>
717 <entry><literal>-95</literal></entry>
721 <entry><literal><function>degrees</function>(<type>dp</type>)</literal></entry>
722 <entry><type>dp</type></entry>
723 <entry>radians to degrees</entry>
724 <entry><literal>degrees(0.5)</literal></entry>
725 <entry><literal>28.6478897565412</literal></entry>
729 <entry><literal><function>div</function>(<parameter>y</parameter> <type>numeric</>,
730 <parameter>x</parameter> <type>numeric</>)</literal></entry>
731 <entry><type>numeric</></entry>
732 <entry>integer quotient of <parameter>y</parameter>/<parameter>x</parameter></entry>
733 <entry><literal>div(9,4)</literal></entry>
734 <entry><literal>2</literal></entry>
738 <entry><literal><function>exp</function>(<type>dp</type> or <type>numeric</type>)</literal></entry>
739 <entry>(same as input)</entry>
740 <entry>exponential</entry>
741 <entry><literal>exp(1.0)</literal></entry>
742 <entry><literal>2.71828182845905</literal></entry>
746 <entry><literal><function>floor</function>(<type>dp</type> or <type>numeric</type>)</literal></entry>
747 <entry>(same as input)</entry>
748 <entry>largest integer not greater than argument</entry>
749 <entry><literal>floor(-42.8)</literal></entry>
750 <entry><literal>-43</literal></entry>
754 <entry><literal><function>ln</function>(<type>dp</type> or <type>numeric</type>)</literal></entry>
755 <entry>(same as input)</entry>
756 <entry>natural logarithm</entry>
757 <entry><literal>ln(2.0)</literal></entry>
758 <entry><literal>0.693147180559945</literal></entry>
762 <entry><literal><function>log</function>(<type>dp</type> or <type>numeric</type>)</literal></entry>
763 <entry>(same as input)</entry>
764 <entry>base 10 logarithm</entry>
765 <entry><literal>log(100.0)</literal></entry>
766 <entry><literal>2</literal></entry>
770 <entry><literal><function>log</function>(<parameter>b</parameter> <type>numeric</type>,
771 <parameter>x</parameter> <type>numeric</type>)</literal></entry>
772 <entry><type>numeric</type></entry>
773 <entry>logarithm to base <parameter>b</parameter></entry>
774 <entry><literal>log(2.0, 64.0)</literal></entry>
775 <entry><literal>6.0000000000</literal></entry>
779 <entry><literal><function>mod</function>(<parameter>y</parameter>,
780 <parameter>x</parameter>)</literal></entry>
781 <entry>(same as argument types)</entry>
782 <entry>remainder of <parameter>y</parameter>/<parameter>x</parameter></entry>
783 <entry><literal>mod(9,4)</literal></entry>
784 <entry><literal>1</literal></entry>
788 <entry><literal><function>pi</function>()</literal></entry>
789 <entry><type>dp</type></entry>
790 <entry><quote>π</quote> constant</entry>
791 <entry><literal>pi()</literal></entry>
792 <entry><literal>3.14159265358979</literal></entry>
796 <entry><literal><function>power</function>(<parameter>a</parameter> <type>dp</type>,
797 <parameter>b</parameter> <type>dp</type>)</literal></entry>
798 <entry><type>dp</type></entry>
799 <entry><parameter>a</> raised to the power of <parameter>b</parameter></entry>
800 <entry><literal>power(9.0, 3.0)</literal></entry>
801 <entry><literal>729</literal></entry>
805 <entry><literal><function>power</function>(<parameter>a</parameter> <type>numeric</type>,
806 <parameter>b</parameter> <type>numeric</type>)</literal></entry>
807 <entry><type>numeric</type></entry>
808 <entry><parameter>a</> raised to the power of <parameter>b</parameter></entry>
809 <entry><literal>power(9.0, 3.0)</literal></entry>
810 <entry><literal>729</literal></entry>
814 <entry><literal><function>radians</function>(<type>dp</type>)</literal></entry>
815 <entry><type>dp</type></entry>
816 <entry>degrees to radians</entry>
817 <entry><literal>radians(45.0)</literal></entry>
818 <entry><literal>0.785398163397448</literal></entry>
822 <entry><literal><function>random</function>()</literal></entry>
823 <entry><type>dp</type></entry>
824 <entry>random value between 0.0 and 1.0, inclusive</entry>
825 <entry><literal>random()</literal></entry>
830 <entry><literal><function>round</function>(<type>dp</type> or <type>numeric</type>)</literal></entry>
831 <entry>(same as input)</entry>
832 <entry>round to nearest integer</entry>
833 <entry><literal>round(42.4)</literal></entry>
834 <entry><literal>42</literal></entry>
838 <entry><literal><function>round</function>(<parameter>v</parameter> <type>numeric</type>, <parameter>s</parameter> <type>int</type>)</literal></entry>
839 <entry><type>numeric</type></entry>
840 <entry>round to <parameter>s</parameter> decimal places</entry>
841 <entry><literal>round(42.4382, 2)</literal></entry>
842 <entry><literal>42.44</literal></entry>
846 <entry><literal><function>setseed</function>(<type>dp</type>)</literal></entry>
847 <entry><type>void</type></entry>
848 <entry>set seed for subsequent <literal>random()</literal> calls (value between -1.0 and
849 1.0, inclusive)</entry>
850 <entry><literal>setseed(0.54823)</literal></entry>
855 <entry><literal><function>sign</function>(<type>dp</type> or <type>numeric</type>)</literal></entry>
856 <entry>(same as input)</entry>
857 <entry>sign of the argument (-1, 0, +1)</entry>
858 <entry><literal>sign(-8.4)</literal></entry>
859 <entry><literal>-1</literal></entry>
863 <entry><literal><function>sqrt</function>(<type>dp</type> or <type>numeric</type>)</literal></entry>
864 <entry>(same as input)</entry>
865 <entry>square root</entry>
866 <entry><literal>sqrt(2.0)</literal></entry>
867 <entry><literal>1.4142135623731</literal></entry>
871 <entry><literal><function>trunc</function>(<type>dp</type> or <type>numeric</type>)</literal></entry>
872 <entry>(same as input)</entry>
873 <entry>truncate toward zero</entry>
874 <entry><literal>trunc(42.8)</literal></entry>
875 <entry><literal>42</literal></entry>
879 <entry><literal><function>trunc</function>(<parameter>v</parameter> <type>numeric</type>, <parameter>s</parameter> <type>int</type>)</literal></entry>
880 <entry><type>numeric</type></entry>
881 <entry>truncate to <parameter>s</parameter> decimal places</entry>
882 <entry><literal>trunc(42.4382, 2)</literal></entry>
883 <entry><literal>42.43</literal></entry>
887 <entry><literal><function>width_bucket</function>(<parameter>op</parameter> <type>numeric</type>, <parameter>b1</parameter> <type>numeric</type>, <parameter>b2</parameter> <type>numeric</type>, <parameter>count</parameter> <type>int</type>)</literal></entry>
888 <entry><type>int</type></entry>
889 <entry>return the bucket to which <parameter>operand</> would
890 be assigned in an equidepth histogram with <parameter>count</>
891 buckets, in the range <parameter>b1</> to <parameter>b2</></entry>
892 <entry><literal>width_bucket(5.35, 0.024, 10.06, 5)</literal></entry>
893 <entry><literal>3</literal></entry>
897 <entry><literal><function>width_bucket</function>(<parameter>op</parameter> <type>dp</type>, <parameter>b1</parameter> <type>dp</type>, <parameter>b2</parameter> <type>dp</type>, <parameter>count</parameter> <type>int</type>)</literal></entry>
898 <entry><type>int</type></entry>
899 <entry>return the bucket to which <parameter>operand</> would
900 be assigned in an equidepth histogram with <parameter>count</>
901 buckets, in the range <parameter>b1</> to <parameter>b2</></entry>
902 <entry><literal>width_bucket(5.35, 0.024, 10.06, 5)</literal></entry>
903 <entry><literal>3</literal></entry>
910 Finally, <xref linkend="functions-math-trig-table"> shows the
911 available trigonometric functions. All trigonometric functions
912 take arguments and return values of type <type>double
917 <primary>acos</primary>
920 <primary>asin</primary>
923 <primary>atan</primary>
926 <primary>atan2</primary>
929 <primary>cos</primary>
932 <primary>cot</primary>
935 <primary>sin</primary>
938 <primary>tan</primary>
941 <table id="functions-math-trig-table">
942 <title>Trigonometric Functions</title>
947 <entry>Function</entry>
948 <entry>Description</entry>
954 <entry><literal><function>acos</function>(<replaceable>x</replaceable>)</literal></entry>
955 <entry>inverse cosine</entry>
959 <entry><literal><function>asin</function>(<replaceable>x</replaceable>)</literal></entry>
960 <entry>inverse sine</entry>
964 <entry><literal><function>atan</function>(<replaceable>x</replaceable>)</literal></entry>
965 <entry>inverse tangent</entry>
969 <entry><literal><function>atan2</function>(<replaceable>y</replaceable>,
970 <replaceable>x</replaceable>)</literal></entry>
971 <entry>inverse tangent of
972 <literal><replaceable>y</replaceable>/<replaceable>x</replaceable></literal></entry>
976 <entry><literal><function>cos</function>(<replaceable>x</replaceable>)</literal></entry>
977 <entry>cosine</entry>
981 <entry><literal><function>cot</function>(<replaceable>x</replaceable>)</literal></entry>
982 <entry>cotangent</entry>
986 <entry><literal><function>sin</function>(<replaceable>x</replaceable>)</literal></entry>
991 <entry><literal><function>tan</function>(<replaceable>x</replaceable>)</literal></entry>
992 <entry>tangent</entry>
1001 <sect1 id="functions-string">
1002 <title>String Functions and Operators</title>
1005 This section describes functions and operators for examining and
1006 manipulating string values. Strings in this context include values
1007 of the types <type>character</type>, <type>character varying</type>,
1008 and <type>text</type>. Unless otherwise noted, all
1009 of the functions listed below work on all of these types, but be
1010 wary of potential effects of automatic space-padding when using the
1011 <type>character</type> type. Some functions also exist
1012 natively for the bit-string types.
1016 <acronym>SQL</acronym> defines some string functions that use
1017 key words, rather than commas, to separate
1018 arguments. Details are in
1019 <xref linkend="functions-string-sql">.
1020 <productname>PostgreSQL</> also provides versions of these functions
1021 that use the regular function invocation syntax
1022 (see <xref linkend="functions-string-other">).
1027 Before <productname>PostgreSQL</productname> 8.3, these functions would
1028 silently accept values of several non-string data types as well, due to
1029 the presence of implicit coercions from those data types to
1030 <type>text</>. Those coercions have been removed because they frequently
1031 caused surprising behaviors. However, the string concatenation operator
1032 (<literal>||</>) still accepts non-string input, so long as at least one
1033 input is of a string type, as shown in <xref
1034 linkend="functions-string-sql">. For other cases, insert an explicit
1035 coercion to <type>text</> if you need to duplicate the previous behavior.
1040 <primary>bit_length</primary>
1043 <primary>char_length</primary>
1046 <primary>lower</primary>
1049 <primary>octet_length</primary>
1052 <primary>overlay</primary>
1055 <primary>position</primary>
1058 <primary>substring</primary>
1061 <primary>trim</primary>
1064 <primary>upper</primary>
1067 <table id="functions-string-sql">
1068 <title><acronym>SQL</acronym> String Functions and Operators</title>
1072 <entry>Function</entry>
1073 <entry>Return Type</entry>
1074 <entry>Description</entry>
1075 <entry>Example</entry>
1076 <entry>Result</entry>
1082 <entry><literal><parameter>string</parameter> <literal>||</literal>
1083 <parameter>string</parameter></literal></entry>
1084 <entry> <type>text</type> </entry>
1086 String concatenation
1088 <primary>character string</primary>
1089 <secondary>concatenation</secondary>
1092 <entry><literal>'Post' || 'greSQL'</literal></entry>
1093 <entry><literal>PostgreSQL</literal></entry>
1098 <literal><parameter>string</parameter> <literal>||</literal>
1099 <parameter>non-string</parameter></literal>
1101 <literal><parameter>non-string</parameter> <literal>||</literal>
1102 <parameter>string</parameter></literal>
1104 <entry> <type>text</type> </entry>
1106 String concatenation with one non-string input
1108 <entry><literal>'Value: ' || 42</literal></entry>
1109 <entry><literal>Value: 42</literal></entry>
1113 <entry><literal><function>bit_length</function>(<parameter>string</parameter>)</literal></entry>
1114 <entry><type>int</type></entry>
1115 <entry>Number of bits in string</entry>
1116 <entry><literal>bit_length('jose')</literal></entry>
1117 <entry><literal>32</literal></entry>
1121 <entry><literal><function>char_length</function>(<parameter>string</parameter>)</literal> or <literal><function>character_length</function>(<parameter>string</parameter>)</literal></entry>
1122 <entry><type>int</type></entry>
1124 Number of characters in string
1126 <primary>character string</primary>
1127 <secondary>length</secondary>
1130 <primary>length</primary>
1131 <secondary sortas="character string">of a character string</secondary>
1132 <see>character string, length</see>
1135 <entry><literal>char_length('jose')</literal></entry>
1136 <entry><literal>4</literal></entry>
1140 <entry><literal><function>lower</function>(<parameter>string</parameter>)</literal></entry>
1141 <entry><type>text</type></entry>
1142 <entry>Convert string to lower case</entry>
1143 <entry><literal>lower('TOM')</literal></entry>
1144 <entry><literal>tom</literal></entry>
1148 <entry><literal><function>octet_length</function>(<parameter>string</parameter>)</literal></entry>
1149 <entry><type>int</type></entry>
1150 <entry>Number of bytes in string</entry>
1151 <entry><literal>octet_length('jose')</literal></entry>
1152 <entry><literal>4</literal></entry>
1156 <entry><literal><function>overlay</function>(<parameter>string</parameter> placing <parameter>string</parameter> from <type>int</type> <optional>for <type>int</type></optional>)</literal></entry>
1157 <entry><type>text</type></entry>
1161 <entry><literal>overlay('Txxxxas' placing 'hom' from 2 for 4)</literal></entry>
1162 <entry><literal>Thomas</literal></entry>
1166 <entry><literal><function>position</function>(<parameter>substring</parameter> in <parameter>string</parameter>)</literal></entry>
1167 <entry><type>int</type></entry>
1168 <entry>Location of specified substring</entry>
1169 <entry><literal>position('om' in 'Thomas')</literal></entry>
1170 <entry><literal>3</literal></entry>
1174 <entry><literal><function>substring</function>(<parameter>string</parameter> <optional>from <type>int</type></optional> <optional>for <type>int</type></optional>)</literal></entry>
1175 <entry><type>text</type></entry>
1179 <entry><literal>substring('Thomas' from 2 for 3)</literal></entry>
1180 <entry><literal>hom</literal></entry>
1184 <entry><literal><function>substring</function>(<parameter>string</parameter> from <replaceable>pattern</replaceable>)</literal></entry>
1185 <entry><type>text</type></entry>
1187 Extract substring matching POSIX regular expression. See
1188 <xref linkend="functions-matching"> for more information on pattern
1191 <entry><literal>substring('Thomas' from '...$')</literal></entry>
1192 <entry><literal>mas</literal></entry>
1196 <entry><literal><function>substring</function>(<parameter>string</parameter> from <replaceable>pattern</replaceable> for <replaceable>escape</replaceable>)</literal></entry>
1197 <entry><type>text</type></entry>
1199 Extract substring matching <acronym>SQL</acronym> regular expression.
1200 See <xref linkend="functions-matching"> for more information on
1203 <entry><literal>substring('Thomas' from '%#"o_a#"_' for '#')</literal></entry>
1204 <entry><literal>oma</literal></entry>
1209 <literal><function>trim</function>(<optional>leading | trailing | both</optional>
1210 <optional><parameter>characters</parameter></optional> from
1211 <parameter>string</parameter>)</literal>
1213 <entry><type>text</type></entry>
1215 Remove the longest string containing only the
1216 <parameter>characters</parameter> (a space by default) from the
1217 start/end/both ends of the <parameter>string</parameter>
1219 <entry><literal>trim(both 'x' from 'xTomxx')</literal></entry>
1220 <entry><literal>Tom</literal></entry>
1224 <entry><literal><function>upper</function>(<parameter>string</parameter>)</literal></entry>
1225 <entry><type>text</type></entry>
1226 <entry>Convert string to uppercase</entry>
1227 <entry><literal>upper('tom')</literal></entry>
1228 <entry><literal>TOM</literal></entry>
1235 Additional string manipulation functions are available and are
1236 listed in <xref linkend="functions-string-other">. Some of them are used internally to implement the
1237 <acronym>SQL</acronym>-standard string functions listed in <xref linkend="functions-string-sql">.
1241 <primary>ascii</primary>
1244 <primary>btrim</primary>
1247 <primary>chr</primary>
1250 <primary>convert</primary>
1253 <primary>convert_from</primary>
1256 <primary>convert_to</primary>
1259 <primary>decode</primary>
1262 <primary>encode</primary>
1265 <primary>initcap</primary>
1268 <primary>lpad</primary>
1271 <primary>ltrim</primary>
1274 <primary>md5</primary>
1277 <primary>pg_client_encoding</primary>
1280 <primary>quote_ident</primary>
1283 <primary>quote_literal</primary>
1286 <primary>quote_nullable</primary>
1289 <primary>repeat</primary>
1292 <primary>replace</primary>
1295 <primary>rpad</primary>
1298 <primary>rtrim</primary>
1301 <primary>split_part</primary>
1304 <primary>strpos</primary>
1307 <primary>substr</primary>
1310 <primary>to_ascii</primary>
1313 <primary>to_hex</primary>
1316 <primary>translate</primary>
1319 <table id="functions-string-other">
1320 <title>Other String Functions</title>
1324 <entry>Function</entry>
1325 <entry>Return Type</entry>
1326 <entry>Description</entry>
1327 <entry>Example</entry>
1328 <entry>Result</entry>
1334 <entry><literal><function>ascii</function>(<parameter>string</parameter>)</literal></entry>
1335 <entry><type>int</type></entry>
1337 <acronym>ASCII</acronym> code of the first character of the
1338 argument. For <acronym>UTF8</acronym> returns the Unicode code
1339 point of the character. For other multibyte encodings, the
1340 argument must be an <acronym>ASCII</acronym> character.
1342 <entry><literal>ascii('x')</literal></entry>
1343 <entry><literal>120</literal></entry>
1347 <entry><literal><function>btrim</function>(<parameter>string</parameter> <type>text</type>
1348 <optional>, <parameter>characters</parameter> <type>text</type></optional>)</literal></entry>
1349 <entry><type>text</type></entry>
1351 Remove the longest string consisting only of characters
1352 in <parameter>characters</parameter> (a space by default)
1353 from the start and end of <parameter>string</parameter>
1355 <entry><literal>btrim('xyxtrimyyx', 'xy')</literal></entry>
1356 <entry><literal>trim</literal></entry>
1360 <entry><literal><function>chr</function>(<type>int</type>)</literal></entry>
1361 <entry><type>text</type></entry>
1363 Character with the given code. For <acronym>UTF8</acronym> the
1364 argument is treated as a Unicode code point. For other multibyte
1365 encodings the argument must designate an
1366 <acronym>ASCII</acronym> character. The NULL (0) character is not
1367 allowed because text data types cannot store such bytes.
1369 <entry><literal>chr(65)</literal></entry>
1370 <entry><literal>A</literal></entry>
1375 <literal><function>convert</function>(<parameter>string</parameter> <type>bytea</type>,
1376 <parameter>src_encoding</parameter> <type>name</type>,
1377 <parameter>dest_encoding</parameter> <type>name</type>)</literal>
1379 <entry><type>bytea</type></entry>
1381 Convert string to <parameter>dest_encoding</parameter>. The
1382 original encoding is specified by
1383 <parameter>src_encoding</parameter>. The
1384 <parameter>string</parameter> must be valid in this encoding.
1385 Conversions can be defined by <command>CREATE CONVERSION</command>.
1386 Also there are some predefined conversions. See <xref
1387 linkend="conversion-names"> for available conversions.
1389 <entry><literal>convert('text_in_utf8', 'UTF8', 'LATIN1')</literal></entry>
1390 <entry><literal>text_in_utf8</literal> represented in Latin-1
1391 encoding (ISO 8859-1)</entry>
1396 <literal><function>convert_from</function>(<parameter>string</parameter> <type>bytea</type>,
1397 <parameter>src_encoding</parameter> <type>name</type>)</literal>
1399 <entry><type>text</type></entry>
1401 Convert string to the database encoding. The original encoding
1402 is specified by <parameter>src_encoding</parameter>. The
1403 <parameter>string</parameter> must be valid in this encoding.
1405 <entry><literal>convert_from('text_in_utf8', 'UTF8')</literal></entry>
1406 <entry><literal>text_in_utf8</literal> represented in the current database encoding</entry>
1411 <literal><function>convert_to</function>(<parameter>string</parameter> <type>text</type>,
1412 <parameter>dest_encoding</parameter> <type>name</type>)</literal>
1414 <entry><type>bytea</type></entry>
1416 Convert string to <parameter>dest_encoding</parameter>.
1418 <entry><literal>convert_to('some text', 'UTF8')</literal></entry>
1419 <entry><literal>some text</literal> represented in the UTF8 encoding</entry>
1424 <literal><function>decode</function>(<parameter>string</parameter> <type>text</type>,
1425 <parameter>type</parameter> <type>text</type>)</literal>
1427 <entry><type>bytea</type></entry>
1429 Decode binary data from <parameter>string</parameter> previously
1430 encoded with <function>encode</>. Parameter type is same as in <function>encode</>.
1432 <entry><literal>decode('MTIzAAE=', 'base64')</literal></entry>
1433 <entry><literal>123\000\001</literal></entry>
1438 <literal><function>encode</function>(<parameter>data</parameter> <type>bytea</type>,
1439 <parameter>type</parameter> <type>text</type>)</literal>
1441 <entry><type>text</type></entry>
1443 Encode binary data to different representation. Supported
1444 types are: <literal>base64</>, <literal>hex</>, <literal>escape</>.
1445 <literal>Escape</> merely outputs null bytes as <literal>\000</> and
1446 doubles backslashes.
1448 <entry><literal>encode(E'123\\000\\001', 'base64')</literal></entry>
1449 <entry><literal>MTIzAAE=</literal></entry>
1453 <entry><literal><function>initcap</function>(<parameter>string</parameter>)</literal></entry>
1454 <entry><type>text</type></entry>
1456 Convert the first letter of each word to uppercase and the
1457 rest to lowercase. Words are sequences of alphanumeric
1458 characters separated by non-alphanumeric characters.
1460 <entry><literal>initcap('hi THOMAS')</literal></entry>
1461 <entry><literal>Hi Thomas</literal></entry>
1465 <entry><literal><function>length</function>(<parameter>string</parameter>)</literal></entry>
1466 <entry><type>int</type></entry>
1468 Number of characters in <parameter>string</parameter>
1470 <entry><literal>length('jose')</literal></entry>
1471 <entry><literal>4</literal></entry>
1475 <entry><literal><function>length</function>(<parameter>string</parameter><type>bytea</type>,
1476 <parameter>encoding</parameter> <type>name</type> )</literal></entry>
1477 <entry><type>int</type></entry>
1479 Number of characters in <parameter>string</parameter> in the given
1480 <parameter>encoding</parameter>. The <parameter>string</parameter>
1481 must be valid in this encoding.
1483 <entry><literal>length('jose', 'UTF8')</literal></entry>
1484 <entry><literal>4</literal></entry>
1489 <literal><function>lpad</function>(<parameter>string</parameter> <type>text</type>,
1490 <parameter>length</parameter> <type>int</type>
1491 <optional>, <parameter>fill</parameter> <type>text</type></optional>)</literal>
1493 <entry><type>text</type></entry>
1495 Fill up the <parameter>string</parameter> to length
1496 <parameter>length</parameter> by prepending the characters
1497 <parameter>fill</parameter> (a space by default). If the
1498 <parameter>string</parameter> is already longer than
1499 <parameter>length</parameter> then it is truncated (on the
1502 <entry><literal>lpad('hi', 5, 'xy')</literal></entry>
1503 <entry><literal>xyxhi</literal></entry>
1507 <entry><literal><function>ltrim</function>(<parameter>string</parameter> <type>text</type>
1508 <optional>, <parameter>characters</parameter> <type>text</type></optional>)</literal>
1510 <entry><type>text</type></entry>
1512 Remove the longest string containing only characters from
1513 <parameter>characters</parameter> (a space by default) from the start of
1514 <parameter>string</parameter>
1516 <entry><literal>ltrim('zzzytrim', 'xyz')</literal></entry>
1517 <entry><literal>trim</literal></entry>
1521 <entry><literal><function>md5</function>(<parameter>string</parameter>)</literal></entry>
1522 <entry><type>text</type></entry>
1524 Calculates the MD5 hash of <parameter>string</parameter>,
1525 returning the result in hexadecimal
1527 <entry><literal>md5('abc')</literal></entry>
1528 <entry><literal>900150983cd24fb0 d6963f7d28e17f72</literal></entry>
1532 <entry><literal><function>pg_client_encoding</function>()</literal></entry>
1533 <entry><type>name</type></entry>
1535 Current client encoding name
1537 <entry><literal>pg_client_encoding()</literal></entry>
1538 <entry><literal>SQL_ASCII</literal></entry>
1542 <entry><literal><function>quote_ident</function>(<parameter>string</parameter> <type>text</type>)</literal></entry>
1543 <entry><type>text</type></entry>
1545 Return the given string suitably quoted to be used as an identifier
1546 in an <acronym>SQL</acronym> statement string.
1547 Quotes are added only if necessary (i.e., if the string contains
1548 non-identifier characters or would be case-folded).
1549 Embedded quotes are properly doubled.
1550 See also <xref linkend="plpgsql-quote-literal-example">.
1552 <entry><literal>quote_ident('Foo bar')</literal></entry>
1553 <entry><literal>"Foo bar"</literal></entry>
1557 <entry><literal><function>quote_literal</function>(<parameter>string</parameter> <type>text</type>)</literal></entry>
1558 <entry><type>text</type></entry>
1560 Return the given string suitably quoted to be used as a string literal
1561 in an <acronym>SQL</acronym> statement string.
1562 Embedded single-quotes and backslashes are properly doubled.
1563 Note that <function>quote_literal</function> returns null on null
1564 input; if the argument might be null,
1565 <function>quote_nullable</function> is often more suitable.
1566 See also <xref linkend="plpgsql-quote-literal-example">.
1568 <entry><literal>quote_literal('O\'Reilly')</literal></entry>
1569 <entry><literal>'O''Reilly'</literal></entry>
1573 <entry><literal><function>quote_literal</function>(<parameter>value</parameter> <type>anyelement</type>)</literal></entry>
1574 <entry><type>text</type></entry>
1576 Coerce the given value to text and then quote it as a literal.
1577 Embedded single-quotes and backslashes are properly doubled.
1579 <entry><literal>quote_literal(42.5)</literal></entry>
1580 <entry><literal>'42.5'</literal></entry>
1584 <entry><literal><function>quote_nullable</function>(<parameter>string</parameter> <type>text</type>)</literal></entry>
1585 <entry><type>text</type></entry>
1587 Return the given string suitably quoted to be used as a string literal
1588 in an <acronym>SQL</acronym> statement string; or, if the argument
1589 is null, return <literal>NULL</>.
1590 Embedded single-quotes and backslashes are properly doubled.
1591 See also <xref linkend="plpgsql-quote-literal-example">.
1593 <entry><literal>quote_nullable(NULL)</literal></entry>
1594 <entry><literal>NULL</literal></entry>
1598 <entry><literal><function>quote_nullable</function>(<parameter>value</parameter> <type>anyelement</type>)</literal></entry>
1599 <entry><type>text</type></entry>
1601 Coerce the given value to text and then quote it as a literal;
1602 or, if the argument is null, return <literal>NULL</>.
1603 Embedded single-quotes and backslashes are properly doubled.
1605 <entry><literal>quote_nullable(42.5)</literal></entry>
1606 <entry><literal>'42.5'</literal></entry>
1610 <entry><literal><function>regexp_matches</function>(<parameter>string</parameter> <type>text</type>, <parameter>pattern</parameter> <type>text</type> [, <parameter>flags</parameter> <type>text</type>])</literal></entry>
1611 <entry><type>setof text[]</type></entry>
1613 Return all captured substrings resulting from matching a POSIX regular
1614 expression against the <parameter>string</parameter>. See
1615 <xref linkend="functions-posix-regexp"> for more information.
1617 <entry><literal>regexp_matches('foobarbequebaz', '(bar)(beque)')</literal></entry>
1618 <entry><literal>{bar,beque}</literal></entry>
1622 <entry><literal><function>regexp_replace</function>(<parameter>string</parameter> <type>text</type>, <parameter>pattern</parameter> <type>text</type>, <parameter>replacement</parameter> <type>text</type> [, <parameter>flags</parameter> <type>text</type>])</literal></entry>
1623 <entry><type>text</type></entry>
1625 Replace substring(s) matching a POSIX regular expression. See
1626 <xref linkend="functions-posix-regexp"> for more information.
1628 <entry><literal>regexp_replace('Thomas', '.[mN]a.', 'M')</literal></entry>
1629 <entry><literal>ThM</literal></entry>
1633 <entry><literal><function>regexp_split_to_array</function>(<parameter>string</parameter> <type>text</type>, <parameter>pattern</parameter> <type>text</type> [, <parameter>flags</parameter> <type>text</type> ])</literal></entry>
1634 <entry><type>text[]</type></entry>
1636 Split <parameter>string</parameter> using a POSIX regular expression as
1637 the delimiter. See <xref linkend="functions-posix-regexp"> for more
1640 <entry><literal>regexp_split_to_array('hello world', E'\\s+')</literal></entry>
1641 <entry><literal>{hello,world}</literal></entry>
1645 <entry><literal><function>regexp_split_to_table</function>(<parameter>string</parameter> <type>text</type>, <parameter>pattern</parameter> <type>text</type> [, <parameter>flags</parameter> <type>text</type>])</literal></entry>
1646 <entry><type>setof text</type></entry>
1648 Split <parameter>string</parameter> using a POSIX regular expression as
1649 the delimiter. See <xref linkend="functions-posix-regexp"> for more
1652 <entry><literal>regexp_split_to_table('hello world', E'\\s+')</literal></entry>
1653 <entry><literal>hello</literal><para><literal>world</literal></para> (2 rows)</entry>
1657 <entry><literal><function>repeat</function>(<parameter>string</parameter> <type>text</type>, <parameter>number</parameter> <type>int</type>)</literal></entry>
1658 <entry><type>text</type></entry>
1659 <entry>Repeat <parameter>string</parameter> the specified
1660 <parameter>number</parameter> of times</entry>
1661 <entry><literal>repeat('Pg', 4)</literal></entry>
1662 <entry><literal>PgPgPgPg</literal></entry>
1666 <entry><literal><function>replace</function>(<parameter>string</parameter> <type>text</type>,
1667 <parameter>from</parameter> <type>text</type>,
1668 <parameter>to</parameter> <type>text</type>)</literal></entry>
1669 <entry><type>text</type></entry>
1670 <entry>Replace all occurrences in <parameter>string</parameter> of substring
1671 <parameter>from</parameter> with substring <parameter>to</parameter>
1673 <entry><literal>replace('abcdefabcdef', 'cd', 'XX')</literal></entry>
1674 <entry><literal>abXXefabXXef</literal></entry>
1679 <literal><function>rpad</function>(<parameter>string</parameter> <type>text</type>,
1680 <parameter>length</parameter> <type>int</type>
1681 <optional>, <parameter>fill</parameter> <type>text</type></optional>)</literal>
1683 <entry><type>text</type></entry>
1685 Fill up the <parameter>string</parameter> to length
1686 <parameter>length</parameter> by appending the characters
1687 <parameter>fill</parameter> (a space by default). If the
1688 <parameter>string</parameter> is already longer than
1689 <parameter>length</parameter> then it is truncated.
1691 <entry><literal>rpad('hi', 5, 'xy')</literal></entry>
1692 <entry><literal>hixyx</literal></entry>
1696 <entry><literal><function>rtrim</function>(<parameter>string</parameter> <type>text</type>
1697 <optional>, <parameter>characters</parameter> <type>text</type></optional>)</literal>
1699 <entry><type>text</type></entry>
1701 Remove the longest string containing only characters from
1702 <parameter>characters</parameter> (a space by default) from the end of
1703 <parameter>string</parameter>
1705 <entry><literal>rtrim('trimxxxx', 'x')</literal></entry>
1706 <entry><literal>trim</literal></entry>
1710 <entry><literal><function>split_part</function>(<parameter>string</parameter> <type>text</type>,
1711 <parameter>delimiter</parameter> <type>text</type>,
1712 <parameter>field</parameter> <type>int</type>)</literal></entry>
1713 <entry><type>text</type></entry>
1714 <entry>Split <parameter>string</parameter> on <parameter>delimiter</parameter>
1715 and return the given field (counting from one)
1717 <entry><literal>split_part('abc~@~def~@~ghi', '~@~', 2)</literal></entry>
1718 <entry><literal>def</literal></entry>
1722 <entry><literal><function>strpos</function>(<parameter>string</parameter>, <parameter>substring</parameter>)</literal></entry>
1723 <entry><type>int</type></entry>
1725 Location of specified substring (same as
1726 <literal>position(<parameter>substring</parameter> in
1727 <parameter>string</parameter>)</literal>, but note the reversed
1730 <entry><literal>strpos('high', 'ig')</literal></entry>
1731 <entry><literal>2</literal></entry>
1735 <entry><literal><function>substr</function>(<parameter>string</parameter>, <parameter>from</parameter> <optional>, <parameter>count</parameter></optional>)</literal></entry>
1736 <entry><type>text</type></entry>
1738 Extract substring (same as
1739 <literal>substring(<parameter>string</parameter> from <parameter>from</parameter> for <parameter>count</parameter>)</literal>)
1741 <entry><literal>substr('alphabet', 3, 2)</literal></entry>
1742 <entry><literal>ph</literal></entry>
1746 <entry><literal><function>to_ascii</function>(<parameter>string</parameter> <type>text</type>
1747 <optional>, <parameter>encoding</parameter> <type>text</type></optional>)</literal></entry>
1748 <entry><type>text</type></entry>
1751 Convert <parameter>string</parameter> to <acronym>ASCII</acronym> from another encoding
1752 (only supports conversion from <literal>LATIN1</>, <literal>LATIN2</>, <literal>LATIN9</>,
1753 and <literal>WIN1250</> encodings)
1756 <entry><literal>to_ascii('Karel')</literal></entry>
1757 <entry><literal>Karel</literal></entry>
1761 <entry><literal><function>to_hex</function>(<parameter>number</parameter> <type>int</type>
1762 or <type>bigint</type>)</literal></entry>
1763 <entry><type>text</type></entry>
1764 <entry>Convert <parameter>number</parameter> to its equivalent hexadecimal
1767 <entry><literal>to_hex(2147483647)</literal></entry>
1768 <entry><literal>7fffffff</literal></entry>
1773 <literal><function>translate</function>(<parameter>string</parameter> <type>text</type>,
1774 <parameter>from</parameter> <type>text</type>,
1775 <parameter>to</parameter> <type>text</type>)</literal>
1777 <entry><type>text</type></entry>
1779 Any character in <parameter>string</parameter> that matches a
1780 character in the <parameter>from</parameter> set is replaced by
1781 the corresponding character in the <parameter>to</parameter>
1784 <entry><literal>translate('12345', '14', 'ax')</literal></entry>
1785 <entry><literal>a23x5</literal></entry>
1793 <table id="conversion-names">
1794 <title>Built-in Conversions</title>
1798 <entry>Conversion Name
1801 The conversion names follow a standard naming scheme: The
1802 official name of the source encoding with all
1803 non-alphanumeric characters replaced by underscores, followed
1804 by <literal>_to_</literal>, followed by the similarly processed
1805 destination encoding name. Therefore, the names might deviate
1806 from the customary encoding names.
1810 <entry>Source Encoding</entry>
1811 <entry>Destination Encoding</entry>
1817 <entry><literal>ascii_to_mic</literal></entry>
1818 <entry><literal>SQL_ASCII</literal></entry>
1819 <entry><literal>MULE_INTERNAL</literal></entry>
1823 <entry><literal>ascii_to_utf8</literal></entry>
1824 <entry><literal>SQL_ASCII</literal></entry>
1825 <entry><literal>UTF8</literal></entry>
1829 <entry><literal>big5_to_euc_tw</literal></entry>
1830 <entry><literal>BIG5</literal></entry>
1831 <entry><literal>EUC_TW</literal></entry>
1835 <entry><literal>big5_to_mic</literal></entry>
1836 <entry><literal>BIG5</literal></entry>
1837 <entry><literal>MULE_INTERNAL</literal></entry>
1841 <entry><literal>big5_to_utf8</literal></entry>
1842 <entry><literal>BIG5</literal></entry>
1843 <entry><literal>UTF8</literal></entry>
1847 <entry><literal>euc_cn_to_mic</literal></entry>
1848 <entry><literal>EUC_CN</literal></entry>
1849 <entry><literal>MULE_INTERNAL</literal></entry>
1853 <entry><literal>euc_cn_to_utf8</literal></entry>
1854 <entry><literal>EUC_CN</literal></entry>
1855 <entry><literal>UTF8</literal></entry>
1859 <entry><literal>euc_jp_to_mic</literal></entry>
1860 <entry><literal>EUC_JP</literal></entry>
1861 <entry><literal>MULE_INTERNAL</literal></entry>
1865 <entry><literal>euc_jp_to_sjis</literal></entry>
1866 <entry><literal>EUC_JP</literal></entry>
1867 <entry><literal>SJIS</literal></entry>
1871 <entry><literal>euc_jp_to_utf8</literal></entry>
1872 <entry><literal>EUC_JP</literal></entry>
1873 <entry><literal>UTF8</literal></entry>
1877 <entry><literal>euc_kr_to_mic</literal></entry>
1878 <entry><literal>EUC_KR</literal></entry>
1879 <entry><literal>MULE_INTERNAL</literal></entry>
1883 <entry><literal>euc_kr_to_utf8</literal></entry>
1884 <entry><literal>EUC_KR</literal></entry>
1885 <entry><literal>UTF8</literal></entry>
1889 <entry><literal>euc_tw_to_big5</literal></entry>
1890 <entry><literal>EUC_TW</literal></entry>
1891 <entry><literal>BIG5</literal></entry>
1895 <entry><literal>euc_tw_to_mic</literal></entry>
1896 <entry><literal>EUC_TW</literal></entry>
1897 <entry><literal>MULE_INTERNAL</literal></entry>
1901 <entry><literal>euc_tw_to_utf8</literal></entry>
1902 <entry><literal>EUC_TW</literal></entry>
1903 <entry><literal>UTF8</literal></entry>
1907 <entry><literal>gb18030_to_utf8</literal></entry>
1908 <entry><literal>GB18030</literal></entry>
1909 <entry><literal>UTF8</literal></entry>
1913 <entry><literal>gbk_to_utf8</literal></entry>
1914 <entry><literal>GBK</literal></entry>
1915 <entry><literal>UTF8</literal></entry>
1919 <entry><literal>iso_8859_10_to_utf8</literal></entry>
1920 <entry><literal>LATIN6</literal></entry>
1921 <entry><literal>UTF8</literal></entry>
1925 <entry><literal>iso_8859_13_to_utf8</literal></entry>
1926 <entry><literal>LATIN7</literal></entry>
1927 <entry><literal>UTF8</literal></entry>
1931 <entry><literal>iso_8859_14_to_utf8</literal></entry>
1932 <entry><literal>LATIN8</literal></entry>
1933 <entry><literal>UTF8</literal></entry>
1937 <entry><literal>iso_8859_15_to_utf8</literal></entry>
1938 <entry><literal>LATIN9</literal></entry>
1939 <entry><literal>UTF8</literal></entry>
1943 <entry><literal>iso_8859_16_to_utf8</literal></entry>
1944 <entry><literal>LATIN10</literal></entry>
1945 <entry><literal>UTF8</literal></entry>
1949 <entry><literal>iso_8859_1_to_mic</literal></entry>
1950 <entry><literal>LATIN1</literal></entry>
1951 <entry><literal>MULE_INTERNAL</literal></entry>
1955 <entry><literal>iso_8859_1_to_utf8</literal></entry>
1956 <entry><literal>LATIN1</literal></entry>
1957 <entry><literal>UTF8</literal></entry>
1961 <entry><literal>iso_8859_2_to_mic</literal></entry>
1962 <entry><literal>LATIN2</literal></entry>
1963 <entry><literal>MULE_INTERNAL</literal></entry>
1967 <entry><literal>iso_8859_2_to_utf8</literal></entry>
1968 <entry><literal>LATIN2</literal></entry>
1969 <entry><literal>UTF8</literal></entry>
1973 <entry><literal>iso_8859_2_to_windows_1250</literal></entry>
1974 <entry><literal>LATIN2</literal></entry>
1975 <entry><literal>WIN1250</literal></entry>
1979 <entry><literal>iso_8859_3_to_mic</literal></entry>
1980 <entry><literal>LATIN3</literal></entry>
1981 <entry><literal>MULE_INTERNAL</literal></entry>
1985 <entry><literal>iso_8859_3_to_utf8</literal></entry>
1986 <entry><literal>LATIN3</literal></entry>
1987 <entry><literal>UTF8</literal></entry>
1991 <entry><literal>iso_8859_4_to_mic</literal></entry>
1992 <entry><literal>LATIN4</literal></entry>
1993 <entry><literal>MULE_INTERNAL</literal></entry>
1997 <entry><literal>iso_8859_4_to_utf8</literal></entry>
1998 <entry><literal>LATIN4</literal></entry>
1999 <entry><literal>UTF8</literal></entry>
2003 <entry><literal>iso_8859_5_to_koi8_r</literal></entry>
2004 <entry><literal>ISO_8859_5</literal></entry>
2005 <entry><literal>KOI8R</literal></entry>
2009 <entry><literal>iso_8859_5_to_mic</literal></entry>
2010 <entry><literal>ISO_8859_5</literal></entry>
2011 <entry><literal>MULE_INTERNAL</literal></entry>
2015 <entry><literal>iso_8859_5_to_utf8</literal></entry>
2016 <entry><literal>ISO_8859_5</literal></entry>
2017 <entry><literal>UTF8</literal></entry>
2021 <entry><literal>iso_8859_5_to_windows_1251</literal></entry>
2022 <entry><literal>ISO_8859_5</literal></entry>
2023 <entry><literal>WIN1251</literal></entry>
2027 <entry><literal>iso_8859_5_to_windows_866</literal></entry>
2028 <entry><literal>ISO_8859_5</literal></entry>
2029 <entry><literal>WIN866</literal></entry>
2033 <entry><literal>iso_8859_6_to_utf8</literal></entry>
2034 <entry><literal>ISO_8859_6</literal></entry>
2035 <entry><literal>UTF8</literal></entry>
2039 <entry><literal>iso_8859_7_to_utf8</literal></entry>
2040 <entry><literal>ISO_8859_7</literal></entry>
2041 <entry><literal>UTF8</literal></entry>
2045 <entry><literal>iso_8859_8_to_utf8</literal></entry>
2046 <entry><literal>ISO_8859_8</literal></entry>
2047 <entry><literal>UTF8</literal></entry>
2051 <entry><literal>iso_8859_9_to_utf8</literal></entry>
2052 <entry><literal>LATIN5</literal></entry>
2053 <entry><literal>UTF8</literal></entry>
2057 <entry><literal>johab_to_utf8</literal></entry>
2058 <entry><literal>JOHAB</literal></entry>
2059 <entry><literal>UTF8</literal></entry>
2063 <entry><literal>koi8_r_to_iso_8859_5</literal></entry>
2064 <entry><literal>KOI8R</literal></entry>
2065 <entry><literal>ISO_8859_5</literal></entry>
2069 <entry><literal>koi8_r_to_mic</literal></entry>
2070 <entry><literal>KOI8R</literal></entry>
2071 <entry><literal>MULE_INTERNAL</literal></entry>
2075 <entry><literal>koi8_r_to_utf8</literal></entry>
2076 <entry><literal>KOI8R</literal></entry>
2077 <entry><literal>UTF8</literal></entry>
2081 <entry><literal>koi8_r_to_windows_1251</literal></entry>
2082 <entry><literal>KOI8R</literal></entry>
2083 <entry><literal>WIN1251</literal></entry>
2087 <entry><literal>koi8_r_to_windows_866</literal></entry>
2088 <entry><literal>KOI8R</literal></entry>
2089 <entry><literal>WIN866</literal></entry>
2093 <entry><literal>koi8_u_to_utf8</literal></entry>
2094 <entry><literal>KOI8U</literal></entry>
2095 <entry><literal>UTF8</literal></entry>
2099 <entry><literal>mic_to_ascii</literal></entry>
2100 <entry><literal>MULE_INTERNAL</literal></entry>
2101 <entry><literal>SQL_ASCII</literal></entry>
2105 <entry><literal>mic_to_big5</literal></entry>
2106 <entry><literal>MULE_INTERNAL</literal></entry>
2107 <entry><literal>BIG5</literal></entry>
2111 <entry><literal>mic_to_euc_cn</literal></entry>
2112 <entry><literal>MULE_INTERNAL</literal></entry>
2113 <entry><literal>EUC_CN</literal></entry>
2117 <entry><literal>mic_to_euc_jp</literal></entry>
2118 <entry><literal>MULE_INTERNAL</literal></entry>
2119 <entry><literal>EUC_JP</literal></entry>
2123 <entry><literal>mic_to_euc_kr</literal></entry>
2124 <entry><literal>MULE_INTERNAL</literal></entry>
2125 <entry><literal>EUC_KR</literal></entry>
2129 <entry><literal>mic_to_euc_tw</literal></entry>
2130 <entry><literal>MULE_INTERNAL</literal></entry>
2131 <entry><literal>EUC_TW</literal></entry>
2135 <entry><literal>mic_to_iso_8859_1</literal></entry>
2136 <entry><literal>MULE_INTERNAL</literal></entry>
2137 <entry><literal>LATIN1</literal></entry>
2141 <entry><literal>mic_to_iso_8859_2</literal></entry>
2142 <entry><literal>MULE_INTERNAL</literal></entry>
2143 <entry><literal>LATIN2</literal></entry>
2147 <entry><literal>mic_to_iso_8859_3</literal></entry>
2148 <entry><literal>MULE_INTERNAL</literal></entry>
2149 <entry><literal>LATIN3</literal></entry>
2153 <entry><literal>mic_to_iso_8859_4</literal></entry>
2154 <entry><literal>MULE_INTERNAL</literal></entry>
2155 <entry><literal>LATIN4</literal></entry>
2159 <entry><literal>mic_to_iso_8859_5</literal></entry>
2160 <entry><literal>MULE_INTERNAL</literal></entry>
2161 <entry><literal>ISO_8859_5</literal></entry>
2165 <entry><literal>mic_to_koi8_r</literal></entry>
2166 <entry><literal>MULE_INTERNAL</literal></entry>
2167 <entry><literal>KOI8R</literal></entry>
2171 <entry><literal>mic_to_sjis</literal></entry>
2172 <entry><literal>MULE_INTERNAL</literal></entry>
2173 <entry><literal>SJIS</literal></entry>
2177 <entry><literal>mic_to_windows_1250</literal></entry>
2178 <entry><literal>MULE_INTERNAL</literal></entry>
2179 <entry><literal>WIN1250</literal></entry>
2183 <entry><literal>mic_to_windows_1251</literal></entry>
2184 <entry><literal>MULE_INTERNAL</literal></entry>
2185 <entry><literal>WIN1251</literal></entry>
2189 <entry><literal>mic_to_windows_866</literal></entry>
2190 <entry><literal>MULE_INTERNAL</literal></entry>
2191 <entry><literal>WIN866</literal></entry>
2195 <entry><literal>sjis_to_euc_jp</literal></entry>
2196 <entry><literal>SJIS</literal></entry>
2197 <entry><literal>EUC_JP</literal></entry>
2201 <entry><literal>sjis_to_mic</literal></entry>
2202 <entry><literal>SJIS</literal></entry>
2203 <entry><literal>MULE_INTERNAL</literal></entry>
2207 <entry><literal>sjis_to_utf8</literal></entry>
2208 <entry><literal>SJIS</literal></entry>
2209 <entry><literal>UTF8</literal></entry>
2213 <entry><literal>tcvn_to_utf8</literal></entry>
2214 <entry><literal>WIN1258</literal></entry>
2215 <entry><literal>UTF8</literal></entry>
2219 <entry><literal>uhc_to_utf8</literal></entry>
2220 <entry><literal>UHC</literal></entry>
2221 <entry><literal>UTF8</literal></entry>
2225 <entry><literal>utf8_to_ascii</literal></entry>
2226 <entry><literal>UTF8</literal></entry>
2227 <entry><literal>SQL_ASCII</literal></entry>
2231 <entry><literal>utf8_to_big5</literal></entry>
2232 <entry><literal>UTF8</literal></entry>
2233 <entry><literal>BIG5</literal></entry>
2237 <entry><literal>utf8_to_euc_cn</literal></entry>
2238 <entry><literal>UTF8</literal></entry>
2239 <entry><literal>EUC_CN</literal></entry>
2243 <entry><literal>utf8_to_euc_jp</literal></entry>
2244 <entry><literal>UTF8</literal></entry>
2245 <entry><literal>EUC_JP</literal></entry>
2249 <entry><literal>utf8_to_euc_kr</literal></entry>
2250 <entry><literal>UTF8</literal></entry>
2251 <entry><literal>EUC_KR</literal></entry>
2255 <entry><literal>utf8_to_euc_tw</literal></entry>
2256 <entry><literal>UTF8</literal></entry>
2257 <entry><literal>EUC_TW</literal></entry>
2261 <entry><literal>utf8_to_gb18030</literal></entry>
2262 <entry><literal>UTF8</literal></entry>
2263 <entry><literal>GB18030</literal></entry>
2267 <entry><literal>utf8_to_gbk</literal></entry>
2268 <entry><literal>UTF8</literal></entry>
2269 <entry><literal>GBK</literal></entry>
2273 <entry><literal>utf8_to_iso_8859_1</literal></entry>
2274 <entry><literal>UTF8</literal></entry>
2275 <entry><literal>LATIN1</literal></entry>
2279 <entry><literal>utf8_to_iso_8859_10</literal></entry>
2280 <entry><literal>UTF8</literal></entry>
2281 <entry><literal>LATIN6</literal></entry>
2285 <entry><literal>utf8_to_iso_8859_13</literal></entry>
2286 <entry><literal>UTF8</literal></entry>
2287 <entry><literal>LATIN7</literal></entry>
2291 <entry><literal>utf8_to_iso_8859_14</literal></entry>
2292 <entry><literal>UTF8</literal></entry>
2293 <entry><literal>LATIN8</literal></entry>
2297 <entry><literal>utf8_to_iso_8859_15</literal></entry>
2298 <entry><literal>UTF8</literal></entry>
2299 <entry><literal>LATIN9</literal></entry>
2303 <entry><literal>utf8_to_iso_8859_16</literal></entry>
2304 <entry><literal>UTF8</literal></entry>
2305 <entry><literal>LATIN10</literal></entry>
2309 <entry><literal>utf8_to_iso_8859_2</literal></entry>
2310 <entry><literal>UTF8</literal></entry>
2311 <entry><literal>LATIN2</literal></entry>
2315 <entry><literal>utf8_to_iso_8859_3</literal></entry>
2316 <entry><literal>UTF8</literal></entry>
2317 <entry><literal>LATIN3</literal></entry>
2321 <entry><literal>utf8_to_iso_8859_4</literal></entry>
2322 <entry><literal>UTF8</literal></entry>
2323 <entry><literal>LATIN4</literal></entry>
2327 <entry><literal>utf8_to_iso_8859_5</literal></entry>
2328 <entry><literal>UTF8</literal></entry>
2329 <entry><literal>ISO_8859_5</literal></entry>
2333 <entry><literal>utf8_to_iso_8859_6</literal></entry>
2334 <entry><literal>UTF8</literal></entry>
2335 <entry><literal>ISO_8859_6</literal></entry>
2339 <entry><literal>utf8_to_iso_8859_7</literal></entry>
2340 <entry><literal>UTF8</literal></entry>
2341 <entry><literal>ISO_8859_7</literal></entry>
2345 <entry><literal>utf8_to_iso_8859_8</literal></entry>
2346 <entry><literal>UTF8</literal></entry>
2347 <entry><literal>ISO_8859_8</literal></entry>
2351 <entry><literal>utf8_to_iso_8859_9</literal></entry>
2352 <entry><literal>UTF8</literal></entry>
2353 <entry><literal>LATIN5</literal></entry>
2357 <entry><literal>utf8_to_johab</literal></entry>
2358 <entry><literal>UTF8</literal></entry>
2359 <entry><literal>JOHAB</literal></entry>
2363 <entry><literal>utf8_to_koi8_r</literal></entry>
2364 <entry><literal>UTF8</literal></entry>
2365 <entry><literal>KOI8R</literal></entry>
2369 <entry><literal>utf8_to_koi8_u</literal></entry>
2370 <entry><literal>UTF8</literal></entry>
2371 <entry><literal>KOI8U</literal></entry>
2375 <entry><literal>utf8_to_sjis</literal></entry>
2376 <entry><literal>UTF8</literal></entry>
2377 <entry><literal>SJIS</literal></entry>
2381 <entry><literal>utf8_to_tcvn</literal></entry>
2382 <entry><literal>UTF8</literal></entry>
2383 <entry><literal>WIN1258</literal></entry>
2387 <entry><literal>utf8_to_uhc</literal></entry>
2388 <entry><literal>UTF8</literal></entry>
2389 <entry><literal>UHC</literal></entry>
2393 <entry><literal>utf8_to_windows_1250</literal></entry>
2394 <entry><literal>UTF8</literal></entry>
2395 <entry><literal>WIN1250</literal></entry>
2399 <entry><literal>utf8_to_windows_1251</literal></entry>
2400 <entry><literal>UTF8</literal></entry>
2401 <entry><literal>WIN1251</literal></entry>
2405 <entry><literal>utf8_to_windows_1252</literal></entry>
2406 <entry><literal>UTF8</literal></entry>
2407 <entry><literal>WIN1252</literal></entry>
2411 <entry><literal>utf8_to_windows_1253</literal></entry>
2412 <entry><literal>UTF8</literal></entry>
2413 <entry><literal>WIN1253</literal></entry>
2417 <entry><literal>utf8_to_windows_1254</literal></entry>
2418 <entry><literal>UTF8</literal></entry>
2419 <entry><literal>WIN1254</literal></entry>
2423 <entry><literal>utf8_to_windows_1255</literal></entry>
2424 <entry><literal>UTF8</literal></entry>
2425 <entry><literal>WIN1255</literal></entry>
2429 <entry><literal>utf8_to_windows_1256</literal></entry>
2430 <entry><literal>UTF8</literal></entry>
2431 <entry><literal>WIN1256</literal></entry>
2435 <entry><literal>utf8_to_windows_1257</literal></entry>
2436 <entry><literal>UTF8</literal></entry>
2437 <entry><literal>WIN1257</literal></entry>
2441 <entry><literal>utf8_to_windows_866</literal></entry>
2442 <entry><literal>UTF8</literal></entry>
2443 <entry><literal>WIN866</literal></entry>
2447 <entry><literal>utf8_to_windows_874</literal></entry>
2448 <entry><literal>UTF8</literal></entry>
2449 <entry><literal>WIN874</literal></entry>
2453 <entry><literal>windows_1250_to_iso_8859_2</literal></entry>
2454 <entry><literal>WIN1250</literal></entry>
2455 <entry><literal>LATIN2</literal></entry>
2459 <entry><literal>windows_1250_to_mic</literal></entry>
2460 <entry><literal>WIN1250</literal></entry>
2461 <entry><literal>MULE_INTERNAL</literal></entry>
2465 <entry><literal>windows_1250_to_utf8</literal></entry>
2466 <entry><literal>WIN1250</literal></entry>
2467 <entry><literal>UTF8</literal></entry>
2471 <entry><literal>windows_1251_to_iso_8859_5</literal></entry>
2472 <entry><literal>WIN1251</literal></entry>
2473 <entry><literal>ISO_8859_5</literal></entry>
2477 <entry><literal>windows_1251_to_koi8_r</literal></entry>
2478 <entry><literal>WIN1251</literal></entry>
2479 <entry><literal>KOI8R</literal></entry>
2483 <entry><literal>windows_1251_to_mic</literal></entry>
2484 <entry><literal>WIN1251</literal></entry>
2485 <entry><literal>MULE_INTERNAL</literal></entry>
2489 <entry><literal>windows_1251_to_utf8</literal></entry>
2490 <entry><literal>WIN1251</literal></entry>
2491 <entry><literal>UTF8</literal></entry>
2495 <entry><literal>windows_1251_to_windows_866</literal></entry>
2496 <entry><literal>WIN1251</literal></entry>
2497 <entry><literal>WIN866</literal></entry>
2501 <entry><literal>windows_1252_to_utf8</literal></entry>
2502 <entry><literal>WIN1252</literal></entry>
2503 <entry><literal>UTF8</literal></entry>
2507 <entry><literal>windows_1256_to_utf8</literal></entry>
2508 <entry><literal>WIN1256</literal></entry>
2509 <entry><literal>UTF8</literal></entry>
2513 <entry><literal>windows_866_to_iso_8859_5</literal></entry>
2514 <entry><literal>WIN866</literal></entry>
2515 <entry><literal>ISO_8859_5</literal></entry>
2519 <entry><literal>windows_866_to_koi8_r</literal></entry>
2520 <entry><literal>WIN866</literal></entry>
2521 <entry><literal>KOI8R</literal></entry>
2525 <entry><literal>windows_866_to_mic</literal></entry>
2526 <entry><literal>WIN866</literal></entry>
2527 <entry><literal>MULE_INTERNAL</literal></entry>
2531 <entry><literal>windows_866_to_utf8</literal></entry>
2532 <entry><literal>WIN866</literal></entry>
2533 <entry><literal>UTF8</literal></entry>
2537 <entry><literal>windows_866_to_windows_1251</literal></entry>
2538 <entry><literal>WIN866</literal></entry>
2539 <entry><literal>WIN</literal></entry>
2543 <entry><literal>windows_874_to_utf8</literal></entry>
2544 <entry><literal>WIN874</literal></entry>
2545 <entry><literal>UTF8</literal></entry>
2549 <entry><literal>euc_jis_2004_to_utf8</literal></entry>
2550 <entry><literal>EUC_JIS_2004</literal></entry>
2551 <entry><literal>UTF8</literal></entry>
2555 <entry><literal>ut8_to_euc_jis_2004</literal></entry>
2556 <entry><literal>UTF8</literal></entry>
2557 <entry><literal>EUC_JIS_2004</literal></entry>
2561 <entry><literal>shift_jis_2004_to_utf8</literal></entry>
2562 <entry><literal>SHIFT_JIS_2004</literal></entry>
2563 <entry><literal>UTF8</literal></entry>
2567 <entry><literal>ut8_to_shift_jis_2004</literal></entry>
2568 <entry><literal>UTF8</literal></entry>
2569 <entry><literal>SHIFT_JIS_2004</literal></entry>
2573 <entry><literal>euc_jis_2004_to_shift_jis_2004</literal></entry>
2574 <entry><literal>EUC_JIS_2004</literal></entry>
2575 <entry><literal>SHIFT_JIS_2004</literal></entry>
2579 <entry><literal>shift_jis_2004_to_euc_jis_2004</literal></entry>
2580 <entry><literal>SHIFT_JIS_2004</literal></entry>
2581 <entry><literal>EUC_JIS_2004</literal></entry>
2591 <sect1 id="functions-binarystring">
2592 <title>Binary String Functions and Operators</title>
2594 <indexterm zone="functions-binarystring">
2595 <primary>binary data</primary>
2596 <secondary>functions</secondary>
2600 This section describes functions and operators for examining and
2601 manipulating values of type <type>bytea</type>.
2605 <acronym>SQL</acronym> defines some string functions that use
2606 key words, rather than commas, to separate
2607 arguments. Details are in
2608 <xref linkend="functions-binarystring-sql">.
2609 <productname>PostgreSQL</> also provides versions of these functions
2610 that use the regular function invocation syntax
2611 (see <xref linkend="functions-binarystring-other">).
2614 <table id="functions-binarystring-sql">
2615 <title><acronym>SQL</acronym> Binary String Functions and Operators</title>
2619 <entry>Function</entry>
2620 <entry>Return Type</entry>
2621 <entry>Description</entry>
2622 <entry>Example</entry>
2623 <entry>Result</entry>
2629 <entry><literal><parameter>string</parameter> <literal>||</literal>
2630 <parameter>string</parameter></literal></entry>
2631 <entry> <type>bytea</type> </entry>
2633 String concatenation
2635 <primary>binary string</primary>
2636 <secondary>concatenation</secondary>
2639 <entry><literal>E'\\\\Post'::bytea || E'\\047gres\\000'::bytea</literal></entry>
2640 <entry><literal>\\Post'gres\000</literal></entry>
2644 <entry><function>get_bit</function>(<parameter>string</parameter>, <parameter>offset</parameter>)</entry>
2645 <entry><type>int</type></entry>
2647 Extract bit from string
2649 <primary>get_bit</primary>
2652 <entry><literal>get_bit(E'Th\\000omas'::bytea, 45)</literal></entry>
2653 <entry><literal>1</literal></entry>
2657 <entry><function>get_byte</function>(<parameter>string</parameter>, <parameter>offset</parameter>)</entry>
2658 <entry><type>int</type></entry>
2660 Extract byte from string
2662 <primary>get_byte</primary>
2665 <entry><literal>get_byte(E'Th\\000omas'::bytea, 4)</literal></entry>
2666 <entry><literal>109</literal></entry>
2670 <entry><literal><function>octet_length</function>(<parameter>string</parameter>)</literal></entry>
2671 <entry><type>int</type></entry>
2672 <entry>Number of bytes in binary string</entry>
2673 <entry><literal>octet_length(E'jo\\000se'::bytea)</literal></entry>
2674 <entry><literal>5</literal></entry>
2678 <entry><literal><function>position</function>(<parameter>substring</parameter> in <parameter>string</parameter>)</literal></entry>
2679 <entry><type>int</type></entry>
2680 <entry>Location of specified substring</entry>
2681 <entry><literal>position(E'\\000om'::bytea in E'Th\\000omas'::bytea)</literal></entry>
2682 <entry><literal>3</literal></entry>
2686 <entry><function>set_bit</function>(<parameter>string</parameter>,
2687 <parameter>offset</parameter>, <parameter>newvalue</>)</entry>
2688 <entry><type>bytea</type></entry>
2692 <primary>set_bit</primary>
2695 <entry><literal>set_bit(E'Th\\000omas'::bytea, 45, 0)</literal></entry>
2696 <entry><literal>Th\000omAs</literal></entry>
2700 <entry><function>set_byte</function>(<parameter>string</parameter>,
2701 <parameter>offset</parameter>, <parameter>newvalue</>)</entry>
2702 <entry><type>bytea</type></entry>
2706 <primary>set_byte</primary>
2709 <entry><literal>set_byte(E'Th\\000omas'::bytea, 4, 64)</literal></entry>
2710 <entry><literal>Th\000o@as</literal></entry>
2714 <entry><literal><function>substring</function>(<parameter>string</parameter> <optional>from <type>int</type></optional> <optional>for <type>int</type></optional>)</literal></entry>
2715 <entry><type>bytea</type></entry>
2719 <primary>substring</primary>
2722 <entry><literal>substring(E'Th\\000omas'::bytea from 2 for 3)</literal></entry>
2723 <entry><literal>h\000o</literal></entry>
2728 <literal><function>trim</function>(<optional>both</optional>
2729 <parameter>bytes</parameter> from
2730 <parameter>string</parameter>)</literal>
2732 <entry><type>bytea</type></entry>
2734 Remove the longest string containing only the bytes in
2735 <parameter>bytes</parameter> from the start
2736 and end of <parameter>string</parameter>
2738 <entry><literal>trim(E'\\000'::bytea from E'\\000Tom\\000'::bytea)</literal></entry>
2739 <entry><literal>Tom</literal></entry>
2746 Additional binary string manipulation functions are available and
2747 are listed in <xref linkend="functions-binarystring-other">. Some
2748 of them are used internally to implement the
2749 <acronym>SQL</acronym>-standard string functions listed in <xref
2750 linkend="functions-binarystring-sql">.
2753 <table id="functions-binarystring-other">
2754 <title>Other Binary String Functions</title>
2758 <entry>Function</entry>
2759 <entry>Return Type</entry>
2760 <entry>Description</entry>
2761 <entry>Example</entry>
2762 <entry>Result</entry>
2768 <entry><literal><function>btrim</function>(<parameter>string</parameter>
2769 <type>bytea</type>, <parameter>bytes</parameter> <type>bytea</type>)</literal></entry>
2770 <entry><type>bytea</type></entry>
2772 Remove the longest string consisting only of bytes
2773 in <parameter>bytes</parameter> from the start and end of
2774 <parameter>string</parameter>
2776 <entry><literal>btrim(E'\\000trim\\000'::bytea, E'\\000'::bytea)</literal></entry>
2777 <entry><literal>trim</literal></entry>
2782 <literal><function>decode</function>(<parameter>string</parameter> <type>text</type>,
2783 <parameter>type</parameter> <type>text</type>)</literal>
2785 <entry><type>bytea</type></entry>
2787 Decode binary string from <parameter>string</parameter> previously
2788 encoded with <function>encode</>. Parameter type is same as in <function>encode</>.
2790 <entry><literal>decode(E'123\\000456', 'escape')</literal></entry>
2791 <entry><literal>123\000456</literal></entry>
2796 <literal><function>encode</function>(<parameter>string</parameter> <type>bytea</type>,
2797 <parameter>type</parameter> <type>text</type>)</literal>
2799 <entry><type>text</type></entry>
2801 Encode binary string to <acronym>ASCII</acronym>-only representation. Supported
2802 types are: <literal>base64</>, <literal>hex</>, <literal>escape</>.
2804 <entry><literal>encode(E'123\\000456'::bytea, 'escape')</literal></entry>
2805 <entry><literal>123\000456</literal></entry>
2809 <entry><literal><function>length</function>(<parameter>string</parameter>)</literal></entry>
2810 <entry><type>int</type></entry>
2812 Length of binary string
2814 <primary>binary string</primary>
2815 <secondary>length</secondary>
2818 <primary>length</primary>
2819 <secondary sortas="binary string">of a binary string</secondary>
2820 <see>binary strings, length</see>
2823 <entry><literal>length(E'jo\\000se'::bytea)</literal></entry>
2824 <entry><literal>5</literal></entry>
2828 <entry><literal><function>md5</function>(<parameter>string</parameter>)</literal></entry>
2829 <entry><type>text</type></entry>
2831 Calculates the MD5 hash of <parameter>string</parameter>,
2832 returning the result in hexadecimal
2834 <entry><literal>md5(E'Th\\000omas'::bytea)</literal></entry>
2835 <entry><literal>8ab2d3c9689aaf18 b4958c334c82d8b1</literal></entry>
2844 <sect1 id="functions-bitstring">
2845 <title>Bit String Functions and Operators</title>
2847 <indexterm zone="functions-bitstring">
2848 <primary>bit strings</primary>
2849 <secondary>functions</secondary>
2853 This section describes functions and operators for examining and
2854 manipulating bit strings, that is values of the types
2855 <type>bit</type> and <type>bit varying</type>. Aside from the
2856 usual comparison operators, the operators
2857 shown in <xref linkend="functions-bit-string-op-table"> can be used.
2858 Bit string operands of <literal>&</literal>, <literal>|</literal>,
2859 and <literal>#</literal> must be of equal length. When bit
2860 shifting, the original length of the string is preserved, as shown
2864 <table id="functions-bit-string-op-table">
2865 <title>Bit String Operators</title>
2870 <entry>Operator</entry>
2871 <entry>Description</entry>
2872 <entry>Example</entry>
2873 <entry>Result</entry>
2879 <entry> <literal>||</literal> </entry>
2880 <entry>concatenation</entry>
2881 <entry><literal>B'10001' || B'011'</literal></entry>
2882 <entry><literal>10001011</literal></entry>
2886 <entry> <literal>&</literal> </entry>
2887 <entry>bitwise AND</entry>
2888 <entry><literal>B'10001' & B'01101'</literal></entry>
2889 <entry><literal>00001</literal></entry>
2893 <entry> <literal>|</literal> </entry>
2894 <entry>bitwise OR</entry>
2895 <entry><literal>B'10001' | B'01101'</literal></entry>
2896 <entry><literal>11101</literal></entry>
2900 <entry> <literal>#</literal> </entry>
2901 <entry>bitwise XOR</entry>
2902 <entry><literal>B'10001' # B'01101'</literal></entry>
2903 <entry><literal>11100</literal></entry>
2907 <entry> <literal>~</literal> </entry>
2908 <entry>bitwise NOT</entry>
2909 <entry><literal>~ B'10001'</literal></entry>
2910 <entry><literal>01110</literal></entry>
2914 <entry> <literal><<</literal> </entry>
2915 <entry>bitwise shift left</entry>
2916 <entry><literal>B'10001' << 3</literal></entry>
2917 <entry><literal>01000</literal></entry>
2921 <entry> <literal>>></literal> </entry>
2922 <entry>bitwise shift right</entry>
2923 <entry><literal>B'10001' >> 2</literal></entry>
2924 <entry><literal>00100</literal></entry>
2931 The following <acronym>SQL</acronym>-standard functions work on bit
2932 strings as well as character strings:
2933 <literal><function>length</function></literal>,
2934 <literal><function>bit_length</function></literal>,
2935 <literal><function>octet_length</function></literal>,
2936 <literal><function>position</function></literal>,
2937 <literal><function>substring</function></literal>.
2941 In addition, it is possible to cast integral values to and from type
2945 44::bit(10) <lineannotation>0000101100</lineannotation>
2946 44::bit(3) <lineannotation>100</lineannotation>
2947 cast(-44 as bit(12)) <lineannotation>111111010100</lineannotation>
2948 '1110'::bit(4)::integer <lineannotation>14</lineannotation>
2950 Note that casting to just <quote>bit</> means casting to
2951 <literal>bit(1)</>, and so will deliver only the least significant
2957 Prior to <productname>PostgreSQL</productname> 8.0, casting an
2958 integer to <type>bit(n)</> would copy the leftmost <literal>n</>
2959 bits of the integer, whereas now it copies the rightmost <literal>n</>
2960 bits. Also, casting an integer to a bit string width wider than
2961 the integer itself will sign-extend on the left.
2968 <sect1 id="functions-matching">
2969 <title>Pattern Matching</title>
2971 <indexterm zone="functions-matching">
2972 <primary>pattern matching</primary>
2976 There are three separate approaches to pattern matching provided
2977 by <productname>PostgreSQL</productname>: the traditional
2978 <acronym>SQL</acronym> <function>LIKE</function> operator, the
2979 more recent <function>SIMILAR TO</function> operator (added in
2980 SQL:1999), and <acronym>POSIX</acronym>-style regular
2981 expressions. Aside from the basic <quote>does this string match
2982 this pattern?</> operators, functions are available to extract
2983 or replace matching substrings and to split a string at matching
2989 If you have pattern matching needs that go beyond this,
2990 consider writing a user-defined function in Perl or Tcl.
2994 <sect2 id="functions-like">
2995 <title><function>LIKE</function></title>
2998 <primary>LIKE</primary>
3002 <replaceable>string</replaceable> LIKE <replaceable>pattern</replaceable> <optional>ESCAPE <replaceable>escape-character</replaceable></optional>
3003 <replaceable>string</replaceable> NOT LIKE <replaceable>pattern</replaceable> <optional>ESCAPE <replaceable>escape-character</replaceable></optional>
3007 The <function>LIKE</function> expression returns true if the
3008 <replaceable>string</replaceable> matches the supplied
3009 <replaceable>pattern</replaceable>. (As
3010 expected, the <function>NOT LIKE</function> expression returns
3011 false if <function>LIKE</function> returns true, and vice versa.
3012 An equivalent expression is
3013 <literal>NOT (<replaceable>string</replaceable> LIKE
3014 <replaceable>pattern</replaceable>)</literal>.)
3018 If <replaceable>pattern</replaceable> does not contain percent
3019 signs or underscores, then the pattern only represents the string
3020 itself; in that case <function>LIKE</function> acts like the
3021 equals operator. An underscore (<literal>_</literal>) in
3022 <replaceable>pattern</replaceable> stands for (matches) any single
3023 character; a percent sign (<literal>%</literal>) matches any sequence
3024 of zero or more characters.
3030 'abc' LIKE 'abc' <lineannotation>true</lineannotation>
3031 'abc' LIKE 'a%' <lineannotation>true</lineannotation>
3032 'abc' LIKE '_b_' <lineannotation>true</lineannotation>
3033 'abc' LIKE 'c' <lineannotation>false</lineannotation>
3038 <function>LIKE</function> pattern matching always covers the entire
3039 string. Therefore, to match a sequence anywhere within a string, the
3040 pattern must start and end with a percent sign.
3044 To match a literal underscore or percent sign without matching
3045 other characters, the respective character in
3046 <replaceable>pattern</replaceable> must be
3047 preceded by the escape character. The default escape
3048 character is the backslash but a different one can be selected by
3049 using the <literal>ESCAPE</literal> clause. To match the escape
3050 character itself, write two escape characters.
3054 Note that the backslash already has a special meaning in string literals,
3055 so to write a pattern constant that contains a backslash you must write two
3056 backslashes in an SQL statement (assuming escape string syntax is used, see
3057 <xref linkend="sql-syntax-strings">). Thus, writing a pattern that
3058 actually matches a literal backslash means writing four backslashes in the
3059 statement. You can avoid this by selecting a different escape character
3060 with <literal>ESCAPE</literal>; then a backslash is not special to
3061 <function>LIKE</function> anymore. (But backslash is still special to the
3062 string literal parser, so you still need two of them to match a backslash.)
3066 It's also possible to select no escape character by writing
3067 <literal>ESCAPE ''</literal>. This effectively disables the
3068 escape mechanism, which makes it impossible to turn off the
3069 special meaning of underscore and percent signs in the pattern.
3073 The key word <token>ILIKE</token> can be used instead of
3074 <token>LIKE</token> to make the match case-insensitive according
3075 to the active locale. This is not in the <acronym>SQL</acronym> standard but is a
3076 <productname>PostgreSQL</productname> extension.
3080 The operator <literal>~~</literal> is equivalent to
3081 <function>LIKE</function>, and <literal>~~*</literal> corresponds to
3082 <function>ILIKE</function>. There are also
3083 <literal>!~~</literal> and <literal>!~~*</literal> operators that
3084 represent <function>NOT LIKE</function> and <function>NOT
3085 ILIKE</function>, respectively. All of these operators are
3086 <productname>PostgreSQL</productname>-specific.
3091 <sect2 id="functions-similarto-regexp">
3092 <title><function>SIMILAR TO</function> Regular Expressions</title>
3095 <primary>regular expression</primary>
3096 <!-- <seealso>pattern matching</seealso> breaks index build -->
3100 <primary>SIMILAR TO</primary>
3103 <primary>substring</primary>
3107 <replaceable>string</replaceable> SIMILAR TO <replaceable>pattern</replaceable> <optional>ESCAPE <replaceable>escape-character</replaceable></optional>
3108 <replaceable>string</replaceable> NOT SIMILAR TO <replaceable>pattern</replaceable> <optional>ESCAPE <replaceable>escape-character</replaceable></optional>
3112 The <function>SIMILAR TO</function> operator returns true or
3113 false depending on whether its pattern matches the given string.
3114 It is similar to <function>LIKE</function>, except that it
3115 interprets the pattern using the SQL standard's definition of a
3116 regular expression. SQL regular expressions are a curious cross
3117 between <function>LIKE</function> notation and common regular
3118 expression notation.
3122 Like <function>LIKE</function>, the <function>SIMILAR TO</function>
3123 operator succeeds only if its pattern matches the entire string;
3124 this is unlike common regular expression behavior where the pattern
3125 can match any part of the string.
3127 <function>LIKE</function>, <function>SIMILAR TO</function> uses
3128 <literal>_</> and <literal>%</> as wildcard characters denoting
3129 any single character and any string, respectively (these are
3130 comparable to <literal>.</> and <literal>.*</> in POSIX regular
3135 In addition to these facilities borrowed from <function>LIKE</function>,
3136 <function>SIMILAR TO</function> supports these pattern-matching
3137 metacharacters borrowed from POSIX regular expressions:
3142 <literal>|</literal> denotes alternation (either of two alternatives).
3147 <literal>*</literal> denotes repetition of the previous item zero
3153 <literal>+</literal> denotes repetition of the previous item one
3159 Parentheses <literal>()</literal> can be used to group items into
3160 a single logical item.
3165 A bracket expression <literal>[...]</literal> specifies a character
3166 class, just as in POSIX regular expressions.
3171 Notice that bounded repetition operators (<literal>?</> and
3172 <literal>{...}</>) are not provided, though they exist in POSIX.
3173 Also, the period (<literal>.</>) is not a metacharacter.
3177 As with <function>LIKE</>, a backslash disables the special meaning
3178 of any of these metacharacters; or a different escape character can
3179 be specified with <literal>ESCAPE</>.
3185 'abc' SIMILAR TO 'abc' <lineannotation>true</lineannotation>
3186 'abc' SIMILAR TO 'a' <lineannotation>false</lineannotation>
3187 'abc' SIMILAR TO '%(b|d)%' <lineannotation>true</lineannotation>
3188 'abc' SIMILAR TO '(b|c)%' <lineannotation>false</lineannotation>
3193 The <function>substring</> function with three parameters,
3194 <function>substring(<replaceable>string</replaceable> from
3195 <replaceable>pattern</replaceable> for
3196 <replaceable>escape-character</replaceable>)</function>, provides
3197 extraction of a substring that matches an SQL
3198 regular expression pattern. As with <literal>SIMILAR TO</>, the
3199 specified pattern must match the entire data string, or else the
3200 function fails and returns null. To indicate the part of the
3201 pattern that should be returned on success, the pattern must contain
3202 two occurrences of the escape character followed by a double quote
3203 (<literal>"</>). <!-- " font-lock sanity -->
3204 The text matching the portion of the pattern
3205 between these markers is returned.
3209 Some examples, with <literal>#"</> delimiting the return string:
3211 substring('foobar' from '%#"o_b#"%' for '#') <lineannotation>oob</lineannotation>
3212 substring('foobar' from '#"o_b#"%' for '#') <lineannotation>NULL</lineannotation>
3217 <sect2 id="functions-posix-regexp">
3218 <title><acronym>POSIX</acronym> Regular Expressions</title>
3220 <indexterm zone="functions-posix-regexp">
3221 <primary>regular expression</primary>
3222 <seealso>pattern matching</seealso>
3225 <primary>substring</primary>
3228 <primary>regexp_replace</primary>
3231 <primary>regexp_matches</primary>
3234 <primary>regexp_split_to_table</primary>
3237 <primary>regexp_split_to_array</primary>
3241 <xref linkend="functions-posix-table"> lists the available
3242 operators for pattern matching using POSIX regular expressions.
3245 <table id="functions-posix-table">
3246 <title>Regular Expression Match Operators</title>
3251 <entry>Operator</entry>
3252 <entry>Description</entry>
3253 <entry>Example</entry>
3259 <entry> <literal>~</literal> </entry>
3260 <entry>Matches regular expression, case sensitive</entry>
3261 <entry><literal>'thomas' ~ '.*thomas.*'</literal></entry>
3265 <entry> <literal>~*</literal> </entry>
3266 <entry>Matches regular expression, case insensitive</entry>
3267 <entry><literal>'thomas' ~* '.*Thomas.*'</literal></entry>
3271 <entry> <literal>!~</literal> </entry>
3272 <entry>Does not match regular expression, case sensitive</entry>
3273 <entry><literal>'thomas' !~ '.*Thomas.*'</literal></entry>
3277 <entry> <literal>!~*</literal> </entry>
3278 <entry>Does not match regular expression, case insensitive</entry>
3279 <entry><literal>'thomas' !~* '.*vadim.*'</literal></entry>
3286 <acronym>POSIX</acronym> regular expressions provide a more
3288 pattern matching than the <function>LIKE</function> and
3289 <function>SIMILAR TO</> operators.
3290 Many Unix tools such as <command>egrep</command>,
3291 <command>sed</command>, or <command>awk</command> use a pattern
3292 matching language that is similar to the one described here.
3296 A regular expression is a character sequence that is an
3297 abbreviated definition of a set of strings (a <firstterm>regular
3298 set</firstterm>). A string is said to match a regular expression
3299 if it is a member of the regular set described by the regular
3300 expression. As with <function>LIKE</function>, pattern characters
3301 match string characters exactly unless they are special characters
3302 in the regular expression language — but regular expressions use
3303 different special characters than <function>LIKE</function> does.
3304 Unlike <function>LIKE</function> patterns, a
3305 regular expression is allowed to match anywhere within a string, unless
3306 the regular expression is explicitly anchored to the beginning or
3313 'abc' ~ 'abc' <lineannotation>true</lineannotation>
3314 'abc' ~ '^a' <lineannotation>true</lineannotation>
3315 'abc' ~ '(b|d)' <lineannotation>true</lineannotation>
3316 'abc' ~ '^(b|c)' <lineannotation>false</lineannotation>
3321 The <acronym>POSIX</acronym> pattern language is described in much
3322 greater detail below.
3326 The <function>substring</> function with two parameters,
3327 <function>substring(<replaceable>string</replaceable> from
3328 <replaceable>pattern</replaceable>)</function>, provides extraction of a
3330 that matches a POSIX regular expression pattern. It returns null if
3331 there is no match, otherwise the portion of the text that matched the
3332 pattern. But if the pattern contains any parentheses, the portion
3333 of the text that matched the first parenthesized subexpression (the
3334 one whose left parenthesis comes first) is
3335 returned. You can put parentheses around the whole expression
3336 if you want to use parentheses within it without triggering this
3337 exception. If you need parentheses in the pattern before the
3338 subexpression you want to extract, see the non-capturing parentheses
3345 substring('foobar' from 'o.b') <lineannotation>oob</lineannotation>
3346 substring('foobar' from 'o(.)b') <lineannotation>o</lineannotation>
3351 The <function>regexp_replace</> function provides substitution of
3352 new text for substrings that match POSIX regular expression patterns.
3354 <function>regexp_replace</function>(<replaceable>source</>,
3355 <replaceable>pattern</>, <replaceable>replacement</>
3356 <optional>, <replaceable>flags</> </optional>).
3357 The <replaceable>source</> string is returned unchanged if
3358 there is no match to the <replaceable>pattern</>. If there is a
3359 match, the <replaceable>source</> string is returned with the
3360 <replaceable>replacement</> string substituted for the matching
3361 substring. The <replaceable>replacement</> string can contain
3362 <literal>\</><replaceable>n</>, where <replaceable>n</> is <literal>1</>
3363 through <literal>9</>, to indicate that the source substring matching the
3364 <replaceable>n</>'th parenthesized subexpression of the pattern should be
3365 inserted, and it can contain <literal>\&</> to indicate that the
3366 substring matching the entire pattern should be inserted. Write
3367 <literal>\\</> if you need to put a literal backslash in the replacement
3368 text. (As always, remember to double backslashes written in literal
3369 constant strings, assuming escape string syntax is used.)
3370 The <replaceable>flags</> parameter is an optional text
3371 string containing zero or more single-letter flags that change the
3372 function's behavior. Flag <literal>i</> specifies case-insensitive
3373 matching, while flag <literal>g</> specifies replacement of each matching
3374 substring rather than only the first one. Other supported flags are
3375 described in <xref linkend="posix-embedded-options-table">.
3381 regexp_replace('foobarbaz', 'b..', 'X')
3382 <lineannotation>fooXbaz</lineannotation>
3383 regexp_replace('foobarbaz', 'b..', 'X', 'g')
3384 <lineannotation>fooXX</lineannotation>
3385 regexp_replace('foobarbaz', 'b(..)', E'X\\1Y', 'g')
3386 <lineannotation>fooXarYXazY</lineannotation>
3391 The <function>regexp_matches</> function returns all of the captured
3392 substrings resulting from matching a POSIX regular expression pattern.
3394 <function>regexp_matches</function>(<replaceable>string</>, <replaceable>pattern</>
3395 <optional>, <replaceable>flags</> </optional>).
3396 If there is no match to the <replaceable>pattern</>, the function returns
3397 no rows. If there is a match, the function returns a text array whose
3398 <replaceable>n</>'th element is the substring matching the
3399 <replaceable>n</>'th parenthesized subexpression of the pattern
3400 (not counting <quote>non-capturing</> parentheses; see below for
3401 details). If the pattern does not contain any parenthesized
3402 subexpressions, then the result is a single-element text array containing
3403 the substring matching the whole pattern.
3404 The <replaceable>flags</> parameter is an optional text
3405 string containing zero or more single-letter flags that change the
3406 function's behavior. Flag <literal>g</> causes the function to find
3407 each match in the string, not only the first one, and return a row for
3408 each such match. Other supported
3409 flags are described in <xref linkend="posix-embedded-options-table">.
3415 SELECT regexp_matches('foobarbequebaz', '(bar)(beque)');
3421 SELECT regexp_matches('foobarbequebazilbarfbonk', '(b[^b]+)(b[^b]+)', 'g');
3428 SELECT regexp_matches('foobarbequebaz', 'barbeque');
3437 The <function>regexp_split_to_table</> function splits a string using a POSIX
3438 regular expression pattern as a delimiter. It has the syntax
3439 <function>regexp_split_to_table</function>(<replaceable>string</>, <replaceable>pattern</>
3440 <optional>, <replaceable>flags</> </optional>).
3441 If there is no match to the <replaceable>pattern</>, the function returns the
3442 <replaceable>string</>. If there is at least one match, for each match it returns
3443 the text from the end of the last match (or the beginning of the string)
3444 to the beginning of the match. When there are no more matches, it
3445 returns the text from the end of the last match to the end of the string.
3446 The <replaceable>flags</> parameter is an optional text string containing
3447 zero or more single-letter flags that change the function's behavior.
3448 <function>regexp_split_to_table</function> supports the flags described in
3449 <xref linkend="posix-embedded-options-table">.
3453 The <function>regexp_split_to_array</> function behaves the same as
3454 <function>regexp_split_to_table</>, except that <function>regexp_split_to_array</>
3455 returns its result as an array of <type>text</>. It has the syntax
3456 <function>regexp_split_to_array</function>(<replaceable>string</>, <replaceable>pattern</>
3457 <optional>, <replaceable>flags</> </optional>).
3458 The parameters are the same as for <function>regexp_split_to_table</>.
3465 SELECT foo FROM regexp_split_to_table('the quick brown fox jumped over the lazy dog', E'\\s+') AS foo;
3479 SELECT regexp_split_to_array('the quick brown fox jumped over the lazy dog', E'\\s+');
3480 regexp_split_to_array
3481 ------------------------------------------------
3482 {the,quick,brown,fox,jumped,over,the,lazy,dog}
3485 SELECT foo FROM regexp_split_to_table('the quick brown fox', E'\\s*') AS foo;
3509 As the last example demonstrates, the regexp split functions ignore
3510 zero-length matches that occur at the start or end of the string
3511 or immediately after a previous match. This is contrary to the strict
3512 definition of regexp matching that is implemented by
3513 <function>regexp_matches</>, but is usually the most convenient behavior
3514 in practice. Other software systems such as Perl use similar definitions.
3517 <!-- derived from the re_syntax.n man page -->
3519 <sect3 id="posix-syntax-details">
3520 <title>Regular Expression Details</title>
3523 <productname>PostgreSQL</productname>'s regular expressions are implemented
3524 using a software package written by Henry Spencer. Much of
3525 the description of regular expressions below is copied verbatim from his
3530 Regular expressions (<acronym>RE</acronym>s), as defined in
3531 <acronym>POSIX</acronym> 1003.2, come in two forms:
3532 <firstterm>extended</> <acronym>RE</acronym>s or <acronym>ERE</>s
3533 (roughly those of <command>egrep</command>), and
3534 <firstterm>basic</> <acronym>RE</acronym>s or <acronym>BRE</>s
3535 (roughly those of <command>ed</command>).
3536 <productname>PostgreSQL</productname> supports both forms, and
3537 also implements some extensions
3538 that are not in the POSIX standard, but have become widely used
3539 due to their availability in programming languages such as Perl and Tcl.
3540 <acronym>RE</acronym>s using these non-POSIX extensions are called
3541 <firstterm>advanced</> <acronym>RE</acronym>s or <acronym>ARE</>s
3542 in this documentation. AREs are almost an exact superset of EREs,
3543 but BREs have several notational incompatibilities (as well as being
3545 We first describe the ARE and ERE forms, noting features that apply
3546 only to AREs, and then describe how BREs differ.
3551 The form of regular expressions accepted by
3552 <productname>PostgreSQL</> can be chosen by setting the <xref
3553 linkend="guc-regex-flavor"> run-time parameter. The usual
3554 setting is <literal>advanced</>, but one might choose
3555 <literal>extended</> for backwards compatibility with
3556 pre-7.4 releases of <productname>PostgreSQL</>.
3561 A regular expression is defined as one or more
3562 <firstterm>branches</firstterm>, separated by
3563 <literal>|</literal>. It matches anything that matches one of the
3568 A branch is zero or more <firstterm>quantified atoms</> or
3569 <firstterm>constraints</>, concatenated.
3570 It matches a match for the first, followed by a match for the second, etc;
3571 an empty branch matches the empty string.
3575 A quantified atom is an <firstterm>atom</> possibly followed
3576 by a single <firstterm>quantifier</>.
3577 Without a quantifier, it matches a match for the atom.
3578 With a quantifier, it can match some number of matches of the atom.
3579 An <firstterm>atom</firstterm> can be any of the possibilities
3580 shown in <xref linkend="posix-atoms-table">.
3581 The possible quantifiers and their meanings are shown in
3582 <xref linkend="posix-quantifiers-table">.
3586 A <firstterm>constraint</> matches an empty string, but matches only when
3587 specific conditions are met. A constraint can be used where an atom
3588 could be used, except it cannot be followed by a quantifier.
3589 The simple constraints are shown in
3590 <xref linkend="posix-constraints-table">;
3591 some more constraints are described later.
3595 <table id="posix-atoms-table">
3596 <title>Regular Expression Atoms</title>
3602 <entry>Description</entry>
3608 <entry> <literal>(</><replaceable>re</><literal>)</> </entry>
3609 <entry> (where <replaceable>re</> is any regular expression)
3611 <replaceable>re</>, with the match noted for possible reporting </entry>
3615 <entry> <literal>(?:</><replaceable>re</><literal>)</> </entry>
3616 <entry> as above, but the match is not noted for reporting
3617 (a <quote>non-capturing</> set of parentheses)
3618 (AREs only) </entry>
3622 <entry> <literal>.</> </entry>
3623 <entry> matches any single character </entry>
3627 <entry> <literal>[</><replaceable>chars</><literal>]</> </entry>
3628 <entry> a <firstterm>bracket expression</>,
3629 matching any one of the <replaceable>chars</> (see
3630 <xref linkend="posix-bracket-expressions"> for more detail) </entry>
3634 <entry> <literal>\</><replaceable>k</> </entry>
3635 <entry> (where <replaceable>k</> is a non-alphanumeric character)
3636 matches that character taken as an ordinary character,
3637 e.g., <literal>\\</> matches a backslash character </entry>
3641 <entry> <literal>\</><replaceable>c</> </entry>
3642 <entry> where <replaceable>c</> is alphanumeric
3643 (possibly followed by other characters)
3644 is an <firstterm>escape</>, see <xref linkend="posix-escape-sequences">
3645 (AREs only; in EREs and BREs, this matches <replaceable>c</>) </entry>
3649 <entry> <literal>{</> </entry>
3650 <entry> when followed by a character other than a digit,
3651 matches the left-brace character <literal>{</>;
3652 when followed by a digit, it is the beginning of a
3653 <replaceable>bound</> (see below) </entry>
3657 <entry> <replaceable>x</> </entry>
3658 <entry> where <replaceable>x</> is a single character with no other
3659 significance, matches that character </entry>
3666 An RE cannot end with <literal>\</>.
3671 Remember that the backslash (<literal>\</literal>) already has a special
3672 meaning in <productname>PostgreSQL</> string literals.
3673 To write a pattern constant that contains a backslash,
3674 you must write two backslashes in the statement, assuming escape
3675 string syntax is used (see <xref linkend="sql-syntax-strings">).
3679 <table id="posix-quantifiers-table">
3680 <title>Regular Expression Quantifiers</title>
3685 <entry>Quantifier</entry>
3686 <entry>Matches</entry>
3692 <entry> <literal>*</> </entry>
3693 <entry> a sequence of 0 or more matches of the atom </entry>
3697 <entry> <literal>+</> </entry>
3698 <entry> a sequence of 1 or more matches of the atom </entry>
3702 <entry> <literal>?</> </entry>
3703 <entry> a sequence of 0 or 1 matches of the atom </entry>
3707 <entry> <literal>{</><replaceable>m</><literal>}</> </entry>
3708 <entry> a sequence of exactly <replaceable>m</> matches of the atom </entry>
3712 <entry> <literal>{</><replaceable>m</><literal>,}</> </entry>
3713 <entry> a sequence of <replaceable>m</> or more matches of the atom </entry>
3718 <literal>{</><replaceable>m</><literal>,</><replaceable>n</><literal>}</> </entry>
3719 <entry> a sequence of <replaceable>m</> through <replaceable>n</>
3720 (inclusive) matches of the atom; <replaceable>m</> cannot exceed
3721 <replaceable>n</> </entry>
3725 <entry> <literal>*?</> </entry>
3726 <entry> non-greedy version of <literal>*</> </entry>
3730 <entry> <literal>+?</> </entry>
3731 <entry> non-greedy version of <literal>+</> </entry>
3735 <entry> <literal>??</> </entry>
3736 <entry> non-greedy version of <literal>?</> </entry>
3740 <entry> <literal>{</><replaceable>m</><literal>}?</> </entry>
3741 <entry> non-greedy version of <literal>{</><replaceable>m</><literal>}</> </entry>
3745 <entry> <literal>{</><replaceable>m</><literal>,}?</> </entry>
3746 <entry> non-greedy version of <literal>{</><replaceable>m</><literal>,}</> </entry>
3751 <literal>{</><replaceable>m</><literal>,</><replaceable>n</><literal>}?</> </entry>
3752 <entry> non-greedy version of <literal>{</><replaceable>m</><literal>,</><replaceable>n</><literal>}</> </entry>
3759 The forms using <literal>{</><replaceable>...</><literal>}</>
3760 are known as <firstterm>bounds</>.
3761 The numbers <replaceable>m</> and <replaceable>n</> within a bound are
3762 unsigned decimal integers with permissible values from 0 to 255 inclusive.
3766 <firstterm>Non-greedy</> quantifiers (available in AREs only) match the
3767 same possibilities as their corresponding normal (<firstterm>greedy</>)
3768 counterparts, but prefer the smallest number rather than the largest
3770 See <xref linkend="posix-matching-rules"> for more detail.
3775 A quantifier cannot immediately follow another quantifier, e.g.,
3776 <literal>**</> is invalid.
3778 begin an expression or subexpression or follow
3779 <literal>^</literal> or <literal>|</literal>.
3783 <table id="posix-constraints-table">
3784 <title>Regular Expression Constraints</title>
3789 <entry>Constraint</entry>
3790 <entry>Description</entry>
3796 <entry> <literal>^</> </entry>
3797 <entry> matches at the beginning of the string </entry>
3801 <entry> <literal>$</> </entry>
3802 <entry> matches at the end of the string </entry>
3806 <entry> <literal>(?=</><replaceable>re</><literal>)</> </entry>
3807 <entry> <firstterm>positive lookahead</> matches at any point
3808 where a substring matching <replaceable>re</> begins
3809 (AREs only) </entry>
3813 <entry> <literal>(?!</><replaceable>re</><literal>)</> </entry>
3814 <entry> <firstterm>negative lookahead</> matches at any point
3815 where no substring matching <replaceable>re</> begins
3816 (AREs only) </entry>
3823 Lookahead constraints cannot contain <firstterm>back references</>
3824 (see <xref linkend="posix-escape-sequences">),
3825 and all parentheses within them are considered non-capturing.
3829 <sect3 id="posix-bracket-expressions">
3830 <title>Bracket Expressions</title>
3833 A <firstterm>bracket expression</firstterm> is a list of
3834 characters enclosed in <literal>[]</literal>. It normally matches
3835 any single character from the list (but see below). If the list
3836 begins with <literal>^</literal>, it matches any single character
3837 <emphasis>not</> from the rest of the list.
3839 in the list are separated by <literal>-</literal>, this is
3840 shorthand for the full range of characters between those two
3841 (inclusive) in the collating sequence,
3842 e.g., <literal>[0-9]</literal> in <acronym>ASCII</acronym> matches
3843 any decimal digit. It is illegal for two ranges to share an
3844 endpoint, e.g., <literal>a-c-e</literal>. Ranges are very
3845 collating-sequence-dependent, so portable programs should avoid
3850 To include a literal <literal>]</literal> in the list, make it the
3851 first character (after <literal>^</literal>, if that is used). To
3852 include a literal <literal>-</literal>, make it the first or last
3853 character, or the second endpoint of a range. To use a literal
3854 <literal>-</literal> as the first endpoint of a range, enclose it
3855 in <literal>[.</literal> and <literal>.]</literal> to make it a
3856 collating element (see below). With the exception of these characters,
3857 some combinations using <literal>[</literal>
3858 (see next paragraphs), and escapes (AREs only), all other special
3859 characters lose their special significance within a bracket expression.
3860 In particular, <literal>\</literal> is not special when following
3861 ERE or BRE rules, though it is special (as introducing an escape)
3866 Within a bracket expression, a collating element (a character, a
3867 multiple-character sequence that collates as if it were a single
3868 character, or a collating-sequence name for either) enclosed in
3869 <literal>[.</literal> and <literal>.]</literal> stands for the
3870 sequence of characters of that collating element. The sequence is
3871 treated as a single element of the bracket expression's list. This
3873 expression containing a multiple-character collating element to
3874 match more than one character, e.g., if the collating sequence
3875 includes a <literal>ch</literal> collating element, then the RE
3876 <literal>[[.ch.]]*c</literal> matches the first five characters of
3877 <literal>chchcc</literal>.
3882 <productname>PostgreSQL</> currently does not support multi-character collating
3883 elements. This information describes possible future behavior.
3888 Within a bracket expression, a collating element enclosed in
3889 <literal>[=</literal> and <literal>=]</literal> is an <firstterm>equivalence
3890 class</>, standing for the sequences of characters of all collating
3891 elements equivalent to that one, including itself. (If there are
3892 no other equivalent collating elements, the treatment is as if the
3893 enclosing delimiters were <literal>[.</literal> and
3894 <literal>.]</literal>.) For example, if <literal>o</literal> and
3895 <literal>^</literal> are the members of an equivalence class, then
3896 <literal>[[=o=]]</literal>, <literal>[[=^=]]</literal>, and
3897 <literal>[o^]</literal> are all synonymous. An equivalence class
3898 cannot be an endpoint of a range.
3902 Within a bracket expression, the name of a character class
3903 enclosed in <literal>[:</literal> and <literal>:]</literal> stands
3904 for the list of all characters belonging to that class. Standard
3905 character class names are: <literal>alnum</literal>,
3906 <literal>alpha</literal>, <literal>blank</literal>,
3907 <literal>cntrl</literal>, <literal>digit</literal>,
3908 <literal>graph</literal>, <literal>lower</literal>,
3909 <literal>print</literal>, <literal>punct</literal>,
3910 <literal>space</literal>, <literal>upper</literal>,
3911 <literal>xdigit</literal>. These stand for the character classes
3913 <citerefentry><refentrytitle>ctype</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
3914 A locale can provide others. A character class cannot be used as
3915 an endpoint of a range.
3919 There are two special cases of bracket expressions: the bracket
3920 expressions <literal>[[:<:]]</literal> and
3921 <literal>[[:>:]]</literal> are constraints,
3922 matching empty strings at the beginning
3923 and end of a word respectively. A word is defined as a sequence
3924 of word characters that is neither preceded nor followed by word
3925 characters. A word character is an <literal>alnum</> character (as
3927 <citerefentry><refentrytitle>ctype</refentrytitle><manvolnum>3</manvolnum></citerefentry>)
3928 or an underscore. This is an extension, compatible with but not
3929 specified by <acronym>POSIX</acronym> 1003.2, and should be used with
3930 caution in software intended to be portable to other systems.
3931 The constraint escapes described below are usually preferable; they
3932 are no more standard, but are easier to type.
3936 <sect3 id="posix-escape-sequences">
3937 <title>Regular Expression Escapes</title>
3940 <firstterm>Escapes</> are special sequences beginning with <literal>\</>
3941 followed by an alphanumeric character. Escapes come in several varieties:
3942 character entry, class shorthands, constraint escapes, and back references.
3943 A <literal>\</> followed by an alphanumeric character but not constituting
3944 a valid escape is illegal in AREs.
3945 In EREs, there are no escapes: outside a bracket expression,
3946 a <literal>\</> followed by an alphanumeric character merely stands for
3947 that character as an ordinary character, and inside a bracket expression,
3948 <literal>\</> is an ordinary character.
3949 (The latter is the one actual incompatibility between EREs and AREs.)
3953 <firstterm>Character-entry escapes</> exist to make it easier to specify
3954 non-printing and other inconvenient characters in REs. They are
3955 shown in <xref linkend="posix-character-entry-escapes-table">.
3959 <firstterm>Class-shorthand escapes</> provide shorthands for certain
3960 commonly-used character classes. They are
3961 shown in <xref linkend="posix-class-shorthand-escapes-table">.
3965 A <firstterm>constraint escape</> is a constraint,
3966 matching the empty string if specific conditions are met,
3967 written as an escape. They are
3968 shown in <xref linkend="posix-constraint-escapes-table">.
3972 A <firstterm>back reference</> (<literal>\</><replaceable>n</>) matches the
3973 same string matched by the previous parenthesized subexpression specified
3974 by the number <replaceable>n</>
3975 (see <xref linkend="posix-constraint-backref-table">). For example,
3976 <literal>([bc])\1</> matches <literal>bb</> or <literal>cc</>
3977 but not <literal>bc</> or <literal>cb</>.
3978 The subexpression must entirely precede the back reference in the RE.
3979 Subexpressions are numbered in the order of their leading parentheses.
3980 Non-capturing parentheses do not define subexpressions.
3985 Keep in mind that an escape's leading <literal>\</> will need to be
3986 doubled when entering the pattern as an SQL string constant. For example:
3988 '123' ~ E'^\\d{3}' <lineannotation>true</lineannotation>
3993 <table id="posix-character-entry-escapes-table">
3994 <title>Regular Expression Character-Entry Escapes</title>
3999 <entry>Escape</entry>
4000 <entry>Description</entry>
4006 <entry> <literal>\a</> </entry>
4007 <entry> alert (bell) character, as in C </entry>
4011 <entry> <literal>\b</> </entry>
4012 <entry> backspace, as in C </entry>
4016 <entry> <literal>\B</> </entry>
4017 <entry> synonym for backslash (<literal>\</>) to help reduce the need for backslash
4022 <entry> <literal>\c</><replaceable>X</> </entry>
4023 <entry> (where <replaceable>X</> is any character) the character whose
4024 low-order 5 bits are the same as those of
4025 <replaceable>X</>, and whose other bits are all zero </entry>
4029 <entry> <literal>\e</> </entry>
4030 <entry> the character whose collating-sequence name
4032 or failing that, the character with octal value 033 </entry>
4036 <entry> <literal>\f</> </entry>
4037 <entry> form feed, as in C </entry>
4041 <entry> <literal>\n</> </entry>
4042 <entry> newline, as in C </entry>
4046 <entry> <literal>\r</> </entry>
4047 <entry> carriage return, as in C </entry>
4051 <entry> <literal>\t</> </entry>
4052 <entry> horizontal tab, as in C </entry>
4056 <entry> <literal>\u</><replaceable>wxyz</> </entry>
4057 <entry> (where <replaceable>wxyz</> is exactly four hexadecimal digits)
4058 the UTF16 (Unicode, 16-bit) character <literal>U+</><replaceable>wxyz</>
4059 in the local byte ordering </entry>
4063 <entry> <literal>\U</><replaceable>stuvwxyz</> </entry>
4064 <entry> (where <replaceable>stuvwxyz</> is exactly eight hexadecimal
4066 reserved for a hypothetical Unicode extension to 32 bits
4071 <entry> <literal>\v</> </entry>
4072 <entry> vertical tab, as in C </entry>
4076 <entry> <literal>\x</><replaceable>hhh</> </entry>
4077 <entry> (where <replaceable>hhh</> is any sequence of hexadecimal
4079 the character whose hexadecimal value is
4080 <literal>0x</><replaceable>hhh</>
4081 (a single character no matter how many hexadecimal digits are used)
4086 <entry> <literal>\0</> </entry>
4087 <entry> the character whose value is <literal>0</> (the null byte)</entry>
4091 <entry> <literal>\</><replaceable>xy</> </entry>
4092 <entry> (where <replaceable>xy</> is exactly two octal digits,
4093 and is not a <firstterm>back reference</>)
4094 the character whose octal value is
4095 <literal>0</><replaceable>xy</> </entry>
4099 <entry> <literal>\</><replaceable>xyz</> </entry>
4100 <entry> (where <replaceable>xyz</> is exactly three octal digits,
4101 and is not a <firstterm>back reference</>)
4102 the character whose octal value is
4103 <literal>0</><replaceable>xyz</> </entry>
4110 Hexadecimal digits are <literal>0</>-<literal>9</>,
4111 <literal>a</>-<literal>f</>, and <literal>A</>-<literal>F</>.
4112 Octal digits are <literal>0</>-<literal>7</>.
4116 The character-entry escapes are always taken as ordinary characters.
4117 For example, <literal>\135</> is <literal>]</> in ASCII, but
4118 <literal>\135</> does not terminate a bracket expression.
4121 <table id="posix-class-shorthand-escapes-table">
4122 <title>Regular Expression Class-Shorthand Escapes</title>
4127 <entry>Escape</entry>
4128 <entry>Description</entry>
4134 <entry> <literal>\d</> </entry>
4135 <entry> <literal>[[:digit:]]</> </entry>
4139 <entry> <literal>\s</> </entry>
4140 <entry> <literal>[[:space:]]</> </entry>
4144 <entry> <literal>\w</> </entry>
4145 <entry> <literal>[[:alnum:]_]</>
4146 (note underscore is included) </entry>
4150 <entry> <literal>\D</> </entry>
4151 <entry> <literal>[^[:digit:]]</> </entry>
4155 <entry> <literal>\S</> </entry>
4156 <entry> <literal>[^[:space:]]</> </entry>
4160 <entry> <literal>\W</> </entry>
4161 <entry> <literal>[^[:alnum:]_]</>
4162 (note underscore is included) </entry>
4169 Within bracket expressions, <literal>\d</>, <literal>\s</>,
4170 and <literal>\w</> lose their outer brackets,
4171 and <literal>\D</>, <literal>\S</>, and <literal>\W</> are illegal.
4172 (So, for example, <literal>[a-c\d]</> is equivalent to
4173 <literal>[a-c[:digit:]]</>.
4174 Also, <literal>[a-c\D]</>, which is equivalent to
4175 <literal>[a-c^[:digit:]]</>, is illegal.)
4178 <table id="posix-constraint-escapes-table">
4179 <title>Regular Expression Constraint Escapes</title>
4184 <entry>Escape</entry>
4185 <entry>Description</entry>
4191 <entry> <literal>\A</> </entry>
4192 <entry> matches only at the beginning of the string
4193 (see <xref linkend="posix-matching-rules"> for how this differs from
4194 <literal>^</>) </entry>
4198 <entry> <literal>\m</> </entry>
4199 <entry> matches only at the beginning of a word </entry>
4203 <entry> <literal>\M</> </entry>
4204 <entry> matches only at the end of a word </entry>
4208 <entry> <literal>\y</> </entry>
4209 <entry> matches only at the beginning or end of a word </entry>
4213 <entry> <literal>\Y</> </entry>
4214 <entry> matches only at a point that is not the beginning or end of a
4219 <entry> <literal>\Z</> </entry>
4220 <entry> matches only at the end of the string
4221 (see <xref linkend="posix-matching-rules"> for how this differs from
4222 <literal>$</>) </entry>
4229 A word is defined as in the specification of
4230 <literal>[[:<:]]</> and <literal>[[:>:]]</> above.
4231 Constraint escapes are illegal within bracket expressions.
4234 <table id="posix-constraint-backref-table">
4235 <title>Regular Expression Back References</title>
4240 <entry>Escape</entry>
4241 <entry>Description</entry>
4247 <entry> <literal>\</><replaceable>m</> </entry>
4248 <entry> (where <replaceable>m</> is a nonzero digit)
4249 a back reference to the <replaceable>m</>'th subexpression </entry>
4253 <entry> <literal>\</><replaceable>mnn</> </entry>
4254 <entry> (where <replaceable>m</> is a nonzero digit, and
4255 <replaceable>nn</> is some more digits, and the decimal value
4256 <replaceable>mnn</> is not greater than the number of closing capturing
4257 parentheses seen so far)
4258 a back reference to the <replaceable>mnn</>'th subexpression </entry>
4266 There is an inherent ambiguity between octal character-entry
4267 escapes and back references, which is resolved by the following heuristics,
4269 A leading zero always indicates an octal escape.
4270 A single non-zero digit, not followed by another digit,
4271 is always taken as a back reference.
4272 A multi-digit sequence not starting with a zero is taken as a back
4273 reference if it comes after a suitable subexpression
4274 (i.e., the number is in the legal range for a back reference),
4275 and otherwise is taken as octal.
4280 <sect3 id="posix-metasyntax">
4281 <title>Regular Expression Metasyntax</title>
4284 In addition to the main syntax described above, there are some special
4285 forms and miscellaneous syntactic facilities available.
4289 Normally the flavor of RE being used is determined by
4290 <varname>regex_flavor</>.
4291 However, this can be overridden by a <firstterm>director</> prefix.
4292 If an RE begins with <literal>***:</>,
4293 the rest of the RE is taken as an ARE regardless of
4294 <varname>regex_flavor</>.
4295 If an RE begins with <literal>***=</>,
4296 the rest of the RE is taken to be a literal string,
4297 with all characters considered ordinary characters.
4301 An ARE can begin with <firstterm>embedded options</>:
4302 a sequence <literal>(?</><replaceable>xyz</><literal>)</>
4303 (where <replaceable>xyz</> is one or more alphabetic characters)
4304 specifies options affecting the rest of the RE.
4305 These options override any previously determined options (including
4306 both the RE flavor and case sensitivity).
4307 The available option letters are
4308 shown in <xref linkend="posix-embedded-options-table">.
4311 <table id="posix-embedded-options-table">
4312 <title>ARE Embedded-Option Letters</title>
4317 <entry>Option</entry>
4318 <entry>Description</entry>
4324 <entry> <literal>b</> </entry>
4325 <entry> rest of RE is a BRE </entry>
4329 <entry> <literal>c</> </entry>
4330 <entry> case-sensitive matching (overrides operator type) </entry>
4334 <entry> <literal>e</> </entry>
4335 <entry> rest of RE is an ERE </entry>
4339 <entry> <literal>i</> </entry>
4340 <entry> case-insensitive matching (see
4341 <xref linkend="posix-matching-rules">) (overrides operator type) </entry>
4345 <entry> <literal>m</> </entry>
4346 <entry> historical synonym for <literal>n</> </entry>
4350 <entry> <literal>n</> </entry>
4351 <entry> newline-sensitive matching (see
4352 <xref linkend="posix-matching-rules">) </entry>
4356 <entry> <literal>p</> </entry>
4357 <entry> partial newline-sensitive matching (see
4358 <xref linkend="posix-matching-rules">) </entry>
4362 <entry> <literal>q</> </entry>
4363 <entry> rest of RE is a literal (<quote>quoted</>) string, all ordinary
4368 <entry> <literal>s</> </entry>
4369 <entry> non-newline-sensitive matching (default) </entry>
4373 <entry> <literal>t</> </entry>
4374 <entry> tight syntax (default; see below) </entry>
4378 <entry> <literal>w</> </entry>
4379 <entry> inverse partial newline-sensitive (<quote>weird</>) matching
4380 (see <xref linkend="posix-matching-rules">) </entry>
4384 <entry> <literal>x</> </entry>
4385 <entry> expanded syntax (see below) </entry>
4392 Embedded options take effect at the <literal>)</> terminating the sequence.
4393 They can appear only at the start of an ARE (after the
4394 <literal>***:</> director if any).
4398 In addition to the usual (<firstterm>tight</>) RE syntax, in which all
4399 characters are significant, there is an <firstterm>expanded</> syntax,
4400 available by specifying the embedded <literal>x</> option.
4401 In the expanded syntax,
4402 white-space characters in the RE are ignored, as are
4403 all characters between a <literal>#</>
4404 and the following newline (or the end of the RE). This
4405 permits paragraphing and commenting a complex RE.
4406 There are three exceptions to that basic rule:
4411 a white-space character or <literal>#</> preceded by <literal>\</> is
4417 white space or <literal>#</> within a bracket expression is retained
4422 white space and comments cannot appear within multi-character symbols,
4423 such as <literal>(?:</>
4428 For this purpose, white-space characters are blank, tab, newline, and
4429 any character that belongs to the <replaceable>space</> character class.
4433 Finally, in an ARE, outside bracket expressions, the sequence
4434 <literal>(?#</><replaceable>ttt</><literal>)</>
4435 (where <replaceable>ttt</> is any text not containing a <literal>)</>)
4436 is a comment, completely ignored.
4437 Again, this is not allowed between the characters of
4438 multi-character symbols, like <literal>(?:</>.
4439 Such comments are more a historical artifact than a useful facility,
4440 and their use is deprecated; use the expanded syntax instead.
4444 <emphasis>None</> of these metasyntax extensions is available if
4445 an initial <literal>***=</> director
4446 has specified that the user's input be treated as a literal string
4447 rather than as an RE.
4451 <sect3 id="posix-matching-rules">
4452 <title>Regular Expression Matching Rules</title>
4455 In the event that an RE could match more than one substring of a given
4456 string, the RE matches the one starting earliest in the string.
4457 If the RE could match more than one substring starting at that point,
4458 either the longest possible match or the shortest possible match will
4459 be taken, depending on whether the RE is <firstterm>greedy</> or
4460 <firstterm>non-greedy</>.
4464 Whether an RE is greedy or not is determined by the following rules:
4468 Most atoms, and all constraints, have no greediness attribute (because
4469 they cannot match variable amounts of text anyway).
4474 Adding parentheses around an RE does not change its greediness.
4479 A quantified atom with a fixed-repetition quantifier
4480 (<literal>{</><replaceable>m</><literal>}</>
4482 <literal>{</><replaceable>m</><literal>}?</>)
4483 has the same greediness (possibly none) as the atom itself.
4488 A quantified atom with other normal quantifiers (including
4489 <literal>{</><replaceable>m</><literal>,</><replaceable>n</><literal>}</>
4490 with <replaceable>m</> equal to <replaceable>n</>)
4491 is greedy (prefers longest match).
4496 A quantified atom with a non-greedy quantifier (including
4497 <literal>{</><replaceable>m</><literal>,</><replaceable>n</><literal>}?</>
4498 with <replaceable>m</> equal to <replaceable>n</>)
4499 is non-greedy (prefers shortest match).
4504 A branch — that is, an RE that has no top-level
4505 <literal>|</> operator — has the same greediness as the first
4506 quantified atom in it that has a greediness attribute.
4511 An RE consisting of two or more branches connected by the
4512 <literal>|</> operator is always greedy.
4519 The above rules associate greediness attributes not only with individual
4520 quantified atoms, but with branches and entire REs that contain quantified
4521 atoms. What that means is that the matching is done in such a way that
4522 the branch, or whole RE, matches the longest or shortest possible
4523 substring <emphasis>as a whole</>. Once the length of the entire match
4524 is determined, the part of it that matches any particular subexpression
4525 is determined on the basis of the greediness attribute of that
4526 subexpression, with subexpressions starting earlier in the RE taking
4527 priority over ones starting later.
4531 An example of what this means:
4533 SELECT SUBSTRING('XY1234Z', 'Y*([0-9]{1,3})');
4534 <lineannotation>Result: </lineannotation><computeroutput>123</computeroutput>
4535 SELECT SUBSTRING('XY1234Z', 'Y*?([0-9]{1,3})');
4536 <lineannotation>Result: </lineannotation><computeroutput>1</computeroutput>
4538 In the first case, the RE as a whole is greedy because <literal>Y*</>
4539 is greedy. It can match beginning at the <literal>Y</>, and it matches
4540 the longest possible string starting there, i.e., <literal>Y123</>.
4541 The output is the parenthesized part of that, or <literal>123</>.
4542 In the second case, the RE as a whole is non-greedy because <literal>Y*?</>
4543 is non-greedy. It can match beginning at the <literal>Y</>, and it matches
4544 the shortest possible string starting there, i.e., <literal>Y1</>.
4545 The subexpression <literal>[0-9]{1,3}</> is greedy but it cannot change
4546 the decision as to the overall match length; so it is forced to match
4551 In short, when an RE contains both greedy and non-greedy subexpressions,
4552 the total match length is either as long as possible or as short as
4553 possible, according to the attribute assigned to the whole RE. The
4554 attributes assigned to the subexpressions only affect how much of that
4555 match they are allowed to <quote>eat</> relative to each other.
4559 The quantifiers <literal>{1,1}</> and <literal>{1,1}?</>
4560 can be used to force greediness or non-greediness, respectively,
4561 on a subexpression or a whole RE.
4565 Match lengths are measured in characters, not collating elements.
4566 An empty string is considered longer than no match at all.
4569 matches the three middle characters of <literal>abbbc</>;
4570 <literal>(week|wee)(night|knights)</>
4571 matches all ten characters of <literal>weeknights</>;
4572 when <literal>(.*).*</>
4573 is matched against <literal>abc</> the parenthesized subexpression
4574 matches all three characters; and when
4575 <literal>(a*)*</> is matched against <literal>bc</>
4576 both the whole RE and the parenthesized
4577 subexpression match an empty string.
4581 If case-independent matching is specified,
4582 the effect is much as if all case distinctions had vanished from the
4584 When an alphabetic that exists in multiple cases appears as an
4585 ordinary character outside a bracket expression, it is effectively
4586 transformed into a bracket expression containing both cases,
4587 e.g., <literal>x</> becomes <literal>[xX]</>.
4588 When it appears inside a bracket expression, all case counterparts
4589 of it are added to the bracket expression, e.g.,
4590 <literal>[x]</> becomes <literal>[xX]</>
4591 and <literal>[^x]</> becomes <literal>[^xX]</>.
4595 If newline-sensitive matching is specified, <literal>.</>
4596 and bracket expressions using <literal>^</>
4597 will never match the newline character
4598 (so that matches will never cross newlines unless the RE
4599 explicitly arranges it)
4600 and <literal>^</>and <literal>$</>
4601 will match the empty string after and before a newline
4602 respectively, in addition to matching at beginning and end of string
4604 But the ARE escapes <literal>\A</> and <literal>\Z</>
4605 continue to match beginning or end of string <emphasis>only</>.
4609 If partial newline-sensitive matching is specified,
4610 this affects <literal>.</> and bracket expressions
4611 as with newline-sensitive matching, but not <literal>^</>
4616 If inverse partial newline-sensitive matching is specified,
4617 this affects <literal>^</> and <literal>$</>
4618 as with newline-sensitive matching, but not <literal>.</>
4619 and bracket expressions.
4620 This isn't very useful but is provided for symmetry.
4624 <sect3 id="posix-limits-compatibility">
4625 <title>Limits and Compatibility</title>
4628 No particular limit is imposed on the length of REs in this
4629 implementation. However,
4630 programs intended to be highly portable should not employ REs longer
4632 as a POSIX-compliant implementation can refuse to accept such REs.
4636 The only feature of AREs that is actually incompatible with
4637 POSIX EREs is that <literal>\</> does not lose its special
4638 significance inside bracket expressions.
4639 All other ARE features use syntax which is illegal or has
4640 undefined or unspecified effects in POSIX EREs;
4641 the <literal>***</> syntax of directors likewise is outside the POSIX
4642 syntax for both BREs and EREs.
4646 Many of the ARE extensions are borrowed from Perl, but some have
4647 been changed to clean them up, and a few Perl extensions are not present.
4648 Incompatibilities of note include <literal>\b</>, <literal>\B</>,
4649 the lack of special treatment for a trailing newline,
4650 the addition of complemented bracket expressions to the things
4651 affected by newline-sensitive matching,
4652 the restrictions on parentheses and back references in lookahead
4653 constraints, and the longest/shortest-match (rather than first-match)
4658 Two significant incompatibilities exist between AREs and the ERE syntax
4659 recognized by pre-7.4 releases of <productname>PostgreSQL</>:
4664 In AREs, <literal>\</> followed by an alphanumeric character is either
4665 an escape or an error, while in previous releases, it was just another
4666 way of writing the alphanumeric.
4667 This should not be much of a problem because there was no reason to
4668 write such a sequence in earlier releases.
4673 In AREs, <literal>\</> remains a special character within
4674 <literal>[]</>, so a literal <literal>\</> within a bracket
4675 expression must be written <literal>\\</>.
4680 While these differences are unlikely to create a problem for most
4681 applications, you can avoid them if necessary by
4682 setting <varname>regex_flavor</> to <literal>extended</>.
4686 <sect3 id="posix-basic-regexes">
4687 <title>Basic Regular Expressions</title>
4690 BREs differ from EREs in several respects.
4691 In BREs, <literal>|</>, <literal>+</>, and <literal>?</>
4692 are ordinary characters and there is no equivalent
4693 for their functionality.
4694 The delimiters for bounds are
4695 <literal>\{</> and <literal>\}</>,
4696 with <literal>{</> and <literal>}</>
4697 by themselves ordinary characters.
4698 The parentheses for nested subexpressions are
4699 <literal>\(</> and <literal>\)</>,
4700 with <literal>(</> and <literal>)</> by themselves ordinary characters.
4701 <literal>^</> is an ordinary character except at the beginning of the
4702 RE or the beginning of a parenthesized subexpression,
4703 <literal>$</> is an ordinary character except at the end of the
4704 RE or the end of a parenthesized subexpression,
4705 and <literal>*</> is an ordinary character if it appears at the beginning
4706 of the RE or the beginning of a parenthesized subexpression
4707 (after a possible leading <literal>^</>).
4708 Finally, single-digit back references are available, and
4709 <literal>\<</> and <literal>\></>
4711 <literal>[[:<:]]</> and <literal>[[:>:]]</>
4712 respectively; no other escapes are available in BREs.
4716 <!-- end re_syntax.n man page -->
4722 <sect1 id="functions-formatting">
4723 <title>Data Type Formatting Functions</title>
4726 <primary>formatting</primary>
4730 <primary>to_char</primary>
4733 <primary>to_date</primary>
4736 <primary>to_number</primary>
4739 <primary>to_timestamp</primary>
4743 The <productname>PostgreSQL</productname> formatting functions
4744 provide a powerful set of tools for converting various data types
4745 (date/time, integer, floating point, numeric) to formatted strings
4746 and for converting from formatted strings to specific data types.
4747 <xref linkend="functions-formatting-table"> lists them.
4748 These functions all follow a common calling convention: the first
4749 argument is the value to be formatted and the second argument is a
4750 template that defines the output or input format.
4753 A single-argument <function>to_timestamp</function> function is also
4754 available; it accepts a
4755 <type>double precision</type> argument and converts from Unix epoch
4756 (seconds since 1970-01-01 00:00:00+00) to
4757 <type>timestamp with time zone</type>.
4758 (<type>Integer</type> Unix epochs are implicitly cast to
4759 <type>double precision</type>.)
4762 <table id="functions-formatting-table">
4763 <title>Formatting Functions</title>
4767 <entry>Function</entry>
4768 <entry>Return Type</entry>
4769 <entry>Description</entry>
4770 <entry>Example</entry>
4775 <entry><literal><function>to_char</function>(<type>timestamp</type>, <type>text</type>)</literal></entry>
4776 <entry><type>text</type></entry>
4777 <entry>convert time stamp to string</entry>
4778 <entry><literal>to_char(current_timestamp, 'HH12:MI:SS')</literal></entry>
4781 <entry><literal><function>to_char</function>(<type>interval</type>, <type>text</type>)</literal></entry>
4782 <entry><type>text</type></entry>
4783 <entry>convert interval to string</entry>
4784 <entry><literal>to_char(interval '15h 2m 12s', 'HH24:MI:SS')</literal></entry>
4787 <entry><literal><function>to_char</function>(<type>int</type>, <type>text</type>)</literal></entry>
4788 <entry><type>text</type></entry>
4789 <entry>convert integer to string</entry>
4790 <entry><literal>to_char(125, '999')</literal></entry>
4793 <entry><literal><function>to_char</function>(<type>double precision</type>,
4794 <type>text</type>)</literal></entry>
4795 <entry><type>text</type></entry>
4796 <entry>convert real/double precision to string</entry>
4797 <entry><literal>to_char(125.8::real, '999D9')</literal></entry>
4800 <entry><literal><function>to_char</function>(<type>numeric</type>, <type>text</type>)</literal></entry>
4801 <entry><type>text</type></entry>
4802 <entry>convert numeric to string</entry>
4803 <entry><literal>to_char(-125.8, '999D99S')</literal></entry>
4806 <entry><literal><function>to_date</function>(<type>text</type>, <type>text</type>)</literal></entry>
4807 <entry><type>date</type></entry>
4808 <entry>convert string to date</entry>
4809 <entry><literal>to_date('05 Dec 2000', 'DD Mon YYYY')</literal></entry>
4812 <entry><literal><function>to_number</function>(<type>text</type>, <type>text</type>)</literal></entry>
4813 <entry><type>numeric</type></entry>
4814 <entry>convert string to numeric</entry>
4815 <entry><literal>to_number('12,454.8-', '99G999D9S')</literal></entry>
4818 <entry><literal><function>to_timestamp</function>(<type>text</type>, <type>text</type>)</literal></entry>
4819 <entry><type>timestamp with time zone</type></entry>
4820 <entry>convert string to time stamp</entry>
4821 <entry><literal>to_timestamp('05 Dec 2000', 'DD Mon YYYY')</literal></entry>
4824 <entry><literal><function>to_timestamp</function>(<type>double precision</type>)</literal></entry>
4825 <entry><type>timestamp with time zone</type></entry>
4826 <entry>convert Unix epoch to time stamp</entry>
4827 <entry><literal>to_timestamp(1284352323)</literal></entry>
4834 In a <function>to_char</> output template string, there are certain
4835 patterns that are recognized and replaced with appropriately-formatted
4836 data based on the given value. Any text that is not a template pattern is
4837 simply copied verbatim. Similarly, in an input template string (for the
4838 other functions), template patterns identify the values to be supplied by
4839 the input data string.
4843 <xref linkend="functions-formatting-datetime-table"> shows the
4844 template patterns available for formatting date and time values.
4847 <table id="functions-formatting-datetime-table">
4848 <title>Template Patterns for Date/Time Formatting</title>
4852 <entry>Pattern</entry>
4853 <entry>Description</entry>
4858 <entry><literal>HH</literal></entry>
4859 <entry>hour of day (01-12)</entry>
4862 <entry><literal>HH12</literal></entry>
4863 <entry>hour of day (01-12)</entry>
4866 <entry><literal>HH24</literal></entry>
4867 <entry>hour of day (00-23)</entry>
4870 <entry><literal>MI</literal></entry>
4871 <entry>minute (00-59)</entry>
4874 <entry><literal>SS</literal></entry>
4875 <entry>second (00-59)</entry>
4878 <entry><literal>MS</literal></entry>
4879 <entry>millisecond (000-999)</entry>
4882 <entry><literal>US</literal></entry>
4883 <entry>microsecond (000000-999999)</entry>
4886 <entry><literal>SSSS</literal></entry>
4887 <entry>seconds past midnight (0-86399)</entry>
4890 <entry><literal>AM</literal>, <literal>am</literal>,
4891 <literal>PM</literal> or <literal>pm</literal></entry>
4892 <entry>meridiem indicator (without periods)</entry>
4895 <entry><literal>A.M.</literal>, <literal>a.m.</literal>,
4896 <literal>P.M.</literal> or <literal>p.m.</literal></entry>
4897 <entry>meridiem indicator (with periods)</entry>
4900 <entry><literal>Y,YYY</literal></entry>
4901 <entry>year (4 and more digits) with comma</entry>
4904 <entry><literal>YYYY</literal></entry>
4905 <entry>year (4 and more digits)</entry>
4908 <entry><literal>YYY</literal></entry>
4909 <entry>last 3 digits of year</entry>
4912 <entry><literal>YY</literal></entry>
4913 <entry>last 2 digits of year</entry>
4916 <entry><literal>Y</literal></entry>
4917 <entry>last digit of year</entry>
4920 <entry><literal>IYYY</literal></entry>
4921 <entry>ISO year (4 and more digits)</entry>
4924 <entry><literal>IYY</literal></entry>
4925 <entry>last 3 digits of ISO year</entry>
4928 <entry><literal>IY</literal></entry>
4929 <entry>last 2 digits of ISO year</entry>
4932 <entry><literal>I</literal></entry>
4933 <entry>last digit of ISO year</entry>
4936 <entry><literal>BC</literal>, <literal>bc</literal>,
4937 <literal>AD</literal> or <literal>ad</literal></entry>
4938 <entry>era indicator (without periods)</entry>
4941 <entry><literal>B.C.</literal>, <literal>b.c.</literal>,
4942 <literal>A.D.</literal> or <literal>a.d.</literal></entry>
4943 <entry>era indicator (with periods)</entry>
4946 <entry><literal>MONTH</literal></entry>
4947 <entry>full uppercase month name (blank-padded to 9 chars)</entry>
4950 <entry><literal>Month</literal></entry>
4951 <entry>full capitalized month name (blank-padded to 9 chars)</entry>
4954 <entry><literal>month</literal></entry>
4955 <entry>full lowercase month name (blank-padded to 9 chars)</entry>
4958 <entry><literal>MON</literal></entry>
4959 <entry>abbreviated uppercase month name (3 chars in English, localized lengths vary)</entry>
4962 <entry><literal>Mon</literal></entry>
4963 <entry>abbreviated capitalized month name (3 chars in English, localized lengths vary)</entry>
4966 <entry><literal>mon</literal></entry>
4967 <entry>abbreviated lowercase month name (3 chars in English, localized lengths vary)</entry>
4970 <entry><literal>MM</literal></entry>
4971 <entry>month number (01-12)</entry>
4974 <entry><literal>DAY</literal></entry>
4975 <entry>full uppercase day name (blank-padded to 9 chars)</entry>
4978 <entry><literal>Day</literal></entry>
4979 <entry>full capitalized day name (blank-padded to 9 chars)</entry>
4982 <entry><literal>day</literal></entry>
4983 <entry>full lowercase day name (blank-padded to 9 chars)</entry>
4986 <entry><literal>DY</literal></entry>
4987 <entry>abbreviated uppercase day name (3 chars in English, localized lengths vary)</entry>
4990 <entry><literal>Dy</literal></entry>
4991 <entry>abbreviated capitalized day name (3 chars in English, localized lengths vary)</entry>
4994 <entry><literal>dy</literal></entry>
4995 <entry>abbreviated lowercase day name (3 chars in English, localized lengths vary)</entry>
4998 <entry><literal>DDD</literal></entry>
4999 <entry>day of year (001-366)</entry>
5002 <entry><literal>IDDD</literal></entry>
5003 <entry>ISO day of year (001-371; day 1 of the year is Monday of the first ISO week.)</entry>
5006 <entry><literal>DD</literal></entry>
5007 <entry>day of month (01-31)</entry>
5010 <entry><literal>D</literal></entry>
5011 <entry>day of the week, Sunday(<literal>1</>) to Saturday(<literal>7</>)</entry>
5014 <entry><literal>ID</literal></entry>
5015 <entry>ISO day of the week, Monday(<literal>1</>) to Sunday(<literal>7</>)</entry>
5018 <entry><literal>W</literal></entry>
5019 <entry>week of month (1-5) (The first week starts on the first day of the month.)</entry>
5022 <entry><literal>WW</literal></entry>
5023 <entry>week number of year (1-53) (The first week starts on the first day of the year.)</entry>
5026 <entry><literal>IW</literal></entry>
5027 <entry>ISO week number of year (01 - 53; the first Thursday of the new year is in week 1.)</entry>
5030 <entry><literal>CC</literal></entry>
5031 <entry>century (2 digits) (The twenty-first century starts on 2001-01-01.)</entry>
5034 <entry><literal>J</literal></entry>
5035 <entry>Julian Day (days since November 24, 4714 BC at midnight)</entry>
5038 <entry><literal>Q</literal></entry>
5039 <entry>quarter</entry>
5042 <entry><literal>RM</literal></entry>
5043 <entry>month in uppercase Roman numerals (I-XII; I=January)</entry>
5046 <entry><literal>rm</literal></entry>
5047 <entry>month in lowercase Roman numerals (i-xii; i=January)</entry>
5050 <entry><literal>TZ</literal></entry>
5051 <entry>uppercase time-zone name</entry>
5054 <entry><literal>tz</literal></entry>
5055 <entry>lowercase time-zone name</entry>
5062 Modifiers can be applied to any template pattern to alter its
5063 behavior. For example, <literal>FMMonth</literal>
5064 is the <literal>Month</literal> pattern with the
5065 <literal>FM</literal> modifier.
5066 <xref linkend="functions-formatting-datetimemod-table"> shows the
5067 modifier patterns for date/time formatting.
5070 <table id="functions-formatting-datetimemod-table">
5071 <title>Template Pattern Modifiers for Date/Time Formatting</title>
5075 <entry>Modifier</entry>
5076 <entry>Description</entry>
5077 <entry>Example</entry>
5082 <entry><literal>FM</literal> prefix</entry>
5083 <entry>fill mode (suppress padding blanks and zeroes)</entry>
5084 <entry><literal>FMMonth</literal></entry>
5087 <entry><literal>TH</literal> suffix</entry>
5088 <entry>uppercase ordinal number suffix</entry>
5089 <entry><literal>DDTH</literal>, e.g., <literal>12TH</></entry>
5092 <entry><literal>th</literal> suffix</entry>
5093 <entry>lowercase ordinal number suffix</entry>
5094 <entry><literal>DDth</literal>, e.g., <literal>12th</></entry>
5097 <entry><literal>FX</literal> prefix</entry>
5098 <entry>fixed format global option (see usage notes)</entry>
5099 <entry><literal>FX Month DD Day</literal></entry>
5102 <entry><literal>TM</literal> prefix</entry>
5103 <entry>translation mode (print localized day and month names based on
5104 <xref linkend="guc-lc-time">)</entry>
5105 <entry><literal>TMMonth</literal></entry>
5108 <entry><literal>SP</literal> suffix</entry>
5109 <entry>spell mode (not implemented)</entry>
5110 <entry><literal>DDSP</literal></entry>
5117 Usage notes for date/time formatting:
5122 <literal>FM</literal> suppresses leading zeroes and trailing blanks
5123 that would otherwise be added to make the output of a pattern be
5130 <literal>TM</literal> does not include trailing blanks.
5136 <function>to_timestamp</function> and <function>to_date</function>
5137 skip multiple blank spaces in the input string unless the
5138 <literal>FX</literal> option is used. For example,
5139 <literal>to_timestamp('2000 JUN', 'YYYY MON')</literal> works, but
5140 <literal>to_timestamp('2000 JUN', 'FXYYYY MON')</literal> returns an error
5141 because <function>to_timestamp</function> expects one space only.
5142 <literal>FX</literal> must be specified as the first item in
5149 Ordinary text is allowed in <function>to_char</function>
5150 templates and will be output literally. You can put a substring
5151 in double quotes to force it to be interpreted as literal text
5152 even if it contains pattern key words. For example, in
5153 <literal>'"Hello Year "YYYY'</literal>, the <literal>YYYY</literal>
5154 will be replaced by the year data, but the single <literal>Y</literal> in <literal>Year</literal>
5161 If you want to have a double quote in the output you must
5162 precede it with a backslash, for example <literal>E'\\"YYYY
5163 Month\\"'</literal>. <!-- "" font-lock sanity :-) -->
5164 (Two backslashes are necessary because the backslash
5165 has special meaning when using the escape string syntax.)
5171 The <literal>YYYY</literal> conversion from string to <type>timestamp</type> or
5172 <type>date</type> has a restriction when processing years with more than 4 digits. You must
5173 use some non-digit character or template after <literal>YYYY</literal>,
5174 otherwise the year is always interpreted as 4 digits. For example
5175 (with the year 20000):
5176 <literal>to_date('200001131', 'YYYYMMDD')</literal> will be
5177 interpreted as a 4-digit year; instead use a non-digit
5178 separator after the year, like
5179 <literal>to_date('20000-1131', 'YYYY-MMDD')</literal> or
5180 <literal>to_date('20000Nov31', 'YYYYMonDD')</literal>.
5186 In conversions from string to <type>timestamp</type> or
5187 <type>date</type>, the <literal>CC</literal> (century) field is ignored
5188 if there is a <literal>YYY</literal>, <literal>YYYY</literal> or
5189 <literal>Y,YYY</literal> field. If <literal>CC</literal> is used with
5190 <literal>YY</literal> or <literal>Y</literal> then the year is computed
5191 as <literal>(CC-1)*100+YY</literal>.
5197 An ISO week date (as distinct from a Gregorian date) can be
5198 specified to <function>to_timestamp</function> and
5199 <function>to_date</function> in one of two ways:
5203 Year, week, and weekday: for example <literal>to_date('2006-42-4',
5204 'IYYY-IW-ID')</literal> returns the date
5205 <literal>2006-10-19</literal>. If you omit the weekday it
5206 is assumed to be 1 (Monday).
5211 Year and day of year: for example <literal>to_date('2006-291',
5212 'IYYY-IDDD')</literal> also returns <literal>2006-10-19</literal>.
5218 Attempting to construct a date using a mixture of ISO week and
5219 Gregorian date fields is nonsensical, and will cause an error. In the
5220 context of an ISO year, the concept of a <quote>month</> or <quote>day
5221 of month</> has no meaning. In the context of a Gregorian year, the
5222 ISO week has no meaning. Users should avoid mixing Gregorian and
5223 ISO date specifications.
5229 In a conversion from string to <type>timestamp</type>, millisecond
5230 (<literal>MS</literal>) or microsecond (<literal>US</literal>)
5231 values are used as the
5232 seconds digits after the decimal point. For example
5233 <literal>to_timestamp('12:3', 'SS:MS')</literal> is not 3 milliseconds,
5234 but 300, because the conversion counts it as 12 + 0.3 seconds.
5235 This means for the format <literal>SS:MS</literal>, the input values
5236 <literal>12:3</literal>, <literal>12:30</literal>, and <literal>12:300</literal> specify the
5237 same number of milliseconds. To get three milliseconds, one must use
5238 <literal>12:003</literal>, which the conversion counts as
5239 12 + 0.003 = 12.003 seconds.
5245 <literal>to_timestamp('15:12:02.020.001230', 'HH:MI:SS.MS.US')</literal>
5246 is 15 hours, 12 minutes, and 2 seconds + 20 milliseconds +
5247 1230 microseconds = 2.021230 seconds.
5253 <function>to_char(..., 'ID')</function>'s day of the week numbering
5254 matches the <function>extract('isodow', ...)</function> function, but
5255 <function>to_char(..., 'D')</function>'s does not match
5256 <function>extract('dow', ...)</function>'s day numbering.
5262 <function>to_char(interval)</function> formats <literal>HH</> and
5263 <literal>HH12</> as hours in a single day, while <literal>HH24</>
5264 can output hours exceeding a single day, e.g., >24.
5272 <xref linkend="functions-formatting-numeric-table"> shows the
5273 template patterns available for formatting numeric values.
5276 <table id="functions-formatting-numeric-table">
5277 <title>Template Patterns for Numeric Formatting</title>
5281 <entry>Pattern</entry>
5282 <entry>Description</entry>
5287 <entry><literal>9</literal></entry>
5288 <entry>value with the specified number of digits</entry>
5291 <entry><literal>0</literal></entry>
5292 <entry>value with leading zeros</entry>
5295 <entry><literal>.</literal> (period)</entry>
5296 <entry>decimal point</entry>
5299 <entry><literal>,</literal> (comma)</entry>
5300 <entry>group (thousand) separator</entry>
5303 <entry><literal>PR</literal></entry>
5304 <entry>negative value in angle brackets</entry>
5307 <entry><literal>S</literal></entry>
5308 <entry>sign anchored to number (uses locale)</entry>
5311 <entry><literal>L</literal></entry>
5312 <entry>currency symbol (uses locale)</entry>
5315 <entry><literal>D</literal></entry>
5316 <entry>decimal point (uses locale)</entry>
5319 <entry><literal>G</literal></entry>
5320 <entry>group separator (uses locale)</entry>
5323 <entry><literal>MI</literal></entry>
5324 <entry>minus sign in specified position (if number < 0)</entry>
5327 <entry><literal>PL</literal></entry>
5328 <entry>plus sign in specified position (if number > 0)</entry>
5331 <entry><literal>SG</literal></entry>
5332 <entry>plus/minus sign in specified position</entry>
5335 <entry><literal>RN</literal></entry>
5336 <entry>Roman numeral (input between 1 and 3999)</entry>
5339 <entry><literal>TH</literal> or <literal>th</literal></entry>
5340 <entry>ordinal number suffix</entry>
5343 <entry><literal>V</literal></entry>
5344 <entry>shift specified number of digits (see notes)</entry>
5347 <entry><literal>EEEE</literal></entry>
5348 <entry>exponent for scientific notation</entry>
5355 Usage notes for numeric formatting:
5360 A sign formatted using <literal>SG</literal>, <literal>PL</literal>, or
5361 <literal>MI</literal> is not anchored to
5362 the number; for example,
5363 <literal>to_char(-12, 'MI9999')</literal> produces <literal>'- 12'</literal>
5364 but <literal>to_char(-12, 'S9999')</literal> produces <literal>' -12'</literal>.
5365 The Oracle implementation does not allow the use of
5366 <literal>MI</literal> before <literal>9</literal>, but rather
5367 requires that <literal>9</literal> precede
5368 <literal>MI</literal>.
5374 <literal>9</literal> results in a value with the same number of
5375 digits as there are <literal>9</literal>s. If a digit is
5376 not available it outputs a space.
5382 <literal>TH</literal> does not convert values less than zero
5383 and does not convert fractional numbers.
5389 <literal>PL</literal>, <literal>SG</literal>, and
5390 <literal>TH</literal> are <productname>PostgreSQL</productname>
5397 <literal>V</literal> effectively
5398 multiplies the input values by
5399 <literal>10^<replaceable>n</replaceable></literal>, where
5400 <replaceable>n</replaceable> is the number of digits following
5401 <literal>V</literal>.
5402 <function>to_char</function> does not support the use of
5403 <literal>V</literal> combined with a decimal point
5404 (e.g., <literal>99.9V99</literal> is not allowed).
5410 <literal>EEEE</literal> (scientific notation) cannot be used in
5411 combination with any of the other special formatting patterns or
5412 modifiers, and must be at the end of the format string
5413 (e.g., <literal>9.99EEEE</literal> is a valid pattern).
5420 Certain modifiers can be applied to any template pattern to alter its
5421 behavior. For example, <literal>FM9999</literal>
5422 is the <literal>9999</literal> pattern with the
5423 <literal>FM</literal> modifier.
5424 <xref linkend="functions-formatting-numericmod-table"> shows the
5425 modifier patterns for numeric formatting.
5428 <table id="functions-formatting-numericmod-table">
5429 <title>Template Pattern Modifiers for Numeric Formatting</title>
5433 <entry>Modifier</entry>
5434 <entry>Description</entry>
5435 <entry>Example</entry>
5440 <entry><literal>FM</literal> prefix</entry>
5441 <entry>fill mode (suppress padding blanks and zeroes)</entry>
5442 <entry><literal>FM9999</literal></entry>
5445 <entry><literal>TH</literal> suffix</entry>
5446 <entry>uppercase ordinal number suffix</entry>
5447 <entry><literal>999TH</literal></entry>
5450 <entry><literal>th</literal> suffix</entry>
5451 <entry>lowercase ordinal number suffix</entry>
5452 <entry><literal>999th</literal></entry>
5459 <xref linkend="functions-formatting-examples-table"> shows some
5460 examples of the use of the <function>to_char</function> function.
5463 <table id="functions-formatting-examples-table">
5464 <title><function>to_char</function> Examples</title>
5468 <entry>Expression</entry>
5469 <entry>Result</entry>
5474 <entry><literal>to_char(current_timestamp, 'Day, DD HH12:MI:SS')</literal></entry>
5475 <entry><literal>'Tuesday , 06 05:39:18'</literal></entry>
5478 <entry><literal>to_char(current_timestamp, 'FMDay, FMDD HH12:MI:SS')</literal></entry>
5479 <entry><literal>'Tuesday, 6 05:39:18'</literal></entry>
5482 <entry><literal>to_char(-0.1, '99.99')</literal></entry>
5483 <entry><literal>' -.10'</literal></entry>
5486 <entry><literal>to_char(-0.1, 'FM9.99')</literal></entry>
5487 <entry><literal>'-.1'</literal></entry>
5490 <entry><literal>to_char(0.1, '0.9')</literal></entry>
5491 <entry><literal>' 0.1'</literal></entry>
5494 <entry><literal>to_char(12, '9990999.9')</literal></entry>
5495 <entry><literal>' 0012.0'</literal></entry>
5498 <entry><literal>to_char(12, 'FM9990999.9')</literal></entry>
5499 <entry><literal>'0012.'</literal></entry>
5502 <entry><literal>to_char(485, '999')</literal></entry>
5503 <entry><literal>' 485'</literal></entry>
5506 <entry><literal>to_char(-485, '999')</literal></entry>
5507 <entry><literal>'-485'</literal></entry>
5510 <entry><literal>to_char(485, '9 9 9')</literal></entry>
5511 <entry><literal>' 4 8 5'</literal></entry>
5514 <entry><literal>to_char(1485, '9,999')</literal></entry>
5515 <entry><literal>' 1,485'</literal></entry>
5518 <entry><literal>to_char(1485, '9G999')</literal></entry>
5519 <entry><literal>' 1 485'</literal></entry>
5522 <entry><literal>to_char(148.5, '999.999')</literal></entry>
5523 <entry><literal>' 148.500'</literal></entry>
5526 <entry><literal>to_char(148.5, 'FM999.999')</literal></entry>
5527 <entry><literal>'148.5'</literal></entry>
5530 <entry><literal>to_char(148.5, 'FM999.990')</literal></entry>
5531 <entry><literal>'148.500'</literal></entry>
5534 <entry><literal>to_char(148.5, '999D999')</literal></entry>
5535 <entry><literal>' 148,500'</literal></entry>
5538 <entry><literal>to_char(3148.5, '9G999D999')</literal></entry>
5539 <entry><literal>' 3 148,500'</literal></entry>
5542 <entry><literal>to_char(-485, '999S')</literal></entry>
5543 <entry><literal>'485-'</literal></entry>
5546 <entry><literal>to_char(-485, '999MI')</literal></entry>
5547 <entry><literal>'485-'</literal></entry>
5550 <entry><literal>to_char(485, '999MI')</literal></entry>
5551 <entry><literal>'485 '</literal></entry>
5554 <entry><literal>to_char(485, 'FM999MI')</literal></entry>
5555 <entry><literal>'485'</literal></entry>
5558 <entry><literal>to_char(485, 'PL999')</literal></entry>
5559 <entry><literal>'+485'</literal></entry>
5562 <entry><literal>to_char(485, 'SG999')</literal></entry>
5563 <entry><literal>'+485'</literal></entry>
5566 <entry><literal>to_char(-485, 'SG999')</literal></entry>
5567 <entry><literal>'-485'</literal></entry>
5570 <entry><literal>to_char(-485, '9SG99')</literal></entry>
5571 <entry><literal>'4-85'</literal></entry>
5574 <entry><literal>to_char(-485, '999PR')</literal></entry>
5575 <entry><literal>'<485>'</literal></entry>
5578 <entry><literal>to_char(485, 'L999')</literal></entry>
5579 <entry><literal>'DM 485</literal></entry>
5582 <entry><literal>to_char(485, 'RN')</literal></entry>
5583 <entry><literal>' CDLXXXV'</literal></entry>
5586 <entry><literal>to_char(485, 'FMRN')</literal></entry>
5587 <entry><literal>'CDLXXXV'</literal></entry>
5590 <entry><literal>to_char(5.2, 'FMRN')</literal></entry>
5591 <entry><literal>'V'</literal></entry>
5594 <entry><literal>to_char(482, '999th')</literal></entry>
5595 <entry><literal>' 482nd'</literal></entry>
5598 <entry><literal>to_char(485, '"Good number:"999')</literal></entry>
5599 <entry><literal>'Good number: 485'</literal></entry>
5602 <entry><literal>to_char(485.8, '"Pre:"999" Post:" .999')</literal></entry>
5603 <entry><literal>'Pre: 485 Post: .800'</literal></entry>
5606 <entry><literal>to_char(12, '99V999')</literal></entry>
5607 <entry><literal>' 12000'</literal></entry>
5610 <entry><literal>to_char(12.4, '99V999')</literal></entry>
5611 <entry><literal>' 12400'</literal></entry>
5614 <entry><literal>to_char(12.45, '99V9')</literal></entry>
5615 <entry><literal>' 125'</literal></entry>
5618 <entry><literal>to_char(0.0004859, '9.99EEEE')</literal></entry>
5619 <entry><literal>' 4.86e-04'</literal></entry>
5628 <sect1 id="functions-datetime">
5629 <title>Date/Time Functions and Operators</title>
5632 <xref linkend="functions-datetime-table"> shows the available
5633 functions for date/time value processing, with details appearing in
5634 the following subsections. <xref
5635 linkend="operators-datetime-table"> illustrates the behaviors of
5636 the basic arithmetic operators (<literal>+</literal>,
5637 <literal>*</literal>, etc.). For formatting functions, refer to
5638 <xref linkend="functions-formatting">. You should be familiar with
5639 the background information on date/time data types from <xref
5640 linkend="datatype-datetime">.
5644 All the functions and operators described below that take <type>time</type> or <type>timestamp</type>
5645 inputs actually come in two variants: one that takes <type>time with time zone</type> or <type>timestamp
5646 with time zone</type>, and one that takes <type>time without time zone</type> or <type>timestamp without time zone</type>.
5647 For brevity, these variants are not shown separately. Also, the
5648 <literal>+</> and <literal>*</> operators come in commutative pairs (for
5649 example both date + integer and integer + date); we show only one of each
5653 <table id="operators-datetime-table">
5654 <title>Date/Time Operators</title>
5659 <entry>Operator</entry>
5660 <entry>Example</entry>
5661 <entry>Result</entry>
5667 <entry> <literal>+</literal> </entry>
5668 <entry><literal>date '2001-09-28' + integer '7'</literal></entry>
5669 <entry><literal>date '2001-10-05'</literal></entry>
5673 <entry> <literal>+</literal> </entry>
5674 <entry><literal>date '2001-09-28' + interval '1 hour'</literal></entry>
5675 <entry><literal>timestamp '2001-09-28 01:00:00'</literal></entry>
5679 <entry> <literal>+</literal> </entry>
5680 <entry><literal>date '2001-09-28' + time '03:00'</literal></entry>
5681 <entry><literal>timestamp '2001-09-28 03:00:00'</literal></entry>
5685 <entry> <literal>+</literal> </entry>
5686 <entry><literal>interval '1 day' + interval '1 hour'</literal></entry>
5687 <entry><literal>interval '1 day 01:00:00'</literal></entry>
5691 <entry> <literal>+</literal> </entry>
5692 <entry><literal>timestamp '2001-09-28 01:00' + interval '23 hours'</literal></entry>
5693 <entry><literal>timestamp '2001-09-29 00:00:00'</literal></entry>
5697 <entry> <literal>+</literal> </entry>
5698 <entry><literal>time '01:00' + interval '3 hours'</literal></entry>
5699 <entry><literal>time '04:00:00'</literal></entry>
5703 <entry> <literal>-</literal> </entry>
5704 <entry><literal>- interval '23 hours'</literal></entry>
5705 <entry><literal>interval '-23:00:00'</literal></entry>
5709 <entry> <literal>-</literal> </entry>
5710 <entry><literal>date '2001-10-01' - date '2001-09-28'</literal></entry>
5711 <entry><literal>integer '3'</literal> (days)</entry>
5715 <entry> <literal>-</literal> </entry>
5716 <entry><literal>date '2001-10-01' - integer '7'</literal></entry>
5717 <entry><literal>date '2001-09-24'</literal></entry>
5721 <entry> <literal>-</literal> </entry>
5722 <entry><literal>date '2001-09-28' - interval '1 hour'</literal></entry>
5723 <entry><literal>timestamp '2001-09-27 23:00:00'</literal></entry>
5727 <entry> <literal>-</literal> </entry>
5728 <entry><literal>time '05:00' - time '03:00'</literal></entry>
5729 <entry><literal>interval '02:00:00'</literal></entry>
5733 <entry> <literal>-</literal> </entry>
5734 <entry><literal>time '05:00' - interval '2 hours'</literal></entry>
5735 <entry><literal>time '03:00:00'</literal></entry>
5739 <entry> <literal>-</literal> </entry>
5740 <entry><literal>timestamp '2001-09-28 23:00' - interval '23 hours'</literal></entry>
5741 <entry><literal>timestamp '2001-09-28 00:00:00'</literal></entry>
5745 <entry> <literal>-</literal> </entry>
5746 <entry><literal>interval '1 day' - interval '1 hour'</literal></entry>
5747 <entry><literal>interval '1 day -01:00:00'</literal></entry>
5751 <entry> <literal>-</literal> </entry>
5752 <entry><literal>timestamp '2001-09-29 03:00' - timestamp '2001-09-27 12:00'</literal></entry>
5753 <entry><literal>interval '1 day 15:00:00'</literal></entry>
5757 <entry> <literal>*</literal> </entry>
5758 <entry><literal>900 * interval '1 second'</literal></entry>
5759 <entry><literal>interval '00:15:00'</literal></entry>
5763 <entry> <literal>*</literal> </entry>
5764 <entry><literal>21 * interval '1 day'</literal></entry>
5765 <entry><literal>interval '21 days'</literal></entry>
5769 <entry> <literal>*</literal> </entry>
5770 <entry><literal>double precision '3.5' * interval '1 hour'</literal></entry>
5771 <entry><literal>interval '03:30:00'</literal></entry>
5775 <entry> <literal>/</literal> </entry>
5776 <entry><literal>interval '1 hour' / double precision '1.5'</literal></entry>
5777 <entry><literal>interval '00:40:00'</literal></entry>
5784 <primary>age</primary>
5787 <primary>clock_timestamp</primary>
5790 <primary>current_date</primary>
5793 <primary>current_time</primary>
5796 <primary>current_timestamp</primary>
5799 <primary>date_part</primary>
5802 <primary>date_trunc</primary>
5805 <primary>extract</primary>
5808 <primary>isfinite</primary>
5811 <primary>justify_days</primary>
5814 <primary>justify_hours</primary>
5817 <primary>justify_interval</primary>
5820 <primary>localtime</primary>
5823 <primary>localtimestamp</primary>
5826 <primary>now</primary>
5829 <primary>statement_timestamp</primary>
5832 <primary>timeofday</primary>
5835 <primary>transaction_timestamp</primary>
5838 <table id="functions-datetime-table">
5839 <title>Date/Time Functions</title>
5843 <entry>Function</entry>
5844 <entry>Return Type</entry>
5845 <entry>Description</entry>
5846 <entry>Example</entry>
5847 <entry>Result</entry>
5853 <entry><literal><function>age</function>(<type>timestamp</type>, <type>timestamp</type>)</literal></entry>
5854 <entry><type>interval</type></entry>
5855 <entry>Subtract arguments, producing a <quote>symbolic</> result that
5856 uses years and months</entry>
5857 <entry><literal>age(timestamp '2001-04-10', timestamp '1957-06-13')</literal></entry>
5858 <entry><literal>43 years 9 mons 27 days</literal></entry>
5862 <entry><literal><function>age</function>(<type>timestamp</type>)</literal></entry>
5863 <entry><type>interval</type></entry>
5864 <entry>Subtract from <function>current_date</function> (at midnight)</entry>
5865 <entry><literal>age(timestamp '1957-06-13')</literal></entry>
5866 <entry><literal>43 years 8 mons 3 days</literal></entry>
5870 <entry><literal><function>clock_timestamp</function>()</literal></entry>
5871 <entry><type>timestamp with time zone</type></entry>
5872 <entry>Current date and time (changes during statement execution);
5873 see <xref linkend="functions-datetime-current">
5880 <entry><literal><function>current_date</function></literal></entry>
5881 <entry><type>date</type></entry>
5882 <entry>Current date;
5883 see <xref linkend="functions-datetime-current">
5890 <entry><literal><function>current_time</function></literal></entry>
5891 <entry><type>time with time zone</type></entry>
5892 <entry>Current time of day;
5893 see <xref linkend="functions-datetime-current">
5900 <entry><literal><function>current_timestamp</function></literal></entry>
5901 <entry><type>timestamp with time zone</type></entry>
5902 <entry>Current date and time (start of current transaction);
5903 see <xref linkend="functions-datetime-current">
5910 <entry><literal><function>date_part</function>(<type>text</type>, <type>timestamp</type>)</literal></entry>
5911 <entry><type>double precision</type></entry>
5912 <entry>Get subfield (equivalent to <function>extract</function>);
5913 see <xref linkend="functions-datetime-extract">
5915 <entry><literal>date_part('hour', timestamp '2001-02-16 20:38:40')</literal></entry>
5916 <entry><literal>20</literal></entry>
5920 <entry><literal><function>date_part</function>(<type>text</type>, <type>interval</type>)</literal></entry>
5921 <entry><type>double precision</type></entry>
5922 <entry>Get subfield (equivalent to
5923 <function>extract</function>); see <xref linkend="functions-datetime-extract">
5925 <entry><literal>date_part('month', interval '2 years 3 months')</literal></entry>
5926 <entry><literal>3</literal></entry>
5930 <entry><literal><function>date_trunc</function>(<type>text</type>, <type>timestamp</type>)</literal></entry>
5931 <entry><type>timestamp</type></entry>
5932 <entry>Truncate to specified precision; see also <xref linkend="functions-datetime-trunc">
5934 <entry><literal>date_trunc('hour', timestamp '2001-02-16 20:38:40')</literal></entry>
5935 <entry><literal>2001-02-16 20:00:00</literal></entry>
5939 <entry><literal><function>extract</function>(<parameter>field</parameter> from
5940 <type>timestamp</type>)</literal></entry>
5941 <entry><type>double precision</type></entry>
5942 <entry>Get subfield; see <xref linkend="functions-datetime-extract">
5944 <entry><literal>extract(hour from timestamp '2001-02-16 20:38:40')</literal></entry>
5945 <entry><literal>20</literal></entry>
5949 <entry><literal><function>extract</function>(<parameter>field</parameter> from
5950 <type>interval</type>)</literal></entry>
5951 <entry><type>double precision</type></entry>
5952 <entry>Get subfield; see <xref linkend="functions-datetime-extract">
5954 <entry><literal>extract(month from interval '2 years 3 months')</literal></entry>
5955 <entry><literal>3</literal></entry>
5959 <entry><literal><function>isfinite</function>(<type>date</type>)</literal></entry>
5960 <entry><type>boolean</type></entry>
5961 <entry>Test for finite date (not +/-infinity)</entry>
5962 <entry><literal>isfinite(date '2001-02-16')</literal></entry>
5963 <entry><literal>true</literal></entry>
5967 <entry><literal><function>isfinite</function>(<type>timestamp</type>)</literal></entry>
5968 <entry><type>boolean</type></entry>
5969 <entry>Test for finite time stamp (not +/-infinity)</entry>
5970 <entry><literal>isfinite(timestamp '2001-02-16 21:28:30')</literal></entry>
5971 <entry><literal>true</literal></entry>
5975 <entry><literal><function>isfinite</function>(<type>interval</type>)</literal></entry>
5976 <entry><type>boolean</type></entry>
5977 <entry>Test for finite interval</entry>
5978 <entry><literal>isfinite(interval '4 hours')</literal></entry>
5979 <entry><literal>true</literal></entry>
5983 <entry><literal><function>justify_days</function>(<type>interval</type>)</literal></entry>
5984 <entry><type>interval</type></entry>
5985 <entry>Adjust interval so 30-day time periods are represented as months</entry>
5986 <entry><literal>justify_days(interval '35 days')</literal></entry>
5987 <entry><literal>1 mon 5 days</literal></entry>
5991 <entry><literal><function>justify_hours</function>(<type>interval</type>)</literal></entry>
5992 <entry><type>interval</type></entry>
5993 <entry>Adjust interval so 24-hour time periods are represented as days</entry>
5994 <entry><literal>justify_hours(interval '27 hours')</literal></entry>
5995 <entry><literal>1 day 03:00:00</literal></entry>
5999 <entry><literal><function>justify_interval</function>(<type>interval</type>)</literal></entry>
6000 <entry><type>interval</type></entry>
6001 <entry>Adjust interval using <function>justify_days</> and <function>justify_hours</>, with additional sign adjustments</entry>
6002 <entry><literal>justify_interval(interval '1 mon -1 hour')</literal></entry>
6003 <entry><literal>29 days 23:00:00</literal></entry>
6007 <entry><literal><function>localtime</function></literal></entry>
6008 <entry><type>time</type></entry>
6009 <entry>Current time of day;
6010 see <xref linkend="functions-datetime-current">
6017 <entry><literal><function>localtimestamp</function></literal></entry>
6018 <entry><type>timestamp</type></entry>
6019 <entry>Current date and time (start of current transaction);
6020 see <xref linkend="functions-datetime-current">
6027 <entry><literal><function>now</function>()</literal></entry>
6028 <entry><type>timestamp with time zone</type></entry>
6029 <entry>Current date and time (start of current transaction);
6030 see <xref linkend="functions-datetime-current">
6037 <entry><literal><function>statement_timestamp</function>()</literal></entry>
6038 <entry><type>timestamp with time zone</type></entry>
6039 <entry>Current date and time (start of current statement);
6040 see <xref linkend="functions-datetime-current">
6047 <entry><literal><function>timeofday</function>()</literal></entry>
6048 <entry><type>text</type></entry>
6049 <entry>Current date and time
6050 (like <function>clock_timestamp</>, but as a <type>text</> string);
6051 see <xref linkend="functions-datetime-current">
6058 <entry><literal><function>transaction_timestamp</function>()</literal></entry>
6059 <entry><type>timestamp with time zone</type></entry>
6060 <entry>Current date and time (start of current transaction);
6061 see <xref linkend="functions-datetime-current">
6071 In addition to these functions, the SQL <literal>OVERLAPS</> operator is
6074 (<replaceable>start1</replaceable>, <replaceable>end1</replaceable>) OVERLAPS (<replaceable>start2</replaceable>, <replaceable>end2</replaceable>)
6075 (<replaceable>start1</replaceable>, <replaceable>length1</replaceable>) OVERLAPS (<replaceable>start2</replaceable>, <replaceable>length2</replaceable>)
6077 This expression yields true when two time periods (defined by their
6078 endpoints) overlap, false when they do not overlap. The endpoints
6079 can be specified as pairs of dates, times, or time stamps; or as
6080 a date, time, or time stamp followed by an interval.
6084 SELECT (DATE '2001-02-16', DATE '2001-12-21') OVERLAPS
6085 (DATE '2001-10-30', DATE '2002-10-30');
6086 <lineannotation>Result: </lineannotation><computeroutput>true</computeroutput>
6087 SELECT (DATE '2001-02-16', INTERVAL '100 days') OVERLAPS
6088 (DATE '2001-10-30', DATE '2002-10-30');
6089 <lineannotation>Result: </lineannotation><computeroutput>false</computeroutput>
6093 When adding an <type>interval</type> value to (or subtracting an
6094 <type>interval</type> value from) a <type>timestamp with time zone</type>
6095 value, the days component advances (or decrements) the date of the
6096 <type>timestamp with time zone</type> by the indicated number of days.
6097 Across daylight saving time changes (with the session time zone set to a
6098 time zone that recognizes DST), this means <literal>interval '1 day'</literal>
6099 does not necessarily equal <literal>interval '24 hours'</literal>.
6100 For example, with the session time zone set to <literal>CST7CDT</literal>,
6101 <literal>timestamp with time zone '2005-04-02 12:00-07' + interval '1 day' </literal>
6102 will produce <literal>timestamp with time zone '2005-04-03 12:00-06'</literal>,
6103 while adding <literal>interval '24 hours'</literal> to the same initial
6104 <type>timestamp with time zone</type> produces
6105 <literal>timestamp with time zone '2005-04-03 13:00-06'</literal>, as there is
6106 a change in daylight saving time at <literal>2005-04-03 02:00</literal> in time zone
6107 <literal>CST7CDT</literal>.
6111 Note there can be ambiguity in the <literal>months</> returned by
6112 <function>age</> because different months have a different number of
6113 days. <productname>PostgreSQL</>'s approach uses the month from the
6114 earlier of the two dates when calculating partial months. For example,
6115 <literal>age('2004-06-01', '2004-04-30')</> uses April to yield
6116 <literal>1 mon 1 day</>, while using May would yield <literal>1 mon 2
6117 days</> because May has 31 days, while April has only 30.
6120 <sect2 id="functions-datetime-extract">
6121 <title><function>EXTRACT</function>, <function>date_part</function></title>
6124 <primary>date_part</primary>
6127 <primary>extract</primary>
6131 EXTRACT(<replaceable>field</replaceable> FROM <replaceable>source</replaceable>)
6135 The <function>extract</function> function retrieves subfields
6136 such as year or hour from date/time values.
6137 <replaceable>source</replaceable> must be a value expression of
6138 type <type>timestamp</type>, <type>time</type>, or <type>interval</type>.
6139 (Expressions of type <type>date</type> are
6140 cast to <type>timestamp</type> and can therefore be used as
6141 well.) <replaceable>field</replaceable> is an identifier or
6142 string that selects what field to extract from the source value.
6143 The <function>extract</function> function returns values of type
6144 <type>double precision</type>.
6145 The following are valid field names:
6147 <!-- alphabetical -->
6150 <term><literal>century</literal></term>
6157 SELECT EXTRACT(CENTURY FROM TIMESTAMP '2000-12-16 12:21:13');
6158 <lineannotation>Result: </lineannotation><computeroutput>20</computeroutput>
6159 SELECT EXTRACT(CENTURY FROM TIMESTAMP '2001-02-16 20:38:40');
6160 <lineannotation>Result: </lineannotation><computeroutput>21</computeroutput>
6164 The first century starts at 0001-01-01 00:00:00 AD, although
6165 they did not know it at the time. This definition applies to all
6166 Gregorian calendar countries. There is no century number 0,
6167 you go from -1 century to 1 century.
6169 If you disagree with this, please write your complaint to:
6170 Pope, Cathedral Saint-Peter of Roma, Vatican.
6174 <productname>PostgreSQL</productname> releases before 8.0 did not
6175 follow the conventional numbering of centuries, but just returned
6176 the year field divided by 100.
6182 <term><literal>day</literal></term>
6185 The day (of the month) field (1 - 31)
6189 SELECT EXTRACT(DAY FROM TIMESTAMP '2001-02-16 20:38:40');
6190 <lineannotation>Result: </lineannotation><computeroutput>16</computeroutput>
6196 <term><literal>decade</literal></term>
6199 The year field divided by 10
6203 SELECT EXTRACT(DECADE FROM TIMESTAMP '2001-02-16 20:38:40');
6204 <lineannotation>Result: </lineannotation><computeroutput>200</computeroutput>
6210 <term><literal>dow</literal></term>
6213 The day of the week as Sunday(<literal>0</>) to
6214 Saturday(<literal>6</>)
6218 SELECT EXTRACT(DOW FROM TIMESTAMP '2001-02-16 20:38:40');
6219 <lineannotation>Result: </lineannotation><computeroutput>5</computeroutput>
6222 Note that <function>extract</function>'s day of the week numbering
6223 differs from that of the <function>to_char(...,
6224 'D')</function> function.
6231 <term><literal>doy</literal></term>
6234 The day of the year (1 - 365/366)
6238 SELECT EXTRACT(DOY FROM TIMESTAMP '2001-02-16 20:38:40');
6239 <lineannotation>Result: </lineannotation><computeroutput>47</computeroutput>
6245 <term><literal>epoch</literal></term>
6248 For <type>date</type> and <type>timestamp</type> values, the
6249 number of seconds since 1970-01-01 00:00:00 UTC (can be negative);
6250 for <type>interval</type> values, the total number
6251 of seconds in the interval
6255 SELECT EXTRACT(EPOCH FROM TIMESTAMP WITH TIME ZONE '2001-02-16 20:38:40.12-08');
6256 <lineannotation>Result: </lineannotation><computeroutput>982384720.12</computeroutput>
6258 SELECT EXTRACT(EPOCH FROM INTERVAL '5 days 3 hours');
6259 <lineannotation>Result: </lineannotation><computeroutput>442800</computeroutput>
6263 Here is how you can convert an epoch value back to a time
6267 SELECT TIMESTAMP WITH TIME ZONE 'epoch' + 982384720.12 * INTERVAL '1 second';
6270 (The <function>to_timestamp</> function encapsulates the above
6277 <term><literal>hour</literal></term>
6280 The hour field (0 - 23)
6284 SELECT EXTRACT(HOUR FROM TIMESTAMP '2001-02-16 20:38:40');
6285 <lineannotation>Result: </lineannotation><computeroutput>20</computeroutput>
6291 <term><literal>isodow</literal></term>
6294 The day of the week as Monday(<literal>1</>) to
6295 Sunday(<literal>7</>)
6299 SELECT EXTRACT(ISODOW FROM TIMESTAMP '2001-02-18 20:38:40');
6300 <lineannotation>Result: </lineannotation><computeroutput>7</computeroutput>
6303 This is identical to <literal>dow</> except for Sunday. This
6304 matches the <acronym>ISO</> 8601 day of the week numbering.
6311 <term><literal>isoyear</literal></term>
6314 The <acronym>ISO</acronym> 8601 year that the date falls in (not applicable to intervals)
6318 SELECT EXTRACT(ISOYEAR FROM DATE '2006-01-01');
6319 <lineannotation>Result: </lineannotation><computeroutput>2005</computeroutput>
6320 SELECT EXTRACT(ISOYEAR FROM DATE '2006-01-02');
6321 <lineannotation>Result: </lineannotation><computeroutput>2006</computeroutput>
6325 Each <acronym>ISO</acronym> year begins with the Monday of the week containing the 4th of January, so in early January or late December the <acronym>ISO</acronym> year may be different from the Gregorian year. See the <literal>week</literal> field for more information.
6328 This field is not available in PostgreSQL releases prior to 8.3.
6334 <term><literal>microseconds</literal></term>
6337 The seconds field, including fractional parts, multiplied by 1
6338 000 000; note that this includes full seconds
6342 SELECT EXTRACT(MICROSECONDS FROM TIME '17:12:28.5');
6343 <lineannotation>Result: </lineannotation><computeroutput>28500000</computeroutput>
6349 <term><literal>millennium</literal></term>
6356 SELECT EXTRACT(MILLENNIUM FROM TIMESTAMP '2001-02-16 20:38:40');
6357 <lineannotation>Result: </lineannotation><computeroutput>3</computeroutput>
6361 Years in the 1900s are in the second millennium.
6362 The third millennium started January 1, 2001.
6366 <productname>PostgreSQL</productname> releases before 8.0 did not
6367 follow the conventional numbering of millennia, but just returned
6368 the year field divided by 1000.
6374 <term><literal>milliseconds</literal></term>
6377 The seconds field, including fractional parts, multiplied by
6378 1000. Note that this includes full seconds.
6382 SELECT EXTRACT(MILLISECONDS FROM TIME '17:12:28.5');
6383 <lineannotation>Result: </lineannotation><computeroutput>28500</computeroutput>
6389 <term><literal>minute</literal></term>
6392 The minutes field (0 - 59)
6396 SELECT EXTRACT(MINUTE FROM TIMESTAMP '2001-02-16 20:38:40');
6397 <lineannotation>Result: </lineannotation><computeroutput>38</computeroutput>
6403 <term><literal>month</literal></term>
6406 For <type>timestamp</type> values, the number of the month
6407 within the year (1 - 12) ; for <type>interval</type> values
6408 the number of months, modulo 12 (0 - 11)
6412 SELECT EXTRACT(MONTH FROM TIMESTAMP '2001-02-16 20:38:40');
6413 <lineannotation>Result: </lineannotation><computeroutput>2</computeroutput>
6415 SELECT EXTRACT(MONTH FROM INTERVAL '2 years 3 months');
6416 <lineannotation>Result: </lineannotation><computeroutput>3</computeroutput>
6418 SELECT EXTRACT(MONTH FROM INTERVAL '2 years 13 months');
6419 <lineannotation>Result: </lineannotation><computeroutput>1</computeroutput>
6425 <term><literal>quarter</literal></term>
6428 The quarter of the year (1 - 4) that the date is in
6432 SELECT EXTRACT(QUARTER FROM TIMESTAMP '2001-02-16 20:38:40');
6433 <lineannotation>Result: </lineannotation><computeroutput>1</computeroutput>
6439 <term><literal>second</literal></term>
6442 The seconds field, including fractional parts (0 -
6443 59<footnote><simpara>60 if leap seconds are
6444 implemented by the operating system</simpara></footnote>)
6448 SELECT EXTRACT(SECOND FROM TIMESTAMP '2001-02-16 20:38:40');
6449 <lineannotation>Result: </lineannotation><computeroutput>40</computeroutput>
6451 SELECT EXTRACT(SECOND FROM TIME '17:12:28.5');
6452 <lineannotation>Result: </lineannotation><computeroutput>28.5</computeroutput>
6457 <term><literal>timezone</literal></term>
6460 The time zone offset from UTC, measured in seconds. Positive values
6461 correspond to time zones east of UTC, negative values to
6468 <term><literal>timezone_hour</literal></term>
6471 The hour component of the time zone offset
6477 <term><literal>timezone_minute</literal></term>
6480 The minute component of the time zone offset
6486 <term><literal>week</literal></term>
6489 The number of the week of the year that the day is in. By definition
6490 (<acronym>ISO</acronym> 8601), the first week of a year
6491 contains January 4 of that year. (The <acronym>ISO</acronym>-8601
6492 week starts on Monday.) In other words, the first Thursday of
6493 a year is in week 1 of that year.
6496 Because of this, it is possible for early January dates to be part of the
6497 52nd or 53rd week of the previous year. For example, <literal>2005-01-01</>
6498 is part of the 53rd week of year 2004, and <literal>2006-01-01</> is part of
6499 the 52nd week of year 2005.
6503 SELECT EXTRACT(WEEK FROM TIMESTAMP '2001-02-16 20:38:40');
6504 <lineannotation>Result: </lineannotation><computeroutput>7</computeroutput>
6510 <term><literal>year</literal></term>
6513 The year field. Keep in mind there is no <literal>0 AD</>, so subtracting
6514 <literal>BC</> years from <literal>AD</> years should be done with care.
6518 SELECT EXTRACT(YEAR FROM TIMESTAMP '2001-02-16 20:38:40');
6519 <lineannotation>Result: </lineannotation><computeroutput>2001</computeroutput>
6528 The <function>extract</function> function is primarily intended
6529 for computational processing. For formatting date/time values for
6530 display, see <xref linkend="functions-formatting">.
6534 The <function>date_part</function> function is modeled on the traditional
6535 <productname>Ingres</productname> equivalent to the
6536 <acronym>SQL</acronym>-standard function <function>extract</function>:
6538 date_part('<replaceable>field</replaceable>', <replaceable>source</replaceable>)
6540 Note that here the <replaceable>field</replaceable> parameter needs to
6541 be a string value, not a name. The valid field names for
6542 <function>date_part</function> are the same as for
6543 <function>extract</function>.
6547 SELECT date_part('day', TIMESTAMP '2001-02-16 20:38:40');
6548 <lineannotation>Result: </lineannotation><computeroutput>16</computeroutput>
6550 SELECT date_part('hour', INTERVAL '4 hours 3 minutes');
6551 <lineannotation>Result: </lineannotation><computeroutput>4</computeroutput>
6556 <sect2 id="functions-datetime-trunc">
6557 <title><function>date_trunc</function></title>
6560 <primary>date_trunc</primary>
6564 The function <function>date_trunc</function> is conceptually
6565 similar to the <function>trunc</function> function for numbers.
6570 date_trunc('<replaceable>field</replaceable>', <replaceable>source</replaceable>)
6572 <replaceable>source</replaceable> is a value expression of type
6573 <type>timestamp</type> or <type>interval</>.
6574 (Values of type <type>date</type> and
6575 <type>time</type> are cast automatically to <type>timestamp</type> or
6576 <type>interval</>, respectively.)
6577 <replaceable>field</replaceable> selects to which precision to
6578 truncate the input value. The return value is of type
6579 <type>timestamp</type> or <type>interval</>
6580 with all fields that are less significant than the
6581 selected one set to zero (or one, for day and month).
6585 Valid values for <replaceable>field</replaceable> are:
6587 <member><literal>microseconds</literal></member>
6588 <member><literal>milliseconds</literal></member>
6589 <member><literal>second</literal></member>
6590 <member><literal>minute</literal></member>
6591 <member><literal>hour</literal></member>
6592 <member><literal>day</literal></member>
6593 <member><literal>week</literal></member>
6594 <member><literal>month</literal></member>
6595 <member><literal>quarter</literal></member>
6596 <member><literal>year</literal></member>
6597 <member><literal>decade</literal></member>
6598 <member><literal>century</literal></member>
6599 <member><literal>millennium</literal></member>
6606 SELECT date_trunc('hour', TIMESTAMP '2001-02-16 20:38:40');
6607 <lineannotation>Result: </lineannotation><computeroutput>2001-02-16 20:00:00</computeroutput>
6609 SELECT date_trunc('year', TIMESTAMP '2001-02-16 20:38:40');
6610 <lineannotation>Result: </lineannotation><computeroutput>2001-01-01 00:00:00</computeroutput>
6615 <sect2 id="functions-datetime-zoneconvert">
6616 <title><literal>AT TIME ZONE</literal></title>
6619 <primary>time zone</primary>
6620 <secondary>conversion</secondary>
6624 <primary>AT TIME ZONE</primary>
6628 The <literal>AT TIME ZONE</literal> construct allows conversions
6629 of time stamps to different time zones. <xref
6630 linkend="functions-datetime-zoneconvert-table"> shows its
6634 <table id="functions-datetime-zoneconvert-table">
6635 <title><literal>AT TIME ZONE</literal> Variants</title>
6639 <entry>Expression</entry>
6640 <entry>Return Type</entry>
6641 <entry>Description</entry>
6648 <literal><type>timestamp without time zone</type> AT TIME ZONE <replaceable>zone</></literal>
6650 <entry><type>timestamp with time zone</type></entry>
6651 <entry>Treat given time stamp <emphasis>without time zone</> as located in the specified time zone</entry>
6656 <literal><type>timestamp with time zone</type> AT TIME ZONE <replaceable>zone</></literal>
6658 <entry><type>timestamp without time zone</type></entry>
6659 <entry>Convert given time stamp <emphasis>with time zone</> to the new time
6660 zone, with no time zone designation</entry>
6665 <literal><type>time with time zone</type> AT TIME ZONE <replaceable>zone</></literal>
6667 <entry><type>time with time zone</type></entry>
6668 <entry>Convert given time <emphasis>with time zone</> to the new time zone</entry>
6675 In these expressions, the desired time zone <replaceable>zone</> can be
6676 specified either as a text string (e.g., <literal>'PST'</literal>)
6677 or as an interval (e.g., <literal>INTERVAL '-08:00'</literal>).
6678 In the text case, a time zone name can be specified in any of the ways
6679 described in <xref linkend="datatype-timezones">.
6683 Examples (assuming the local time zone is <literal>PST8PDT</>):
6685 SELECT TIMESTAMP '2001-02-16 20:38:40' AT TIME ZONE 'MST';
6686 <lineannotation>Result: </lineannotation><computeroutput>2001-02-16 19:38:40-08</computeroutput>
6688 SELECT TIMESTAMP WITH TIME ZONE '2001-02-16 20:38:40-05' AT TIME ZONE 'MST';
6689 <lineannotation>Result: </lineannotation><computeroutput>2001-02-16 18:38:40</computeroutput>
6691 The first example takes a time stamp without time zone and interprets it as MST time
6692 (UTC-7), which is then converted to PST (UTC-8) for display. The second example takes
6693 a time stamp specified in EST (UTC-5) and converts it to local time in MST (UTC-7).
6697 The function <literal><function>timezone</function>(<replaceable>zone</>,
6698 <replaceable>timestamp</>)</literal> is equivalent to the SQL-conforming construct
6699 <literal><replaceable>timestamp</> AT TIME ZONE
6700 <replaceable>zone</></literal>.
6704 <sect2 id="functions-datetime-current">
6705 <title>Current Date/Time</title>
6708 <primary>date</primary>
6709 <secondary>current</secondary>
6713 <primary>time</primary>
6714 <secondary>current</secondary>
6718 <productname>PostgreSQL</productname> provides a number of functions
6719 that return values related to the current date and time. These
6720 SQL-standard functions all return values based on the start time of
6721 the current transaction:
6726 CURRENT_TIME(<replaceable>precision</replaceable>)
6727 CURRENT_TIMESTAMP(<replaceable>precision</replaceable>)
6730 LOCALTIME(<replaceable>precision</replaceable>)
6731 LOCALTIMESTAMP(<replaceable>precision</replaceable>)
6736 <function>CURRENT_TIME</function> and
6737 <function>CURRENT_TIMESTAMP</function> deliver values with time zone;
6738 <function>LOCALTIME</function> and
6739 <function>LOCALTIMESTAMP</function> deliver values without time zone.
6743 <function>CURRENT_TIME</function>,
6744 <function>CURRENT_TIMESTAMP</function>,
6745 <function>LOCALTIME</function>, and
6746 <function>LOCALTIMESTAMP</function>
6748 a precision parameter, which causes the result to be rounded
6749 to that many fractional digits in the seconds field. Without a precision parameter,
6750 the result is given to the full available precision.
6756 SELECT CURRENT_TIME;
6757 <lineannotation>Result: </lineannotation><computeroutput>14:39:53.662522-05</computeroutput>
6759 SELECT CURRENT_DATE;
6760 <lineannotation>Result: </lineannotation><computeroutput>2001-12-23</computeroutput>
6762 SELECT CURRENT_TIMESTAMP;
6763 <lineannotation>Result: </lineannotation><computeroutput>2001-12-23 14:39:53.662522-05</computeroutput>
6765 SELECT CURRENT_TIMESTAMP(2);
6766 <lineannotation>Result: </lineannotation><computeroutput>2001-12-23 14:39:53.66-05</computeroutput>
6768 SELECT LOCALTIMESTAMP;
6769 <lineannotation>Result: </lineannotation><computeroutput>2001-12-23 14:39:53.662522</computeroutput>
6774 Since these functions return
6775 the start time of the current transaction, their values do not
6776 change during the transaction. This is considered a feature:
6777 the intent is to allow a single transaction to have a consistent
6778 notion of the <quote>current</quote> time, so that multiple
6779 modifications within the same transaction bear the same
6785 Other database systems might advance these values more
6791 <productname>PostgreSQL</productname> also provides functions that
6792 return the start time of the current statement, as well as the actual
6793 current time at the instant the function is called. The complete list
6794 of non-SQL-standard time functions is:
6796 transaction_timestamp()
6797 statement_timestamp()
6805 <function>transaction_timestamp()</> is equivalent to
6806 <function>CURRENT_TIMESTAMP</function>, but is named to clearly reflect
6808 <function>statement_timestamp()</> returns the start time of the current
6809 statement (more specifically, the time of receipt of the latest command
6810 message from the client).
6811 <function>statement_timestamp()</> and <function>transaction_timestamp()</>
6812 return the same value during the first command of a transaction, but might
6813 differ during subsequent commands.
6814 <function>clock_timestamp()</> returns the actual current time, and
6815 therefore its value changes even within a single SQL command.
6816 <function>timeofday()</> is a historical
6817 <productname>PostgreSQL</productname> function. Like
6818 <function>clock_timestamp()</>, it returns the actual current time,
6819 but as a formatted <type>text</> string rather than a <type>timestamp
6820 with time zone</> value.
6821 <function>now()</> is a traditional <productname>PostgreSQL</productname>
6822 equivalent to <function>transaction_timestamp()</function>.
6826 All the date/time data types also accept the special literal value
6827 <literal>now</literal> to specify the current date and time (again,
6828 interpreted as the transaction start time). Thus,
6829 the following three all return the same result:
6831 SELECT CURRENT_TIMESTAMP;
6833 SELECT TIMESTAMP 'now'; -- incorrect for use with DEFAULT
6839 You do not want to use the third form when specifying a <literal>DEFAULT</>
6840 clause while creating a table. The system will convert <literal>now</literal>
6841 to a <type>timestamp</type> as soon as the constant is parsed, so that when
6842 the default value is needed,
6843 the time of the table creation would be used! The first two
6844 forms will not be evaluated until the default value is used,
6845 because they are function calls. Thus they will give the desired
6846 behavior of defaulting to the time of row insertion.
6851 <sect2 id="functions-datetime-delay">
6852 <title>Delaying Execution</title>
6855 <primary>pg_sleep</primary>
6858 <primary>sleep</primary>
6861 <primary>delay</primary>
6865 The following function is available to delay execution of the server
6868 pg_sleep(<replaceable>seconds</replaceable>)
6871 <function>pg_sleep</function> makes the current session's process
6872 sleep until <replaceable>seconds</replaceable> seconds have
6873 elapsed. <replaceable>seconds</replaceable> is a value of type
6874 <type>double precision</>, so fractional-second delays can be specified.
6878 SELECT pg_sleep(1.5);
6884 The effective resolution of the sleep interval is platform-specific;
6885 0.01 seconds is a common value. The sleep delay will be at least as long
6886 as specified. It might be longer depending on factors such as server load.
6892 Make sure that your session does not hold more locks than necessary
6893 when calling <function>pg_sleep</function>. Otherwise other sessions
6894 might have to wait for your sleeping process, slowing down the entire
6903 <sect1 id="functions-enum">
6904 <title>Enum Support Functions</title>
6907 For enum types (described in <xref linkend="datatype-enum">),
6908 there are several functions that allow cleaner programming without
6909 hard-coding particular values of an enum type.
6910 These are listed in <xref linkend="functions-enum-table">. The examples
6911 assume an enum type created as:
6914 CREATE TYPE rainbow AS ENUM ('red', 'orange', 'yellow', 'green', 'blue', 'purple');
6919 <table id="functions-enum-table">
6920 <title>Enum Support Functions</title>
6924 <entry>Function</entry>
6925 <entry>Description</entry>
6926 <entry>Example</entry>
6927 <entry>Example Result</entry>
6932 <entry><literal>enum_first(anyenum)</literal></entry>
6933 <entry>Returns the first value of the input enum type</entry>
6934 <entry><literal>enum_first(null::rainbow)</literal></entry>
6935 <entry><literal>red</literal></entry>
6938 <entry><literal>enum_last(anyenum)</literal></entry>
6939 <entry>Returns the last value of the input enum type</entry>
6940 <entry><literal>enum_last(null::rainbow)</literal></entry>
6941 <entry><literal>purple</literal></entry>
6944 <entry><literal>enum_range(anyenum)</literal></entry>
6945 <entry>Returns all values of the input enum type in an ordered array</entry>
6946 <entry><literal>enum_range(null::rainbow)</literal></entry>
6947 <entry><literal>{red,orange,yellow,green,blue,purple}</literal></entry>
6950 <entry morerows="2"><literal>enum_range(anyenum, anyenum)</literal></entry>
6951 <entry morerows="2">
6952 Returns the range between the two given enum values, as an ordered
6953 array. The values must be from the same enum type. If the first
6954 parameter is null, the result will start with the first value of
6956 If the second parameter is null, the result will end with the last
6957 value of the enum type.
6959 <entry><literal>enum_range('orange'::rainbow, 'green'::rainbow)</literal></entry>
6960 <entry><literal>{orange,yellow,green}</literal></entry>
6963 <entry><literal>enum_range(NULL, 'green'::rainbow)</literal></entry>
6964 <entry><literal>{red,orange,yellow,green}</literal></entry>
6967 <entry><literal>enum_range('orange'::rainbow, NULL)</literal></entry>
6968 <entry><literal>{orange,yellow,green,blue,purple}</literal></entry>
6975 Notice that except for the two-argument form of <function>enum_range</>,
6976 these functions disregard the specific value passed to them; they care
6977 only about its declared data type. Either null or a specific value of
6978 the type can be passed, with the same result. It is more common to
6979 apply these functions to a table column or function argument than to
6980 a hardwired type name as suggested by the examples.
6984 <sect1 id="functions-geometry">
6985 <title>Geometric Functions and Operators</title>
6988 The geometric types <type>point</type>, <type>box</type>,
6989 <type>lseg</type>, <type>line</type>, <type>path</type>,
6990 <type>polygon</type>, and <type>circle</type> have a large set of
6991 native support functions and operators, shown in <xref
6992 linkend="functions-geometry-op-table">, <xref
6993 linkend="functions-geometry-func-table">, and <xref
6994 linkend="functions-geometry-conv-table">.
6999 Note that the <quote>same as</> operator, <literal>~=</>, represents
7000 the usual notion of equality for the <type>point</type>,
7001 <type>box</type>, <type>polygon</type>, and <type>circle</type> types.
7002 Some of these types also have an <literal>=</> operator, but
7003 <literal>=</> compares
7004 for equal <emphasis>areas</> only. The other scalar comparison operators
7005 (<literal><=</> and so on) likewise compare areas for these types.
7009 <table id="functions-geometry-op-table">
7010 <title>Geometric Operators</title>
7014 <entry>Operator</entry>
7015 <entry>Description</entry>
7016 <entry>Example</entry>
7021 <entry> <literal>+</literal> </entry>
7022 <entry>Translation</entry>
7023 <entry><literal>box '((0,0),(1,1))' + point '(2.0,0)'</literal></entry>
7026 <entry> <literal>-</literal> </entry>
7027 <entry>Translation</entry>
7028 <entry><literal>box '((0,0),(1,1))' - point '(2.0,0)'</literal></entry>
7031 <entry> <literal>*</literal> </entry>
7032 <entry>Scaling/rotation</entry>
7033 <entry><literal>box '((0,0),(1,1))' * point '(2.0,0)'</literal></entry>
7036 <entry> <literal>/</literal> </entry>
7037 <entry>Scaling/rotation</entry>
7038 <entry><literal>box '((0,0),(2,2))' / point '(2.0,0)'</literal></entry>
7041 <entry> <literal>#</literal> </entry>
7042 <entry>Point or box of intersection</entry>
7043 <entry><literal>'((1,-1),(-1,1))' # '((1,1),(-1,-1))'</literal></entry>
7046 <entry> <literal>#</literal> </entry>
7047 <entry>Number of points in path or polygon</entry>
7048 <entry><literal># '((1,0),(0,1),(-1,0))'</literal></entry>
7051 <entry> <literal>@-@</literal> </entry>
7052 <entry>Length or circumference</entry>
7053 <entry><literal>@-@ path '((0,0),(1,0))'</literal></entry>
7056 <entry> <literal>@@</literal> </entry>
7057 <entry>Center</entry>
7058 <entry><literal>@@ circle '((0,0),10)'</literal></entry>
7061 <entry> <literal>##</literal> </entry>
7062 <entry>Closest point to first operand on second operand</entry>
7063 <entry><literal>point '(0,0)' ## lseg '((2,0),(0,2))'</literal></entry>
7066 <entry> <literal><-></literal> </entry>
7067 <entry>Distance between</entry>
7068 <entry><literal>circle '((0,0),1)' <-> circle '((5,0),1)'</literal></entry>
7071 <entry> <literal>&&</literal> </entry>
7072 <entry>Overlaps?</entry>
7073 <entry><literal>box '((0,0),(1,1))' && box '((0,0),(2,2))'</literal></entry>
7076 <entry> <literal><<</literal> </entry>
7077 <entry>Is strictly left of?</entry>
7078 <entry><literal>circle '((0,0),1)' << circle '((5,0),1)'</literal></entry>
7081 <entry> <literal>>></literal> </entry>
7082 <entry>Is strictly right of?</entry>
7083 <entry><literal>circle '((5,0),1)' >> circle '((0,0),1)'</literal></entry>
7086 <entry> <literal>&<</literal> </entry>
7087 <entry>Does not extend to the right of?</entry>
7088 <entry><literal>box '((0,0),(1,1))' &< box '((0,0),(2,2))'</literal></entry>
7091 <entry> <literal>&></literal> </entry>
7092 <entry>Does not extend to the left of?</entry>
7093 <entry><literal>box '((0,0),(3,3))' &> box '((0,0),(2,2))'</literal></entry>
7096 <entry> <literal><<|</literal> </entry>
7097 <entry>Is strictly below?</entry>
7098 <entry><literal>box '((0,0),(3,3))' <<| box '((3,4),(5,5))'</literal></entry>
7101 <entry> <literal>|>></literal> </entry>
7102 <entry>Is strictly above?</entry>
7103 <entry><literal>box '((3,4),(5,5))' |>> box '((0,0),(3,3))'</literal></entry>
7106 <entry> <literal>&<|</literal> </entry>
7107 <entry>Does not extend above?</entry>
7108 <entry><literal>box '((0,0),(1,1))' &<| box '((0,0),(2,2))'</literal></entry>
7111 <entry> <literal>|&></literal> </entry>
7112 <entry>Does not extend below?</entry>
7113 <entry><literal>box '((0,0),(3,3))' |&> box '((0,0),(2,2))'</literal></entry>
7116 <entry> <literal><^</literal> </entry>
7117 <entry>Is below (allows touching)?</entry>
7118 <entry><literal>circle '((0,0),1)' <^ circle '((0,5),1)'</literal></entry>
7121 <entry> <literal>>^</literal> </entry>
7122 <entry>Is above (allows touching)?</entry>
7123 <entry><literal>circle '((0,5),1)' >^ circle '((0,0),1)'</literal></entry>
7126 <entry> <literal>?#</literal> </entry>
7127 <entry>Intersects?</entry>
7128 <entry><literal>lseg '((-1,0),(1,0))' ?# box '((-2,-2),(2,2))'</literal></entry>
7131 <entry> <literal>?-</literal> </entry>
7132 <entry>Is horizontal?</entry>
7133 <entry><literal>?- lseg '((-1,0),(1,0))'</literal></entry>
7136 <entry> <literal>?-</literal> </entry>
7137 <entry>Are horizontally aligned?</entry>
7138 <entry><literal>point '(1,0)' ?- point '(0,0)'</literal></entry>
7141 <entry> <literal>?|</literal> </entry>
7142 <entry>Is vertical?</entry>
7143 <entry><literal>?| lseg '((-1,0),(1,0))'</literal></entry>
7146 <entry> <literal>?|</literal> </entry>
7147 <entry>Are vertically aligned?</entry>
7148 <entry><literal>point '(0,1)' ?| point '(0,0)'</literal></entry>
7151 <entry> <literal>?-|</literal> </entry>
7152 <entry>Is perpendicular?</entry>
7153 <entry><literal>lseg '((0,0),(0,1))' ?-| lseg '((0,0),(1,0))'</literal></entry>
7156 <entry> <literal>?||</literal> </entry>
7157 <entry>Are parallel?</entry>
7158 <entry><literal>lseg '((-1,0),(1,0))' ?|| lseg '((-1,2),(1,2))'</literal></entry>
7161 <entry> <literal>@></literal> </entry>
7162 <entry>Contains?</entry>
7163 <entry><literal>circle '((0,0),2)' @> point '(1,1)'</literal></entry>
7166 <entry> <literal><@</literal> </entry>
7167 <entry>Contained in or on?</entry>
7168 <entry><literal>point '(1,1)' <@ circle '((0,0),2)'</literal></entry>
7171 <entry> <literal>~=</literal> </entry>
7172 <entry>Same as?</entry>
7173 <entry><literal>polygon '((0,0),(1,1))' ~= polygon '((1,1),(0,0))'</literal></entry>
7181 Before <productname>PostgreSQL</productname> 8.2, the containment
7182 operators <literal>@></> and <literal><@</> were respectively
7183 called <literal>~</> and <literal>@</>. These names are still
7184 available, but are deprecated and will eventually be removed.
7189 <primary>area</primary>
7192 <primary>center</primary>
7195 <primary>diameter</primary>
7198 <primary>height</primary>
7201 <primary>isclosed</primary>
7204 <primary>isopen</primary>
7207 <primary>length</primary>
7210 <primary>npoints</primary>
7213 <primary>pclose</primary>
7216 <primary>popen</primary>
7219 <primary>radius</primary>
7222 <primary>width</primary>
7225 <table id="functions-geometry-func-table">
7226 <title>Geometric Functions</title>
7230 <entry>Function</entry>
7231 <entry>Return Type</entry>
7232 <entry>Description</entry>
7233 <entry>Example</entry>
7238 <entry><literal><function>area</function>(<replaceable>object</>)</literal></entry>
7239 <entry><type>double precision</type></entry>
7241 <entry><literal>area(box '((0,0),(1,1))')</literal></entry>
7244 <entry><literal><function>center</function>(<replaceable>object</>)</literal></entry>
7245 <entry><type>point</type></entry>
7246 <entry>center</entry>
7247 <entry><literal>center(box '((0,0),(1,2))')</literal></entry>
7250 <entry><literal><function>diameter</function>(<type>circle</>)</literal></entry>
7251 <entry><type>double precision</type></entry>
7252 <entry>diameter of circle</entry>
7253 <entry><literal>diameter(circle '((0,0),2.0)')</literal></entry>
7256 <entry><literal><function>height</function>(<type>box</>)</literal></entry>
7257 <entry><type>double precision</type></entry>
7258 <entry>vertical size of box</entry>
7259 <entry><literal>height(box '((0,0),(1,1))')</literal></entry>
7262 <entry><literal><function>isclosed</function>(<type>path</>)</literal></entry>
7263 <entry><type>boolean</type></entry>
7264 <entry>a closed path?</entry>
7265 <entry><literal>isclosed(path '((0,0),(1,1),(2,0))')</literal></entry>
7268 <entry><literal><function>isopen</function>(<type>path</>)</literal></entry>
7269 <entry><type>boolean</type></entry>
7270 <entry>an open path?</entry>
7271 <entry><literal>isopen(path '[(0,0),(1,1),(2,0)]')</literal></entry>
7274 <entry><literal><function>length</function>(<replaceable>object</>)</literal></entry>
7275 <entry><type>double precision</type></entry>
7276 <entry>length</entry>
7277 <entry><literal>length(path '((-1,0),(1,0))')</literal></entry>
7280 <entry><literal><function>npoints</function>(<type>path</>)</literal></entry>
7281 <entry><type>int</type></entry>
7282 <entry>number of points</entry>
7283 <entry><literal>npoints(path '[(0,0),(1,1),(2,0)]')</literal></entry>
7286 <entry><literal><function>npoints</function>(<type>polygon</>)</literal></entry>
7287 <entry><type>int</type></entry>
7288 <entry>number of points</entry>
7289 <entry><literal>npoints(polygon '((1,1),(0,0))')</literal></entry>
7292 <entry><literal><function>pclose</function>(<type>path</>)</literal></entry>
7293 <entry><type>path</type></entry>
7294 <entry>convert path to closed</entry>
7295 <entry><literal>pclose(path '[(0,0),(1,1),(2,0)]')</literal></entry>
7298 <!-- Not defined by this name. Implements the intersection operator '#' -->
7300 <entry><literal><function>point</function>(<type>lseg</>, <type>lseg</>)</literal></entry>
7301 <entry><type>point</type></entry>
7302 <entry>intersection</entry>
7303 <entry><literal>point(lseg '((-1,0),(1,0))',lseg '((-2,-2),(2,2))')</literal></entry>
7307 <entry><literal><function>popen</function>(<type>path</>)</literal></entry>
7308 <entry><type>path</type></entry>
7309 <entry>convert path to open</entry>
7310 <entry><literal>popen(path '((0,0),(1,1),(2,0))')</literal></entry>
7313 <entry><literal><function>radius</function>(<type>circle</type>)</literal></entry>
7314 <entry><type>double precision</type></entry>
7315 <entry>radius of circle</entry>
7316 <entry><literal>radius(circle '((0,0),2.0)')</literal></entry>
7319 <entry><literal><function>width</function>(<type>box</>)</literal></entry>
7320 <entry><type>double precision</type></entry>
7321 <entry>horizontal size of box</entry>
7322 <entry><literal>width(box '((0,0),(1,1))')</literal></entry>
7328 <table id="functions-geometry-conv-table">
7329 <title>Geometric Type Conversion Functions</title>
7333 <entry>Function</entry>
7334 <entry>Return Type</entry>
7335 <entry>Description</entry>
7336 <entry>Example</entry>
7341 <entry><literal><function>box</function>(<type>circle</type>)</literal></entry>
7342 <entry><type>box</type></entry>
7343 <entry>circle to box</entry>
7344 <entry><literal>box(circle '((0,0),2.0)')</literal></entry>
7347 <entry><literal><function>box</function>(<type>point</type>, <type>point</type>)</literal></entry>
7348 <entry><type>box</type></entry>
7349 <entry>points to box</entry>
7350 <entry><literal>box(point '(0,0)', point '(1,1)')</literal></entry>
7353 <entry><literal><function>box</function>(<type>polygon</type>)</literal></entry>
7354 <entry><type>box</type></entry>
7355 <entry>polygon to box</entry>
7356 <entry><literal>box(polygon '((0,0),(1,1),(2,0))')</literal></entry>
7359 <entry><literal><function>circle</function>(<type>box</type>)</literal></entry>
7360 <entry><type>circle</type></entry>
7361 <entry>box to circle</entry>
7362 <entry><literal>circle(box '((0,0),(1,1))')</literal></entry>
7365 <entry><literal><function>circle</function>(<type>point</type>, <type>double precision</type>)</literal></entry>
7366 <entry><type>circle</type></entry>
7367 <entry>center and radius to circle</entry>
7368 <entry><literal>circle(point '(0,0)', 2.0)</literal></entry>
7371 <entry><literal><function>circle</function>(<type>polygon</type>)</literal></entry>
7372 <entry><type>circle</type></entry>
7373 <entry>polygon to circle</entry>
7374 <entry><literal>circle(polygon '((0,0),(1,1),(2,0))')</literal></entry>
7377 <entry><literal><function>lseg</function>(<type>box</type>)</literal></entry>
7378 <entry><type>lseg</type></entry>
7379 <entry>box diagonal to line segment</entry>
7380 <entry><literal>lseg(box '((-1,0),(1,0))')</literal></entry>
7383 <entry><literal><function>lseg</function>(<type>point</type>, <type>point</type>)</literal></entry>
7384 <entry><type>lseg</type></entry>
7385 <entry>points to line segment</entry>
7386 <entry><literal>lseg(point '(-1,0)', point '(1,0)')</literal></entry>
7389 <entry><literal><function>path</function>(<type>polygon</type>)</literal></entry>
7390 <entry><type>point</type></entry>
7391 <entry>polygon to path</entry>
7392 <entry><literal>path(polygon '((0,0),(1,1),(2,0))')</literal></entry>
7395 <entry><literal><function>point</function>(<type>double
7396 precision</type>, <type>double precision</type>)</literal></entry>
7397 <entry><type>point</type></entry>
7398 <entry>construct point</entry>
7399 <entry><literal>point(23.4, -44.5)</literal></entry>
7402 <entry><literal><function>point</function>(<type>box</type>)</literal></entry>
7403 <entry><type>point</type></entry>
7404 <entry>center of box</entry>
7405 <entry><literal>point(box '((-1,0),(1,0))')</literal></entry>
7408 <entry><literal><function>point</function>(<type>circle</type>)</literal></entry>
7409 <entry><type>point</type></entry>
7410 <entry>center of circle</entry>
7411 <entry><literal>point(circle '((0,0),2.0)')</literal></entry>
7414 <entry><literal><function>point</function>(<type>lseg</type>)</literal></entry>
7415 <entry><type>point</type></entry>
7416 <entry>center of line segment</entry>
7417 <entry><literal>point(lseg '((-1,0),(1,0))')</literal></entry>
7420 <entry><literal><function>point</function>(<type>polygon</type>)</literal></entry>
7421 <entry><type>point</type></entry>
7422 <entry>center of polygon</entry>
7423 <entry><literal>point(polygon '((0,0),(1,1),(2,0))')</literal></entry>
7426 <entry><literal><function>polygon</function>(<type>box</type>)</literal></entry>
7427 <entry><type>polygon</type></entry>
7428 <entry>box to 4-point polygon</entry>
7429 <entry><literal>polygon(box '((0,0),(1,1))')</literal></entry>
7432 <entry><literal><function>polygon</function>(<type>circle</type>)</literal></entry>
7433 <entry><type>polygon</type></entry>
7434 <entry>circle to 12-point polygon</entry>
7435 <entry><literal>polygon(circle '((0,0),2.0)')</literal></entry>
7438 <entry><literal><function>polygon</function>(<replaceable class="parameter">npts</replaceable>, <type>circle</type>)</literal></entry>
7439 <entry><type>polygon</type></entry>
7440 <entry>circle to <replaceable class="parameter">npts</replaceable>-point polygon</entry>
7441 <entry><literal>polygon(12, circle '((0,0),2.0)')</literal></entry>
7444 <entry><literal><function>polygon</function>(<type>path</type>)</literal></entry>
7445 <entry><type>polygon</type></entry>
7446 <entry>path to polygon</entry>
7447 <entry><literal>polygon(path '((0,0),(1,1),(2,0))')</literal></entry>
7454 It is possible to access the two component numbers of a <type>point</>
7455 as though the point were an array with indexes 0 and 1. For example, if
7456 <literal>t.p</> is a <type>point</> column then
7457 <literal>SELECT p[0] FROM t</> retrieves the X coordinate and
7458 <literal>UPDATE t SET p[1] = ...</> changes the Y coordinate.
7459 In the same way, a value of type <type>box</> or <type>lseg</> can be treated
7460 as an array of two <type>point</> values.
7464 The <function>area</function> function works for the types
7465 <type>box</type>, <type>circle</type>, and <type>path</type>.
7466 The <function>area</function> function only works on the
7467 <type>path</type> data type if the points in the
7468 <type>path</type> are non-intersecting. For example, the
7470 <literal>'((0,0),(0,1),(2,1),(2,2),(1,2),(1,0),(0,0))'::PATH</literal>
7471 will not work; however, the following visually identical
7473 <literal>'((0,0),(0,1),(1,1),(1,2),(2,2),(2,1),(1,1),(1,0),(0,0))'::PATH</literal>
7474 will work. If the concept of an intersecting versus
7475 non-intersecting <type>path</type> is confusing, draw both of the
7476 above <type>path</type>s side by side on a piece of graph paper.
7482 <sect1 id="functions-net">
7483 <title>Network Address Functions and Operators</title>
7486 <xref linkend="cidr-inet-operators-table"> shows the operators
7487 available for the <type>cidr</type> and <type>inet</type> types.
7488 The operators <literal><<</literal>,
7489 <literal><<=</literal>, <literal>>></literal>, and
7490 <literal>>>=</literal> test for subnet inclusion. They
7491 consider only the network parts of the two addresses (ignoring any
7492 host part) and determine whether one network is identical to
7493 or a subnet of the other.
7496 <table id="cidr-inet-operators-table">
7497 <title><type>cidr</type> and <type>inet</type> Operators</title>
7501 <entry>Operator</entry>
7502 <entry>Description</entry>
7503 <entry>Example</entry>
7508 <entry> <literal><</literal> </entry>
7509 <entry>is less than</entry>
7510 <entry><literal>inet '192.168.1.5' < inet '192.168.1.6'</literal></entry>
7513 <entry> <literal><=</literal> </entry>
7514 <entry>is less than or equal</entry>
7515 <entry><literal>inet '192.168.1.5' <= inet '192.168.1.5'</literal></entry>
7518 <entry> <literal>=</literal> </entry>
7519 <entry>equals</entry>
7520 <entry><literal>inet '192.168.1.5' = inet '192.168.1.5'</literal></entry>
7523 <entry> <literal>>=</literal> </entry>
7524 <entry>is greater or equal</entry>
7525 <entry><literal>inet '192.168.1.5' >= inet '192.168.1.5'</literal></entry>
7528 <entry> <literal>></literal> </entry>
7529 <entry>is greater than</entry>
7530 <entry><literal>inet '192.168.1.5' > inet '192.168.1.4'</literal></entry>
7533 <entry> <literal><></literal> </entry>
7534 <entry>is not equal</entry>
7535 <entry><literal>inet '192.168.1.5' <> inet '192.168.1.4'</literal></entry>
7538 <entry> <literal><<</literal> </entry>
7539 <entry>is contained within</entry>
7540 <entry><literal>inet '192.168.1.5' << inet '192.168.1/24'</literal></entry>
7543 <entry> <literal><<=</literal> </entry>
7544 <entry>is contained within or equals</entry>
7545 <entry><literal>inet '192.168.1/24' <<= inet '192.168.1/24'</literal></entry>
7548 <entry> <literal>>></literal> </entry>
7549 <entry>contains</entry>
7550 <entry><literal>inet '192.168.1/24' >> inet '192.168.1.5'</literal></entry>
7553 <entry> <literal>>>=</literal> </entry>
7554 <entry>contains or equals</entry>
7555 <entry><literal>inet '192.168.1/24' >>= inet '192.168.1/24'</literal></entry>
7558 <entry> <literal>~</literal> </entry>
7559 <entry>bitwise NOT</entry>
7560 <entry><literal>~ inet '192.168.1.6'</literal></entry>
7563 <entry> <literal>&</literal> </entry>
7564 <entry>bitwise AND</entry>
7565 <entry><literal>inet '192.168.1.6' & inet '0.0.0.255'</literal></entry>
7568 <entry> <literal>|</literal> </entry>
7569 <entry>bitwise OR</entry>
7570 <entry><literal>inet '192.168.1.6' | inet '0.0.0.255'</literal></entry>
7573 <entry> <literal>+</literal> </entry>
7574 <entry>addition</entry>
7575 <entry><literal>inet '192.168.1.6' + 25</literal></entry>
7578 <entry> <literal>-</literal> </entry>
7579 <entry>subtraction</entry>
7580 <entry><literal>inet '192.168.1.43' - 36</literal></entry>
7583 <entry> <literal>-</literal> </entry>
7584 <entry>subtraction</entry>
7585 <entry><literal>inet '192.168.1.43' - inet '192.168.1.19'</literal></entry>
7592 <xref linkend="cidr-inet-functions-table"> shows the functions
7593 available for use with the <type>cidr</type> and <type>inet</type>
7594 types. The <function>abbrev</function>, <function>host</function>,
7595 and <function>text</function>
7596 functions are primarily intended to offer alternative display
7600 <table id="cidr-inet-functions-table">
7601 <title><type>cidr</type> and <type>inet</type> Functions</title>
7605 <entry>Function</entry>
7606 <entry>Return Type</entry>
7607 <entry>Description</entry>
7608 <entry>Example</entry>
7609 <entry>Result</entry>
7614 <entry><literal><function>abbrev</function>(<type>inet</type>)</literal></entry>
7615 <entry><type>text</type></entry>
7616 <entry>abbreviated display format as text</entry>
7617 <entry><literal>abbrev(inet '10.1.0.0/16')</literal></entry>
7618 <entry><literal>10.1.0.0/16</literal></entry>
7621 <entry><literal><function>abbrev</function>(<type>cidr</type>)</literal></entry>
7622 <entry><type>text</type></entry>
7623 <entry>abbreviated display format as text</entry>
7624 <entry><literal>abbrev(cidr '10.1.0.0/16')</literal></entry>
7625 <entry><literal>10.1/16</literal></entry>
7628 <entry><literal><function>broadcast</function>(<type>inet</type>)</literal></entry>
7629 <entry><type>inet</type></entry>
7630 <entry>broadcast address for network</entry>
7631 <entry><literal>broadcast('192.168.1.5/24')</literal></entry>
7632 <entry><literal>192.168.1.255/24</literal></entry>
7635 <entry><literal><function>family</function>(<type>inet</type>)</literal></entry>
7636 <entry><type>int</type></entry>
7637 <entry>extract family of address; <literal>4</literal> for IPv4,
7638 <literal>6</literal> for IPv6</entry>
7639 <entry><literal>family('::1')</literal></entry>
7640 <entry><literal>6</literal></entry>
7643 <entry><literal><function>host</function>(<type>inet</type>)</literal></entry>
7644 <entry><type>text</type></entry>
7645 <entry>extract IP address as text</entry>
7646 <entry><literal>host('192.168.1.5/24')</literal></entry>
7647 <entry><literal>192.168.1.5</literal></entry>
7650 <entry><literal><function>hostmask</function>(<type>inet</type>)</literal></entry>
7651 <entry><type>inet</type></entry>
7652 <entry>construct host mask for network</entry>
7653 <entry><literal>hostmask('192.168.23.20/30')</literal></entry>
7654 <entry><literal>0.0.0.3</literal></entry>
7657 <entry><literal><function>masklen</function>(<type>inet</type>)</literal></entry>
7658 <entry><type>int</type></entry>
7659 <entry>extract netmask length</entry>
7660 <entry><literal>masklen('192.168.1.5/24')</literal></entry>
7661 <entry><literal>24</literal></entry>
7664 <entry><literal><function>netmask</function>(<type>inet</type>)</literal></entry>
7665 <entry><type>inet</type></entry>
7666 <entry>construct netmask for network</entry>
7667 <entry><literal>netmask('192.168.1.5/24')</literal></entry>
7668 <entry><literal>255.255.255.0</literal></entry>
7671 <entry><literal><function>network</function>(<type>inet</type>)</literal></entry>
7672 <entry><type>cidr</type></entry>
7673 <entry>extract network part of address</entry>
7674 <entry><literal>network('192.168.1.5/24')</literal></entry>
7675 <entry><literal>192.168.1.0/24</literal></entry>
7678 <entry><literal><function>set_masklen</function>(<type>inet</type>, <type>int</type>)</literal></entry>
7679 <entry><type>inet</type></entry>
7680 <entry>set netmask length for <type>inet</type> value</entry>
7681 <entry><literal>set_masklen('192.168.1.5/24', 16)</literal></entry>
7682 <entry><literal>192.168.1.5/16</literal></entry>
7685 <entry><literal><function>set_masklen</function>(<type>cidr</type>, <type>int</type>)</literal></entry>
7686 <entry><type>cidr</type></entry>
7687 <entry>set netmask length for <type>cidr</type> value</entry>
7688 <entry><literal>set_masklen('192.168.1.0/24'::cidr, 16)</literal></entry>
7689 <entry><literal>192.168.0.0/16</literal></entry>
7692 <entry><literal><function>text</function>(<type>inet</type>)</literal></entry>
7693 <entry><type>text</type></entry>
7694 <entry>extract IP address and netmask length as text</entry>
7695 <entry><literal>text(inet '192.168.1.5')</literal></entry>
7696 <entry><literal>192.168.1.5/32</literal></entry>
7703 Any <type>cidr</> value can be cast to <type>inet</> implicitly
7704 or explicitly; therefore, the functions shown above as operating on
7705 <type>inet</> also work on <type>cidr</> values. (Where there are
7706 separate functions for <type>inet</> and <type>cidr</>, it is because
7707 the behavior should be different for the two cases.)
7708 Also, it is permitted to cast an <type>inet</> value to <type>cidr</>.
7709 When this is done, any bits to the right of the netmask are silently zeroed
7710 to create a valid <type>cidr</> value.
7712 you can cast a text value to <type>inet</> or <type>cidr</>
7713 using normal casting syntax: for example,
7714 <literal>inet(<replaceable>expression</>)</literal> or
7715 <literal><replaceable>colname</>::cidr</literal>.
7719 <xref linkend="macaddr-functions-table"> shows the functions
7720 available for use with the <type>macaddr</type> type. The function
7721 <literal><function>trunc</function>(<type>macaddr</type>)</literal> returns a MAC
7722 address with the last 3 bytes set to zero. This can be used to
7723 associate the remaining prefix with a manufacturer.
7726 <table id="macaddr-functions-table">
7727 <title><type>macaddr</type> Functions</title>
7731 <entry>Function</entry>
7732 <entry>Return Type</entry>
7733 <entry>Description</entry>
7734 <entry>Example</entry>
7735 <entry>Result</entry>
7740 <entry><literal><function>trunc</function>(<type>macaddr</type>)</literal></entry>
7741 <entry><type>macaddr</type></entry>
7742 <entry>set last 3 bytes to zero</entry>
7743 <entry><literal>trunc(macaddr '12:34:56:78:90:ab')</literal></entry>
7744 <entry><literal>12:34:56:00:00:00</literal></entry>
7751 The <type>macaddr</type> type also supports the standard relational
7752 operators (<literal>></literal>, <literal><=</literal>, etc.) for
7753 lexicographical ordering.
7759 <sect1 id="functions-textsearch">
7760 <title>Text Search Functions and Operators</title>
7762 <indexterm zone="datatype-textsearch">
7763 <primary>full text search</primary>
7764 <secondary>functions and operators</secondary>
7767 <indexterm zone="datatype-textsearch">
7768 <primary>text search</primary>
7769 <secondary>functions and operators</secondary>
7773 <xref linkend="textsearch-operators-table">,
7774 <xref linkend="textsearch-functions-table"> and
7775 <xref linkend="textsearch-functions-debug-table">
7776 summarize the functions and operators that are provided
7777 for full text searching. See <xref linkend="textsearch"> for a detailed
7778 explanation of <productname>PostgreSQL</productname>'s text search
7782 <table id="textsearch-operators-table">
7783 <title>Text Search Operators</title>
7787 <entry>Operator</entry>
7788 <entry>Description</entry>
7789 <entry>Example</entry>
7790 <entry>Result</entry>
7795 <entry> <literal>@@</literal> </entry>
7796 <entry><type>tsvector</> matches <type>tsquery</> ?</entry>
7797 <entry><literal>to_tsvector('fat cats ate rats') @@ to_tsquery('cat & rat')</literal></entry>
7798 <entry><literal>t</literal></entry>
7801 <entry> <literal>@@@</literal> </entry>
7802 <entry>deprecated synonym for <literal>@@</></entry>
7803 <entry><literal>to_tsvector('fat cats ate rats') @@@ to_tsquery('cat & rat')</literal></entry>
7804 <entry><literal>t</literal></entry>
7807 <entry> <literal>||</literal> </entry>
7808 <entry>concatenate <type>tsvector</>s</entry>
7809 <entry><literal>'a:1 b:2'::tsvector || 'c:1 d:2 b:3'::tsvector</literal></entry>
7810 <entry><literal>'a':1 'b':2,5 'c':3 'd':4</literal></entry>
7813 <entry> <literal>&&</literal> </entry>
7814 <entry>AND <type>tsquery</>s together</entry>
7815 <entry><literal>'fat | rat'::tsquery && 'cat'::tsquery</literal></entry>
7816 <entry><literal>( 'fat' | 'rat' ) & 'cat'</literal></entry>
7819 <entry> <literal>||</literal> </entry>
7820 <entry>OR <type>tsquery</>s together</entry>
7821 <entry><literal>'fat | rat'::tsquery || 'cat'::tsquery</literal></entry>
7822 <entry><literal>( 'fat' | 'rat' ) | 'cat'</literal></entry>
7825 <entry> <literal>!!</literal> </entry>
7826 <entry>negate a <type>tsquery</></entry>
7827 <entry><literal>!! 'cat'::tsquery</literal></entry>
7828 <entry><literal>!'cat'</literal></entry>
7831 <entry> <literal>@></literal> </entry>
7832 <entry><type>tsquery</> contains another ?</entry>
7833 <entry><literal>'cat'::tsquery @> 'cat & rat'::tsquery</literal></entry>
7834 <entry><literal>f</literal></entry>
7837 <entry> <literal><@</literal> </entry>
7838 <entry><type>tsquery</> is contained in ?</entry>
7839 <entry><literal>'cat'::tsquery <@ 'cat & rat'::tsquery</literal></entry>
7840 <entry><literal>t</literal></entry>
7848 The <type>tsquery</> containment operators consider only the lexemes
7849 listed in the two queries, ignoring the combining operators.
7854 In addition to the operators shown in the table, the ordinary B-tree
7855 comparison operators (<literal>=</>, <literal><</>, etc) are defined
7856 for types <type>tsvector</> and <type>tsquery</>. These are not very
7857 useful for text searching but allow, for example, unique indexes to be
7858 built on columns of these types.
7861 <table id="textsearch-functions-table">
7862 <title>Text Search Functions</title>
7866 <entry>Function</entry>
7867 <entry>Return Type</entry>
7868 <entry>Description</entry>
7869 <entry>Example</entry>
7870 <entry>Result</entry>
7875 <entry><literal><function>to_tsvector</function>(<optional> <replaceable class="PARAMETER">config</> <type>regconfig</> , </optional> <replaceable class="PARAMETER">document</> <type>text</type>)</literal></entry>
7876 <entry><type>tsvector</type></entry>
7877 <entry>reduce document text to <type>tsvector</></entry>
7878 <entry><literal>to_tsvector('english', 'The Fat Rats')</literal></entry>
7879 <entry><literal>'fat':2 'rat':3</literal></entry>
7882 <entry><literal><function>length</function>(<type>tsvector</>)</literal></entry>
7883 <entry><type>integer</type></entry>
7884 <entry>number of lexemes in <type>tsvector</></entry>
7885 <entry><literal>length('fat:2,4 cat:3 rat:5A'::tsvector)</literal></entry>
7886 <entry><literal>3</literal></entry>
7889 <entry><literal><function>setweight</function>(<type>tsvector</>, <type>"char"</>)</literal></entry>
7890 <entry><type>tsvector</type></entry>
7891 <entry>assign weight to each element of <type>tsvector</></entry>
7892 <entry><literal>setweight('fat:2,4 cat:3 rat:5B'::tsvector, 'A')</literal></entry>
7893 <entry><literal>'cat':3A 'fat':2A,4A 'rat':5A</literal></entry>
7896 <entry><literal><function>strip</function>(<type>tsvector</>)</literal></entry>
7897 <entry><type>tsvector</type></entry>
7898 <entry>remove positions and weights from <type>tsvector</></entry>
7899 <entry><literal>strip('fat:2,4 cat:3 rat:5A'::tsvector)</literal></entry>
7900 <entry><literal>'cat' 'fat' 'rat'</literal></entry>
7903 <entry><literal><function>to_tsquery</function>(<optional> <replaceable class="PARAMETER">config</> <type>regconfig</> , </optional> <replaceable class="PARAMETER">query</> <type>text</type>)</literal></entry>
7904 <entry><type>tsquery</type></entry>
7905 <entry>normalize words and convert to <type>tsquery</></entry>
7906 <entry><literal>to_tsquery('english', 'The & Fat & Rats')</literal></entry>
7907 <entry><literal>'fat' & 'rat'</literal></entry>
7910 <entry><literal><function>plainto_tsquery</function>(<optional> <replaceable class="PARAMETER">config</> <type>regconfig</> , </optional> <replaceable class="PARAMETER">query</> <type>text</type>)</literal></entry>
7911 <entry><type>tsquery</type></entry>
7912 <entry>produce <type>tsquery</> ignoring punctuation</entry>
7913 <entry><literal>plainto_tsquery('english', 'The Fat Rats')</literal></entry>
7914 <entry><literal>'fat' & 'rat'</literal></entry>
7917 <entry><literal><function>numnode</function>(<type>tsquery</>)</literal></entry>
7918 <entry><type>integer</type></entry>
7919 <entry>number of lexemes plus operators in <type>tsquery</></entry>
7920 <entry><literal> numnode('(fat & rat) | cat'::tsquery)</literal></entry>
7921 <entry><literal>5</literal></entry>
7924 <entry><literal><function>querytree</function>(<replaceable class="PARAMETER">query</replaceable> <type>tsquery</>)</literal></entry>
7925 <entry><type>text</type></entry>
7926 <entry>get indexable part of a <type>tsquery</></entry>
7927 <entry><literal>querytree('foo & ! bar'::tsquery)</literal></entry>
7928 <entry><literal>'foo'</literal></entry>
7931 <entry><literal><function>ts_rank</function>(<optional> <replaceable class="PARAMETER">weights</replaceable> <type>float4[]</>, </optional> <replaceable class="PARAMETER">vector</replaceable> <type>tsvector</>, <replaceable class="PARAMETER">query</replaceable> <type>tsquery</> <optional>, <replaceable class="PARAMETER">normalization</replaceable> <type>integer</> </optional>)</literal></entry>
7932 <entry><type>float4</type></entry>
7933 <entry>rank document for query</entry>
7934 <entry><literal>ts_rank(textsearch, query)</literal></entry>
7935 <entry><literal>0.818</literal></entry>
7938 <entry><literal><function>ts_rank_cd</function>(<optional> <replaceable class="PARAMETER">weights</replaceable> <type>float4[]</>, </optional> <replaceable class="PARAMETER">vector</replaceable> <type>tsvector</>, <replaceable class="PARAMETER">query</replaceable> <type>tsquery</> <optional>, <replaceable class="PARAMETER">normalization</replaceable> <type>integer</> </optional>)</literal></entry>
7939 <entry><type>float4</type></entry>
7940 <entry>rank document for query using cover density</entry>
7941 <entry><literal>ts_rank_cd('{0.1, 0.2, 0.4, 1.0}', textsearch, query)</literal></entry>
7942 <entry><literal>2.01317</literal></entry>
7945 <entry><literal><function>ts_headline</function>(<optional> <replaceable class="PARAMETER">config</replaceable> <type>regconfig</>, </optional> <replaceable class="PARAMETER">document</replaceable> <type>text</>, <replaceable class="PARAMETER">query</replaceable> <type>tsquery</> <optional>, <replaceable class="PARAMETER">options</replaceable> <type>text</> </optional>)</literal></entry>
7946 <entry><type>text</type></entry>
7947 <entry>display a query match</entry>
7948 <entry><literal>ts_headline('x y z', 'z'::tsquery)</literal></entry>
7949 <entry><literal>x y <b>z</b></literal></entry>
7952 <entry><literal><function>ts_rewrite</function>(<replaceable class="PARAMETER">query</replaceable> <type>tsquery</>, <replaceable class="PARAMETER">target</replaceable> <type>tsquery</>, <replaceable class="PARAMETER">substitute</replaceable> <type>tsquery</>)</literal></entry>
7953 <entry><type>tsquery</type></entry>
7954 <entry>replace target with substitute within query</entry>
7955 <entry><literal>ts_rewrite('a & b'::tsquery, 'a'::tsquery, 'foo|bar'::tsquery)</literal></entry>
7956 <entry><literal>'b' & ( 'foo' | 'bar' )</literal></entry>
7959 <entry><literal><function>ts_rewrite</function>(<replaceable class="PARAMETER">query</replaceable> <type>tsquery</>, <replaceable class="PARAMETER">select</replaceable> <type>text</>)</literal></entry>
7960 <entry><type>tsquery</type></entry>
7961 <entry>replace using targets and substitutes from a <command>SELECT</> command</entry>
7962 <entry><literal>SELECT ts_rewrite('a & b'::tsquery, 'SELECT t,s FROM aliases')</literal></entry>
7963 <entry><literal>'b' & ( 'foo' | 'bar' )</literal></entry>
7966 <entry><literal><function>get_current_ts_config</function>()</literal></entry>
7967 <entry><type>regconfig</type></entry>
7968 <entry>get default text search configuration</entry>
7969 <entry><literal>get_current_ts_config()</literal></entry>
7970 <entry><literal>english</literal></entry>
7973 <entry><literal><function>tsvector_update_trigger</function>()</literal></entry>
7974 <entry><type>trigger</type></entry>
7975 <entry>trigger function for automatic <type>tsvector</> column update</entry>
7976 <entry><literal>CREATE TRIGGER ... tsvector_update_trigger(tsvcol, 'pg_catalog.swedish', title, body)</literal></entry>
7977 <entry><literal></literal></entry>
7980 <entry><literal><function>tsvector_update_trigger_column</function>()</literal></entry>
7981 <entry><type>trigger</type></entry>
7982 <entry>trigger function for automatic <type>tsvector</> column update</entry>
7983 <entry><literal>CREATE TRIGGER ... tsvector_update_trigger_column(tsvcol, configcol, title, body)</literal></entry>
7984 <entry><literal></literal></entry>
7985 <entry><literal></literal></entry>
7993 All the text search functions that accept an optional <type>regconfig</>
7994 argument will use the configuration specified by
7995 <xref linkend="guc-default-text-search-config">
7996 when that argument is omitted.
8002 <xref linkend="textsearch-functions-debug-table">
8003 are listed separately because they are not usually used in everyday text
8004 searching operations. They are helpful for development and debugging
8005 of new text search configurations.
8008 <table id="textsearch-functions-debug-table">
8009 <title>Text Search Debugging Functions</title>
8013 <entry>Function</entry>
8014 <entry>Return Type</entry>
8015 <entry>Description</entry>
8016 <entry>Example</entry>
8017 <entry>Result</entry>
8022 <entry><literal><function>ts_debug</function>(<optional> <replaceable class="PARAMETER">config</replaceable> <type>regconfig</>, </optional> <replaceable class="PARAMETER">document</replaceable> <type>text</>, OUT <replaceable class="PARAMETER">alias</> <type>text</>, OUT <replaceable class="PARAMETER">description</> <type>text</>, OUT <replaceable class="PARAMETER">token</> <type>text</>, OUT <replaceable class="PARAMETER">dictionaries</> <type>regdictionary[]</>, OUT <replaceable class="PARAMETER">dictionary</> <type>regdictionary</>, OUT <replaceable class="PARAMETER">lexemes</> <type>text[]</>)</literal></entry>
8023 <entry><type>setof record</type></entry>
8024 <entry>test a configuration</entry>
8025 <entry><literal>ts_debug('english', 'The Brightest supernovaes')</literal></entry>
8026 <entry><literal>(asciiword,"Word, all ASCII",The,{english_stem},english_stem,{}) ...</literal></entry>
8029 <entry><literal><function>ts_lexize</function>(<replaceable class="PARAMETER">dict</replaceable> <type>regdictionary</>, <replaceable class="PARAMETER">token</replaceable> <type>text</>)</literal></entry>
8030 <entry><type>text[]</type></entry>
8031 <entry>test a dictionary</entry>
8032 <entry><literal>ts_lexize('english_stem', 'stars')</literal></entry>
8033 <entry><literal>{star}</literal></entry>
8036 <entry><literal><function>ts_parse</function>(<replaceable class="PARAMETER">parser_name</replaceable> <type>text</>, <replaceable class="PARAMETER">document</replaceable> <type>text</>, OUT <replaceable class="PARAMETER">tokid</> <type>integer</>, OUT <replaceable class="PARAMETER">token</> <type>text</>)</literal></entry>
8037 <entry><type>setof record</type></entry>
8038 <entry>test a parser</entry>
8039 <entry><literal>ts_parse('default', 'foo - bar')</literal></entry>
8040 <entry><literal>(1,foo) ...</literal></entry>
8043 <entry><literal><function>ts_parse</function>(<replaceable class="PARAMETER">parser_oid</replaceable> <type>oid</>, <replaceable class="PARAMETER">document</replaceable> <type>text</>, OUT <replaceable class="PARAMETER">tokid</> <type>integer</>, OUT <replaceable class="PARAMETER">token</> <type>text</>)</literal></entry>
8044 <entry><type>setof record</type></entry>
8045 <entry>test a parser</entry>
8046 <entry><literal>ts_parse(3722, 'foo - bar')</literal></entry>
8047 <entry><literal>(1,foo) ...</literal></entry>
8050 <entry><literal><function>ts_token_type</function>(<replaceable class="PARAMETER">parser_name</> <type>text</>, OUT <replaceable class="PARAMETER">tokid</> <type>integer</>, OUT <replaceable class="PARAMETER">alias</> <type>text</>, OUT <replaceable class="PARAMETER">description</> <type>text</>)</literal></entry>
8051 <entry><type>setof record</type></entry>
8052 <entry>get token types defined by parser</entry>
8053 <entry><literal>ts_token_type('default')</literal></entry>
8054 <entry><literal>(1,asciiword,"Word, all ASCII") ...</literal></entry>
8057 <entry><literal><function>ts_token_type</function>(<replaceable class="PARAMETER">parser_oid</> <type>oid</>, OUT <replaceable class="PARAMETER">tokid</> <type>integer</>, OUT <replaceable class="PARAMETER">alias</> <type>text</>, OUT <replaceable class="PARAMETER">description</> <type>text</>)</literal></entry>
8058 <entry><type>setof record</type></entry>
8059 <entry>get token types defined by parser</entry>
8060 <entry><literal>ts_token_type(3722)</literal></entry>
8061 <entry><literal>(1,asciiword,"Word, all ASCII") ...</literal></entry>
8064 <entry><literal><function>ts_stat</function>(<replaceable class="PARAMETER">sqlquery</replaceable> <type>text</>, <optional> <replaceable class="PARAMETER">weights</replaceable> <type>text</>, </optional> OUT <replaceable class="PARAMETER">word</replaceable> <type>text</>, OUT <replaceable class="PARAMETER">ndoc</replaceable> <type>integer</>, OUT <replaceable class="PARAMETER">nentry</replaceable> <type>integer</>)</literal></entry>
8065 <entry><type>setof record</type></entry>
8066 <entry>get statistics of a <type>tsvector</> column</entry>
8067 <entry><literal>ts_stat('SELECT vector from apod')</literal></entry>
8068 <entry><literal>(foo,10,15) ...</literal></entry>
8077 <sect1 id="functions-xml">
8078 <title>XML Functions</title>
8081 The functions and function-like expressions described in this
8082 section operate on values of type <type>xml</type>. Check <xref
8083 linkend="datatype-xml"> for information about the <type>xml</type>
8084 type. The function-like expressions <function>xmlparse</function>
8085 and <function>xmlserialize</function> for converting to and from
8086 type <type>xml</type> are not repeated here. Use of many of these
8087 functions requires the installation to have been built
8088 with <command>configure --with-libxml</>.
8092 <title>Producing XML Content</title>
8095 A set of functions and function-like expressions are available for
8096 producing XML content from SQL data. As such, they are
8097 particularly suitable for formatting query results into XML
8098 documents for processing in client applications.
8102 <title><literal>xmlcomment</literal></title>
8105 <primary>xmlcomment</primary>
8109 <function>xmlcomment</function>(<replaceable>text</replaceable>)
8113 The function <function>xmlcomment</function> creates an XML value
8114 containing an XML comment with the specified text as content.
8115 The text cannot contain <quote><literal>--</literal></quote> or end with a
8116 <quote><literal>-</literal></quote> so that the resulting construct is a valid
8117 XML comment. If the argument is null, the result is null.
8123 SELECT xmlcomment('hello');
8133 <title><literal>xmlconcat</literal></title>
8136 <primary>xmlconcat</primary>
8140 <function>xmlconcat</function>(<replaceable>xml</replaceable><optional>, ...</optional>)
8144 The function <function>xmlconcat</function> concatenates a list
8145 of individual XML values to create a single value containing an
8146 XML content fragment. Null values are omitted; the result is
8147 only null if there are no nonnull arguments.
8153 SELECT xmlconcat('<abc/>', '<bar>foo</bar>');
8156 ----------------------
8157 <abc/><bar>foo</bar>
8162 XML declarations, if present, are combined as follows. If all
8163 argument values have the same XML version declaration, that
8164 version is used in the result, else no version is used. If all
8165 argument values have the standalone declaration value
8166 <quote>yes</quote>, then that value is used in the result. If
8167 all argument values have a standalone declaration value and at
8168 least one is <quote>no</quote>, then that is used in the result.
8169 Else the result will have no standalone declaration. If the
8170 result is determined to require a standalone declaration but no
8171 version declaration, a version declaration with version 1.0 will
8172 be used because XML requires an XML declaration to contain a
8173 version declaration. Encoding declarations are ignored and
8174 removed in all cases.
8180 SELECT xmlconcat('<?xml version="1.1"?><foo/>', '<?xml version="1.1" standalone="no"?><bar/>');
8183 -----------------------------------
8184 <?xml version="1.1"?><foo/><bar/>
8190 <title><literal>xmlelement</literal></title>
8193 <primary>xmlelement</primary>
8197 <function>xmlelement</function>(name <replaceable>name</replaceable> <optional>, xmlattributes(<replaceable>value</replaceable> <optional>AS <replaceable>attname</replaceable></optional> <optional>, ... </optional>)</optional> <optional><replaceable>, content, ...</replaceable></optional>)
8201 The <function>xmlelement</function> expression produces an XML
8202 element with the given name, attributes, and content.
8208 SELECT xmlelement(name foo);
8214 SELECT xmlelement(name foo, xmlattributes('xyz' as bar));
8220 SELECT xmlelement(name foo, xmlattributes(current_date as bar), 'cont', 'ent');
8223 -------------------------------------
8224 <foo bar="2007-01-26">content</foo>
8229 Element and attribute names that are not valid XML names are
8230 escaped by replacing the offending characters by the sequence
8231 <literal>_x<replaceable>HHHH</replaceable>_</literal>, where
8232 <replaceable>HHHH</replaceable> is the character's Unicode
8233 codepoint in hexadecimal notation. For example:
8235 SELECT xmlelement(name "foo$bar", xmlattributes('xyz' as "a&b"));
8238 ----------------------------------
8239 <foo_x0024_bar a_x0026_b="xyz"/>
8244 An explicit attribute name need not be specified if the attribute
8245 value is a column reference, in which case the column's name will
8246 be used as the attribute name by default. In other cases, the
8247 attribute must be given an explicit name. So this example is
8250 CREATE TABLE test (a xml, b xml);
8251 SELECT xmlelement(name test, xmlattributes(a, b)) FROM test;
8255 SELECT xmlelement(name test, xmlattributes('constant'), a, b) FROM test;
8256 SELECT xmlelement(name test, xmlattributes(func(a, b))) FROM test;
8261 Element content, if specified, will be formatted according to
8262 its data type. If the content is itself of type <type>xml</type>,
8263 complex XML documents can be constructed. For example:
8265 SELECT xmlelement(name foo, xmlattributes('xyz' as bar),
8266 xmlelement(name abc),
8268 xmlelement(name xyz));
8271 ----------------------------------------------
8272 <foo bar="xyz"><abc/><!--test--><xyz/></foo>
8275 Content of other types will be formatted into valid XML character
8276 data. This means in particular that the characters <, >,
8277 and & will be converted to entities. Binary data (data type
8278 <type>bytea</type>) will be represented in base64 or hex
8279 encoding, depending on the setting of the configuration parameter
8280 <xref linkend="guc-xmlbinary">. The particular behavior for
8281 individual data types is expected to evolve in order to align the
8282 SQL and PostgreSQL data types with the XML Schema specification,
8283 at which point a more precise description will appear.
8288 <title><literal>xmlforest</literal></title>
8291 <primary>xmlforest</primary>
8295 <function>xmlforest</function>(<replaceable>content</replaceable> <optional>AS <replaceable>name</replaceable></optional> <optional>, ...</optional>)
8299 The <function>xmlforest</function> expression produces an XML
8300 forest (sequence) of elements using the given names and content.
8306 SELECT xmlforest('abc' AS foo, 123 AS bar);
8309 ------------------------------
8310 <foo>abc</foo><bar>123</bar>
8313 SELECT xmlforest(table_name, column_name)
8314 FROM information_schema.columns
8315 WHERE table_schema = 'pg_catalog';
8318 -------------------------------------------------------------------------------------------
8319 <table_name>pg_authid</table_name><column_name>rolname</column_name>
8320 <table_name>pg_authid</table_name><column_name>rolsuper</column_name>
8324 As seen in the second example, the element name can be omitted if
8325 the content value is a column reference, in which case the column
8326 name is used by default. Otherwise, a name must be specified.
8330 Element names that are not valid XML names are escaped as shown
8331 for <function>xmlelement</function> above. Similarly, content
8332 data is escaped to make valid XML content, unless it is already
8333 of type <type>xml</type>.
8337 Note that XML forests are not valid XML documents if they consist
8338 of more than one element, so it might be useful to wrap
8339 <function>xmlforest</function> expressions in
8340 <function>xmlelement</function>.
8345 <title><literal>xmlpi</literal></title>
8348 <primary>xmlpi</primary>
8352 <function>xmlpi</function>(name <replaceable>target</replaceable> <optional>, <replaceable>content</replaceable></optional>)
8356 The <function>xmlpi</function> expression creates an XML
8357 processing instruction. The content, if present, must not
8358 contain the character sequence <literal>?></literal>.
8364 SELECT xmlpi(name php, 'echo "hello world";');
8367 -----------------------------
8368 <?php echo "hello world";?>
8374 <title><literal>xmlroot</literal></title>
8377 <primary>xmlroot</primary>
8381 <function>xmlroot</function>(<replaceable>xml</replaceable>, version <replaceable>text</replaceable> | no value <optional>, standalone yes|no|no value</optional>)
8385 The <function>xmlroot</function> expression alters the properties
8386 of the root node of an XML value. If a version is specified,
8387 it replaces the value in the root node's version declaration; if a
8388 standalone setting is specified, it replaces the value in the
8389 root node's standalone declaration.
8394 SELECT xmlroot(xmlparse(document '<?xml version="1.1"?><content>abc</content>'),
8395 version '1.0', standalone yes);
8398 ----------------------------------------
8399 <?xml version="1.0" standalone="yes"?>
8400 <content>abc</content>
8405 <sect3 id="functions-xml-xmlagg">
8406 <title><literal>xmlagg</literal></title>
8409 <primary>xmlagg</primary>
8413 <function>xmlagg</function>(<replaceable>xml</replaceable>)
8417 The function <function>xmlagg</function> is, unlike the other
8418 functions described here, an aggregate function. It concatenates the
8419 input values to the aggregate function call,
8420 like <function>xmlconcat</function> does.
8421 See <xref linkend="functions-aggregate"> for additional information
8422 about aggregate functions.
8428 CREATE TABLE test (y int, x xml);
8429 INSERT INTO test VALUES (1, '<foo>abc</foo>');
8430 INSERT INTO test VALUES (2, '<bar/>');
8431 SELECT xmlagg(x) FROM test;
8433 ----------------------
8434 <foo>abc</foo><bar/>
8439 To determine the order of the concatenation, something like the
8440 following approach can be used:
8443 SELECT xmlagg(x) FROM (SELECT * FROM test ORDER BY y DESC) AS tab;
8445 ----------------------
8446 <bar/><foo>abc</foo>
8449 Again, see <xref linkend="functions-aggregate"> for additional
8455 <title>XML Predicates</title>
8458 <primary>IS DOCUMENT</primary>
8462 <replaceable>xml</replaceable> IS DOCUMENT
8466 The expression <literal>IS DOCUMENT</literal> returns true if the
8467 argument XML value is a proper XML document, false if it is not
8468 (that is, it is a content fragment), or null if the argument is
8469 null. See <xref linkend="datatype-xml"> about the difference
8470 between documents and content fragments.
8475 <sect2 id="functions-xml-processing">
8476 <title>Processing XML</title>
8479 <primary>XPath</primary>
8483 To process values of data type <type>xml</type>, PostgreSQL offers
8484 the function <function>xpath</function>, which evaluates XPath 1.0
8489 <function>xpath</function>(<replaceable>xpath</replaceable>, <replaceable>xml</replaceable><optional>, <replaceable>nsarray</replaceable></optional>)
8493 The function <function>xpath</function> evaluates the XPath
8494 expression <replaceable>xpath</replaceable> against the XML value
8495 <replaceable>xml</replaceable>. It returns an array of XML values
8496 corresponding to the node set produced by the XPath expression.
8500 The second argument must be a well formed XML document. In particular,
8501 it must have a single root node element.
8505 The third argument of the function is an array of namespace
8506 mappings. This array should be a two-dimensional array with the
8507 length of the second axis being equal to 2 (i.e., it should be an
8508 array of arrays, each of which consists of exactly 2 elements).
8509 The first element of each array entry is the namespace name, the
8510 second the namespace URI.
8516 SELECT xpath('/my:a/text()', '<my:a xmlns:my="http://example.com">test</my:a>',
8517 ARRAY[ARRAY['my', 'http://example.com']]);
8527 <sect2 id="functions-xml-mapping">
8528 <title>Mapping Tables to XML</title>
8530 <indexterm zone="functions-xml-mapping">
8531 <primary>XML export</primary>
8535 The following functions map the contents of relational tables to
8536 XML values. They can be thought of as XML export functionality:
8538 table_to_xml(tbl regclass, nulls boolean, tableforest boolean, targetns text)
8539 query_to_xml(query text, nulls boolean, tableforest boolean, targetns text)
8540 cursor_to_xml(cursor refcursor, count int, nulls boolean,
8541 tableforest boolean, targetns text)
8543 The return type of each function is <type>xml</type>.
8547 <function>table_to_xml</function> maps the content of the named
8548 table, passed as parameter <parameter>tbl</parameter>. The
8549 <type>regclass</type> type accepts strings identifying tables using the
8550 usual notation, including optional schema qualifications and
8551 double quotes. <function>query_to_xml</function> executes the
8552 query whose text is passed as parameter
8553 <parameter>query</parameter> and maps the result set.
8554 <function>cursor_to_xml</function> fetches the indicated number of
8555 rows from the cursor specified by the parameter
8556 <parameter>cursor</parameter>. This variant is recommended if
8557 large tables have to be mapped, because the result value is built
8558 up in memory by each function.
8562 If <parameter>tableforest</parameter> is false, then the resulting
8563 XML document looks like this:
8567 <columnname1>data</columnname1>
8568 <columnname2>data</columnname2>
8579 If <parameter>tableforest</parameter> is true, the result is an
8580 XML content fragment that looks like this:
8583 <columnname1>data</columnname1>
8584 <columnname2>data</columnname2>
8594 If no table name is available, that is, when mapping a query or a
8595 cursor, the string <literal>table</literal> is used in the first
8596 format, <literal>row</literal> in the second format.
8600 The choice between these formats is up to the user. The first
8601 format is a proper XML document, which will be important in many
8602 applications. The second format tends to be more useful in the
8603 <function>cursor_to_xml</function> function if the result values are to be
8604 reassembled into one document later on. The functions for
8605 producing XML content discussed above, in particular
8606 <function>xmlelement</function>, can be used to alter the results
8611 The data values are mapped in the same way as described for the
8612 function <function>xmlelement</function> above.
8616 The parameter <parameter>nulls</parameter> determines whether null
8617 values should be included in the output. If true, null values in
8618 columns are represented as:
8620 <columnname xsi:nil="true"/>
8622 where <literal>xsi</literal> is the XML namespace prefix for XML
8623 Schema Instance. An appropriate namespace declaration will be
8624 added to the result value. If false, columns containing null
8625 values are simply omitted from the output.
8629 The parameter <parameter>targetns</parameter> specifies the
8630 desired XML namespace of the result. If no particular namespace
8631 is wanted, an empty string should be passed.
8635 The following functions return XML Schema documents describing the
8636 mappings performed by the corresponding functions above:
8638 table_to_xmlschema(tbl regclass, nulls boolean, tableforest boolean, targetns text)
8639 query_to_xmlschema(query text, nulls boolean, tableforest boolean, targetns text)
8640 cursor_to_xmlschema(cursor refcursor, nulls boolean, tableforest boolean, targetns text)
8642 It is essential that the same parameters are passed in order to
8643 obtain matching XML data mappings and XML Schema documents.
8647 The following functions produce XML data mappings and the
8648 corresponding XML Schema in one document (or forest), linked
8649 together. They can be useful where self-contained and
8650 self-describing results are wanted:
8652 table_to_xml_and_xmlschema(tbl regclass, nulls boolean, tableforest boolean, targetns text)
8653 query_to_xml_and_xmlschema(query text, nulls boolean, tableforest boolean, targetns text)
8658 In addition, the following functions are available to produce
8659 analogous mappings of entire schemas or the entire current
8662 schema_to_xml(schema name, nulls boolean, tableforest boolean, targetns text)
8663 schema_to_xmlschema(schema name, nulls boolean, tableforest boolean, targetns text)
8664 schema_to_xml_and_xmlschema(schema name, nulls boolean, tableforest boolean, targetns text)
8666 database_to_xml(nulls boolean, tableforest boolean, targetns text)
8667 database_to_xmlschema(nulls boolean, tableforest boolean, targetns text)
8668 database_to_xml_and_xmlschema(nulls boolean, tableforest boolean, targetns text)
8671 Note that these potentially produce a lot of data, which needs to
8672 be built up in memory. When requesting content mappings of large
8673 schemas or databases, it might be worthwhile to consider mapping the
8674 tables separately instead, possibly even through a cursor.
8678 The result of a schema content mapping looks like this:
8689 </schemaname>]]></screen>
8691 where the format of a table mapping depends on the
8692 <parameter>tableforest</parameter> parameter as explained above.
8696 The result of a database content mapping looks like this:
8711 </dbname>]]></screen>
8713 where the schema mapping is as above.
8717 As an example of using the output produced by these functions,
8718 <xref linkend="xslt-xml-html"> shows an XSLT stylesheet that
8719 converts the output of
8720 <function>table_to_xml_and_xmlschema</function> to an HTML
8721 document containing a tabular rendition of the table data. In a
8722 similar manner, the results from these functions can be
8723 converted into other XML-based formats.
8726 <figure id="xslt-xml-html">
8727 <title>XSLT stylesheet for converting SQL/XML output to HTML</title>
8728 <programlisting><![CDATA[
8729 <?xml version="1.0"?>
8730 <xsl:stylesheet version="1.0"
8731 xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
8732 xmlns:xsd="http://www.w3.org/2001/XMLSchema"
8733 xmlns="http://www.w3.org/1999/xhtml"
8736 <xsl:output method="xml"
8737 doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
8738 doctype-public="-//W3C/DTD XHTML 1.0 Strict//EN"
8741 <xsl:template match="/*">
8742 <xsl:variable name="schema" select="//xsd:schema"/>
8743 <xsl:variable name="tabletypename"
8744 select="$schema/xsd:element[@name=name(current())]/@type"/>
8745 <xsl:variable name="rowtypename"
8746 select="$schema/xsd:complexType[@name=$tabletypename]/xsd:sequence/xsd:element[@name='row']/@type"/>
8750 <title><xsl:value-of select="name(current())"/></title>
8755 <xsl:for-each select="$schema/xsd:complexType[@name=$rowtypename]/xsd:sequence/xsd:element/@name">
8756 <th><xsl:value-of select="."/></th>
8760 <xsl:for-each select="row">
8762 <xsl:for-each select="*">
8763 <td><xsl:value-of select="."/></td>
8773 ]]></programlisting>
8779 <sect1 id="functions-sequence">
8780 <title>Sequence Manipulation Functions</title>
8783 <primary>sequence</primary>
8786 <primary>nextval</primary>
8789 <primary>currval</primary>
8792 <primary>lastval</primary>
8795 <primary>setval</primary>
8799 This section describes <productname>PostgreSQL</productname>'s
8800 functions for operating on <firstterm>sequence objects</firstterm>.
8801 Sequence objects (also called sequence generators or just
8802 sequences) are special single-row tables created with <xref
8803 linkend="sql-createsequence" endterm="sql-createsequence-title">.
8804 A sequence object is usually used to generate unique identifiers
8805 for rows of a table. The sequence functions, listed in <xref
8806 linkend="functions-sequence-table">, provide simple, multiuser-safe
8807 methods for obtaining successive sequence values from sequence
8811 <table id="functions-sequence-table">
8812 <title>Sequence Functions</title>
8815 <row><entry>Function</entry> <entry>Return Type</entry> <entry>Description</entry></row>
8820 <entry><literal><function>currval</function>(<type>regclass</type>)</literal></entry>
8821 <entry><type>bigint</type></entry>
8822 <entry>Return value most recently obtained with
8823 <function>nextval</function> for specified sequence</entry>
8826 <entry><literal><function>lastval</function>()</literal></entry>
8827 <entry><type>bigint</type></entry>
8828 <entry>Return value most recently obtained with
8829 <function>nextval</function> for any sequence</entry>
8832 <entry><literal><function>nextval</function>(<type>regclass</type>)</literal></entry>
8833 <entry><type>bigint</type></entry>
8834 <entry>Advance sequence and return new value</entry>
8837 <entry><literal><function>setval</function>(<type>regclass</type>, <type>bigint</type>)</literal></entry>
8838 <entry><type>bigint</type></entry>
8839 <entry>Set sequence's current value</entry>
8842 <entry><literal><function>setval</function>(<type>regclass</type>, <type>bigint</type>, <type>boolean</type>)</literal></entry>
8843 <entry><type>bigint</type></entry>
8844 <entry>Set sequence's current value and <literal>is_called</literal> flag</entry>
8851 The sequence to be operated on by a sequence function is specified by
8852 a <type>regclass</> argument, which is simply the OID of the sequence in the
8853 <structname>pg_class</> system catalog. You do not have to look up the
8854 OID by hand, however, since the <type>regclass</> data type's input
8855 converter will do the work for you. Just write the sequence name enclosed
8856 in single quotes so that it looks like a literal constant. For
8857 compatibility with the handling of ordinary
8858 <acronym>SQL</acronym> names, the string will be converted to lowercase
8859 unless it contains double quotes around the sequence name. Thus:
8861 nextval('foo') <lineannotation>operates on sequence <literal>foo</literal></>
8862 nextval('FOO') <lineannotation>operates on sequence <literal>foo</literal></>
8863 nextval('"Foo"') <lineannotation>operates on sequence <literal>Foo</literal></>
8865 The sequence name can be schema-qualified if necessary:
8867 nextval('myschema.foo') <lineannotation>operates on <literal>myschema.foo</literal></>
8868 nextval('"myschema".foo') <lineannotation>same as above</lineannotation>
8869 nextval('foo') <lineannotation>searches search path for <literal>foo</literal></>
8871 See <xref linkend="datatype-oid"> for more information about
8877 Before <productname>PostgreSQL</productname> 8.1, the arguments of the
8878 sequence functions were of type <type>text</>, not <type>regclass</>, and
8879 the above-described conversion from a text string to an OID value would
8880 happen at run time during each call. For backwards compatibility, this
8881 facility still exists, but internally it is now handled as an implicit
8882 coercion from <type>text</> to <type>regclass</> before the function is
8887 When you write the argument of a sequence function as an unadorned
8888 literal string, it becomes a constant of type <type>regclass</>.
8889 Since this is really just an OID, it will track the originally
8890 identified sequence despite later renaming, schema reassignment,
8891 etc. This <quote>early binding</> behavior is usually desirable for
8892 sequence references in column defaults and views. But sometimes you might
8893 want <quote>late binding</> where the sequence reference is resolved
8894 at run time. To get late-binding behavior, force the constant to be
8895 stored as a <type>text</> constant instead of <type>regclass</>:
8897 nextval('foo'::text) <lineannotation><literal>foo</literal> is looked up at runtime</>
8899 Note that late binding was the only behavior supported in
8900 <productname>PostgreSQL</productname> releases before 8.1, so you
8901 might need to do this to preserve the semantics of old applications.
8905 Of course, the argument of a sequence function can be an expression
8906 as well as a constant. If it is a text expression then the implicit
8907 coercion will result in a run-time lookup.
8912 The available sequence functions are:
8916 <term><function>nextval</function></term>
8919 Advance the sequence object to its next value and return that
8920 value. This is done atomically: even if multiple sessions
8921 execute <function>nextval</function> concurrently, each will safely receive
8922 a distinct sequence value.
8928 <term><function>currval</function></term>
8931 Return the value most recently obtained by <function>nextval</function>
8932 for this sequence in the current session. (An error is
8933 reported if <function>nextval</function> has never been called for this
8934 sequence in this session.) Because this is returning
8935 a session-local value, it gives a predictable answer whether or not
8936 other sessions have executed <function>nextval</function> since the
8937 current session did.
8943 <term><function>lastval</function></term>
8946 Return the value most recently returned by
8947 <function>nextval</> in the current session. This function is
8948 identical to <function>currval</function>, except that instead
8949 of taking the sequence name as an argument it fetches the
8950 value of the last sequence used by <function>nextval</function>
8951 in the current session. It is an error to call
8952 <function>lastval</function> if <function>nextval</function>
8953 has not yet been called in the current session.
8959 <term><function>setval</function></term>
8962 Reset the sequence object's counter value. The two-parameter
8963 form sets the sequence's <literal>last_value</literal> field to the
8964 specified value and sets its <literal>is_called</literal> field to
8965 <literal>true</literal>, meaning that the next
8966 <function>nextval</function> will advance the sequence before
8967 returning a value. The value reported by <function>currval</> is
8968 also set to the specified value. In the three-parameter form,
8969 <literal>is_called</literal> can be set to either <literal>true</literal>
8970 or <literal>false</literal>. <literal>true</> has the same effect as
8971 the two-parameter form. If it is set to <literal>false</literal>, the
8972 next <function>nextval</function> will return exactly the specified
8973 value, and sequence advancement commences with the following
8974 <function>nextval</function>. Furthermore, the value reported by
8975 <function>currval</> is not changed in this case (this is a change
8976 from pre-8.3 behavior). For example,
8979 SELECT setval('foo', 42); <lineannotation>Next <function>nextval</> will return 43</lineannotation>
8980 SELECT setval('foo', 42, true); <lineannotation>Same as above</lineannotation>
8981 SELECT setval('foo', 42, false); <lineannotation>Next <function>nextval</> will return 42</lineannotation>
8984 The result returned by <function>setval</function> is just the value of its
8993 If a sequence object has been created with default parameters,
8994 successive <function>nextval</function> calls will return successive values
8995 beginning with 1. Other behaviors can be obtained by using
8996 special parameters in the <xref linkend="sql-createsequence" endterm="sql-createsequence-title"> command;
8997 see its command reference page for more information.
9002 To avoid blocking concurrent transactions that obtain numbers from the
9003 same sequence, a <function>nextval</function> operation is never rolled back;
9004 that is, once a value has been fetched it is considered used, even if the
9005 transaction that did the <function>nextval</function> later aborts. This means
9006 that aborted transactions might leave unused <quote>holes</quote> in the
9007 sequence of assigned values. <function>setval</function> operations are never
9008 rolled back, either.
9015 <sect1 id="functions-conditional">
9016 <title>Conditional Expressions</title>
9019 <primary>CASE</primary>
9023 <primary>conditional expression</primary>
9027 This section describes the <acronym>SQL</acronym>-compliant conditional expressions
9028 available in <productname>PostgreSQL</productname>.
9033 If your needs go beyond the capabilities of these conditional
9034 expressions, you might want to consider writing a stored procedure
9035 in a more expressive programming language.
9040 <title><literal>CASE</></title>
9043 The <acronym>SQL</acronym> <token>CASE</token> expression is a
9044 generic conditional expression, similar to if/else statements in
9045 other programming languages:
9048 CASE WHEN <replaceable>condition</replaceable> THEN <replaceable>result</replaceable>
9049 <optional>WHEN ...</optional>
9050 <optional>ELSE <replaceable>result</replaceable></optional>
9054 <token>CASE</token> clauses can be used wherever
9055 an expression is valid. Each <replaceable>condition</replaceable> is an
9056 expression that returns a <type>boolean</type> result. If the condition's
9057 result is true, the value of the <token>CASE</token> expression is the
9058 <replaceable>result</replaceable> that follows the condition, and the
9059 remainder of the <token>CASE</token> expression is not processed. If the
9060 condition's result is not true, any subsequent <token>WHEN</token> clauses
9061 are examined in the same manner. If no <token>WHEN</token>
9062 <replaceable>condition</replaceable> yields true, the value of the
9063 <token>CASE</> expression is the <replaceable>result</replaceable> of the
9064 <token>ELSE</token> clause. If the <token>ELSE</token> clause is
9065 omitted and no condition is true, the result is null.
9081 CASE WHEN a=1 THEN 'one'
9096 The data types of all the <replaceable>result</replaceable>
9097 expressions must be convertible to a single output type.
9098 See <xref linkend="typeconv-union-case"> for more details.
9102 There is a <quote>simple</> form of <token>CASE</token> expression
9103 that is a variant of the general form above:
9106 CASE <replaceable>expression</replaceable>
9107 WHEN <replaceable>value</replaceable> THEN <replaceable>result</replaceable>
9108 <optional>WHEN ...</optional>
9109 <optional>ELSE <replaceable>result</replaceable></optional>
9114 <replaceable>expression</replaceable> is computed, then compared to
9115 each of the <replaceable>value</replaceable> expressions in the
9116 <token>WHEN</token> clauses until one is found that is equal to it. If
9117 no match is found, the <replaceable>result</replaceable> of the
9118 <token>ELSE</token> clause (or a null value) is returned. This is similar
9119 to the <function>switch</function> statement in C.
9123 The example above can be written using the simple
9124 <token>CASE</token> syntax:
9127 CASE a WHEN 1 THEN 'one'
9142 A <token>CASE</token> expression does not evaluate any subexpressions
9143 that are not needed to determine the result. For example, this is a
9144 possible way of avoiding a division-by-zero failure:
9146 SELECT ... WHERE CASE WHEN x <> 0 THEN y/x > 1.5 ELSE false END;
9152 <title><literal>COALESCE</></title>
9155 <primary>COALESCE</primary>
9159 <primary>NVL</primary>
9163 <primary>IFNULL</primary>
9167 <function>COALESCE</function>(<replaceable>value</replaceable> <optional>, ...</optional>)
9171 The <function>COALESCE</function> function returns the first of its
9172 arguments that is not null. Null is returned only if all arguments
9173 are null. It is often used to substitute a default value for
9174 null values when data is retrieved for display, for example:
9176 SELECT COALESCE(description, short_description, '(none)') ...
9181 Like a <token>CASE</token> expression, <function>COALESCE</function> only
9182 evaluates the arguments that are needed to determine the result;
9183 that is, arguments to the right of the first non-null argument are
9184 not evaluated. This SQL-standard function provides capabilities similar
9185 to <function>NVL</> and <function>IFNULL</>, which are used in some other
9191 <title><literal>NULLIF</></title>
9194 <primary>NULLIF</primary>
9198 <function>NULLIF</function>(<replaceable>value1</replaceable>, <replaceable>value2</replaceable>)
9202 The <function>NULLIF</function> function returns a null value if
9203 <replaceable>value1</replaceable> equals <replaceable>value2</replaceable>;
9204 otherwise it returns <replaceable>value1</replaceable>.
9205 This can be used to perform the inverse operation of the
9206 <function>COALESCE</function> example given above:
9208 SELECT NULLIF(value, '(none)') ...
9212 In this example, if <literal>value</literal> is <literal>(none)</>,
9213 null is returned, otherwise the value of <literal>value</literal>
9220 <title><literal>GREATEST</literal> and <literal>LEAST</literal></title>
9223 <primary>GREATEST</primary>
9226 <primary>LEAST</primary>
9230 <function>GREATEST</function>(<replaceable>value</replaceable> <optional>, ...</optional>)
9233 <function>LEAST</function>(<replaceable>value</replaceable> <optional>, ...</optional>)
9237 The <function>GREATEST</> and <function>LEAST</> functions select the
9238 largest or smallest value from a list of any number of expressions.
9239 The expressions must all be convertible to a common data type, which
9240 will be the type of the result
9241 (see <xref linkend="typeconv-union-case"> for details). NULL values
9242 in the list are ignored. The result will be NULL only if all the
9243 expressions evaluate to NULL.
9247 Note that <function>GREATEST</> and <function>LEAST</> are not in
9248 the SQL standard, but are a common extension. Some other databases
9249 make them return NULL if any argument is NULL, rather than only when
9255 <sect1 id="functions-array">
9256 <title>Array Functions and Operators</title>
9259 <xref linkend="array-operators-table"> shows the operators
9260 available for array types.
9263 <table id="array-operators-table">
9264 <title>Array Operators</title>
9268 <entry>Operator</entry>
9269 <entry>Description</entry>
9270 <entry>Example</entry>
9271 <entry>Result</entry>
9276 <entry> <literal>=</literal> </entry>
9277 <entry>equal</entry>
9278 <entry><literal>ARRAY[1.1,2.1,3.1]::int[] = ARRAY[1,2,3]</literal></entry>
9279 <entry><literal>t</literal></entry>
9283 <entry> <literal><></literal> </entry>
9284 <entry>not equal</entry>
9285 <entry><literal>ARRAY[1,2,3] <> ARRAY[1,2,4]</literal></entry>
9286 <entry><literal>t</literal></entry>
9290 <entry> <literal><</literal> </entry>
9291 <entry>less than</entry>
9292 <entry><literal>ARRAY[1,2,3] < ARRAY[1,2,4]</literal></entry>
9293 <entry><literal>t</literal></entry>
9297 <entry> <literal>></literal> </entry>
9298 <entry>greater than</entry>
9299 <entry><literal>ARRAY[1,4,3] > ARRAY[1,2,4]</literal></entry>
9300 <entry><literal>t</literal></entry>
9304 <entry> <literal><=</literal> </entry>
9305 <entry>less than or equal</entry>
9306 <entry><literal>ARRAY[1,2,3] <= ARRAY[1,2,3]</literal></entry>
9307 <entry><literal>t</literal></entry>
9311 <entry> <literal>>=</literal> </entry>
9312 <entry>greater than or equal</entry>
9313 <entry><literal>ARRAY[1,4,3] >= ARRAY[1,4,3]</literal></entry>
9314 <entry><literal>t</literal></entry>
9318 <entry> <literal>@></literal> </entry>
9319 <entry>contains</entry>
9320 <entry><literal>ARRAY[1,4,3] @> ARRAY[3,1]</literal></entry>
9321 <entry><literal>t</literal></entry>
9325 <entry> <literal><@</literal> </entry>
9326 <entry>is contained by</entry>
9327 <entry><literal>ARRAY[2,7] <@ ARRAY[1,7,4,2,6]</literal></entry>
9328 <entry><literal>t</literal></entry>
9332 <entry> <literal>&&</literal> </entry>
9333 <entry>overlap (have elements in common)</entry>
9334 <entry><literal>ARRAY[1,4,3] && ARRAY[2,1]</literal></entry>
9335 <entry><literal>t</literal></entry>
9339 <entry> <literal>||</literal> </entry>
9340 <entry>array-to-array concatenation</entry>
9341 <entry><literal>ARRAY[1,2,3] || ARRAY[4,5,6]</literal></entry>
9342 <entry><literal>{1,2,3,4,5,6}</literal></entry>
9346 <entry> <literal>||</literal> </entry>
9347 <entry>array-to-array concatenation</entry>
9348 <entry><literal>ARRAY[1,2,3] || ARRAY[[4,5,6],[7,8,9]]</literal></entry>
9349 <entry><literal>{{1,2,3},{4,5,6},{7,8,9}}</literal></entry>
9353 <entry> <literal>||</literal> </entry>
9354 <entry>element-to-array concatenation</entry>
9355 <entry><literal>3 || ARRAY[4,5,6]</literal></entry>
9356 <entry><literal>{3,4,5,6}</literal></entry>
9360 <entry> <literal>||</literal> </entry>
9361 <entry>array-to-element concatenation</entry>
9362 <entry><literal>ARRAY[4,5,6] || 7</literal></entry>
9363 <entry><literal>{4,5,6,7}</literal></entry>
9370 Array comparisons compare the array contents element-by-element,
9371 using the default B-Tree comparison function for the element data type.
9372 In multidimensional arrays the elements are visited in row-major order
9373 (last subscript varies most rapidly).
9374 If the contents of two arrays are equal but the dimensionality is
9375 different, the first difference in the dimensionality information
9376 determines the sort order. (This is a change from versions of
9377 <productname>PostgreSQL</> prior to 8.2: older versions would claim
9378 that two arrays with the same contents were equal, even if the
9379 number of dimensions or subscript ranges were different.)
9383 See <xref linkend="arrays"> for more details about array operator
9388 <xref linkend="array-functions-table"> shows the functions
9389 available for use with array types. See <xref linkend="arrays">
9390 for more information and examples of the use of these functions.
9394 <primary>array_append</primary>
9397 <primary>array_cat</primary>
9400 <primary>array_ndims</primary>
9403 <primary>array_dims</primary>
9406 <primary>array_fill</primary>
9409 <primary>array_length</primary>
9412 <primary>array_lower</primary>
9415 <primary>array_prepend</primary>
9418 <primary>array_to_string</primary>
9421 <primary>array_upper</primary>
9424 <primary>string_to_array</primary>
9427 <primary>unnest</primary>
9430 <table id="array-functions-table">
9431 <title>Array Functions</title>
9435 <entry>Function</entry>
9436 <entry>Return Type</entry>
9437 <entry>Description</entry>
9438 <entry>Example</entry>
9439 <entry>Result</entry>
9446 <function>array_append</function>(<type>anyarray</type>, <type>anyelement</type>)
9449 <entry><type>anyarray</type></entry>
9450 <entry>append an element to the end of an array</entry>
9451 <entry><literal>array_append(ARRAY[1,2], 3)</literal></entry>
9452 <entry><literal>{1,2,3}</literal></entry>
9457 <function>array_cat</function>(<type>anyarray</type>, <type>anyarray</type>)
9460 <entry><type>anyarray</type></entry>
9461 <entry>concatenate two arrays</entry>
9462 <entry><literal>array_cat(ARRAY[1,2,3], ARRAY[4,5])</literal></entry>
9463 <entry><literal>{1,2,3,4,5}</literal></entry>
9468 <function>array_ndims</function>(<type>anyarray</type>)
9471 <entry><type>int</type></entry>
9472 <entry>returns the number of dimensions of the array</entry>
9473 <entry><literal>array_ndims(ARRAY[[1,2,3], [4,5,6]])</literal></entry>
9474 <entry><literal>2</literal></entry>
9479 <function>array_dims</function>(<type>anyarray</type>)
9482 <entry><type>text</type></entry>
9483 <entry>returns a text representation of array's dimensions</entry>
9484 <entry><literal>array_dims(ARRAY[[1,2,3], [4,5,6]])</literal></entry>
9485 <entry><literal>[1:2][1:3]</literal></entry>
9490 <function>array_fill</function>(<type>anyelement</type>, <type>int[]</type>,
9491 <optional>, <type>int[]</type></optional>)
9494 <entry><type>anyarray</type></entry>
9495 <entry>returns an array initialized with supplied value and
9496 dimensions, optionally with lower bounds other than 1</entry>
9497 <entry><literal>array_fill(7, ARRAY[3], ARRAY[2])</literal></entry>
9498 <entry><literal>[2:4]={7,7,7}</literal></entry>
9503 <function>array_length</function>(<type>anyarray</type>, <type>int</type>)
9506 <entry><type>int</type></entry>
9507 <entry>returns the length of the requested array dimension</entry>
9508 <entry><literal>array_length(array[1,2,3], 1)</literal></entry>
9509 <entry><literal>3</literal></entry>
9514 <function>array_lower</function>(<type>anyarray</type>, <type>int</type>)
9517 <entry><type>int</type></entry>
9518 <entry>returns lower bound of the requested array dimension</entry>
9519 <entry><literal>array_lower('[0:2]={1,2,3}'::int[], 1)</literal></entry>
9520 <entry><literal>0</literal></entry>
9525 <function>array_prepend</function>(<type>anyelement</type>, <type>anyarray</type>)
9528 <entry><type>anyarray</type></entry>
9529 <entry>append an element to the beginning of an array</entry>
9530 <entry><literal>array_prepend(1, ARRAY[2,3])</literal></entry>
9531 <entry><literal>{1,2,3}</literal></entry>
9536 <function>array_to_string</function>(<type>anyarray</type>, <type>text</type>)
9539 <entry><type>text</type></entry>
9540 <entry>concatenates array elements using supplied delimiter</entry>
9541 <entry><literal>array_to_string(ARRAY[1, 2, 3], '~^~')</literal></entry>
9542 <entry><literal>1~^~2~^~3</literal></entry>
9547 <function>array_upper</function>(<type>anyarray</type>, <type>int</type>)
9550 <entry><type>int</type></entry>
9551 <entry>returns upper bound of the requested array dimension</entry>
9552 <entry><literal>array_upper(ARRAY[1,2,3,4], 1)</literal></entry>
9553 <entry><literal>4</literal></entry>
9558 <function>string_to_array</function>(<type>text</type>, <type>text</type>)
9561 <entry><type>text[]</type></entry>
9562 <entry>splits string into array elements using supplied delimiter</entry>
9563 <entry><literal>string_to_array('xx~^~yy~^~zz', '~^~')</literal></entry>
9564 <entry><literal>{xx,yy,zz}</literal></entry>
9569 <function>unnest</function>(<type>anyarray</type>)
9572 <entry><type>setof anyelement</type></entry>
9573 <entry>expand an array to a set of rows</entry>
9574 <entry><literal>unnest(ARRAY[1,2])</literal></entry>
9575 <entry><literal>1</literal><para><literal>2</literal></para> (2 rows)</entry>
9582 See also <xref linkend="functions-aggregate"> about the aggregate
9583 function <function>array_agg</function> for use with arrays.
9587 <sect1 id="functions-aggregate">
9588 <title>Aggregate Functions</title>
9590 <indexterm zone="functions-aggregate">
9591 <primary>aggregate function</primary>
9592 <secondary>built-in</secondary>
9596 <firstterm>Aggregate functions</firstterm> compute a single result
9597 from a set of input values. The built-in aggregate functions
9599 <xref linkend="functions-aggregate-table"> and
9600 <xref linkend="functions-aggregate-statistics-table">.
9601 The special syntax considerations for aggregate
9602 functions are explained in <xref linkend="syntax-aggregates">.
9603 Consult <xref linkend="tutorial-agg"> for additional introductory
9607 <table id="functions-aggregate-table">
9608 <title>General-Purpose Aggregate Functions</title>
9613 <entry>Function</entry>
9614 <entry>Argument Type</entry>
9615 <entry>Return Type</entry>
9616 <entry>Description</entry>
9624 <primary>array_agg</primary>
9626 <function>array_agg(<replaceable class="parameter">expression</replaceable>)</function>
9632 array of the argument type
9634 <entry>input values concatenated into an array</entry>
9640 <primary>average</primary>
9642 <function>avg(<replaceable class="parameter">expression</replaceable>)</function>
9645 <type>smallint</type>, <type>int</type>,
9646 <type>bigint</type>, <type>real</type>, <type>double
9647 precision</type>, <type>numeric</type>, or <type>interval</type>
9650 <type>numeric</type> for any integer-type argument,
9651 <type>double precision</type> for a floating-point argument,
9652 otherwise the same as the argument data type
9654 <entry>the average (arithmetic mean) of all input values</entry>
9660 <primary>bit_and</primary>
9662 <function>bit_and(<replaceable class="parameter">expression</replaceable>)</function>
9665 <type>smallint</type>, <type>int</type>, <type>bigint</type>, or
9669 same as argument data type
9671 <entry>the bitwise AND of all non-null input values, or null if none</entry>
9677 <primary>bit_or</primary>
9679 <function>bit_or(<replaceable class="parameter">expression</replaceable>)</function>
9682 <type>smallint</type>, <type>int</type>, <type>bigint</type>, or
9686 same as argument data type
9688 <entry>the bitwise OR of all non-null input values, or null if none</entry>
9694 <primary>bool_and</primary>
9696 <function>bool_and(<replaceable class="parameter">expression</replaceable>)</function>
9704 <entry>true if all input values are true, otherwise false</entry>
9710 <primary>bool_or</primary>
9712 <function>bool_or(<replaceable class="parameter">expression</replaceable>)</function>
9720 <entry>true if at least one input value is true, otherwise false</entry>
9724 <entry><function>count(*)</function></entry>
9726 <entry><type>bigint</type></entry>
9727 <entry>number of input rows</entry>
9731 <entry><function>count(<replaceable class="parameter">expression</replaceable>)</function></entry>
9733 <entry><type>bigint</type></entry>
9735 number of input rows for which the value of <replaceable
9736 class="parameter">expression</replaceable> is not null
9743 <primary>every</primary>
9745 <function>every(<replaceable class="parameter">expression</replaceable>)</function>
9753 <entry>equivalent to <function>bool_and</function></entry>
9757 <entry><function>max(<replaceable class="parameter">expression</replaceable>)</function></entry>
9758 <entry>any array, numeric, string, or date/time type</entry>
9759 <entry>same as argument type</entry>
9761 maximum value of <replaceable
9762 class="parameter">expression</replaceable> across all input
9768 <entry><function>min(<replaceable class="parameter">expression</replaceable>)</function></entry>
9769 <entry>any array, numeric, string, or date/time type</entry>
9770 <entry>same as argument type</entry>
9772 minimum value of <replaceable
9773 class="parameter">expression</replaceable> across all input
9779 <entry><function>sum(<replaceable class="parameter">expression</replaceable>)</function></entry>
9781 <type>smallint</type>, <type>int</type>,
9782 <type>bigint</type>, <type>real</type>, <type>double
9783 precision</type>, <type>numeric</type>, or
9784 <type>interval</type>
9787 <type>bigint</type> for <type>smallint</type> or
9788 <type>int</type> arguments, <type>numeric</type> for
9789 <type>bigint</type> arguments, <type>double precision</type>
9790 for floating-point arguments, otherwise the same as the
9793 <entry>sum of <replaceable class="parameter">expression</replaceable> across all input values</entry>
9799 <primary>xmlagg</primary>
9801 <function>xmlagg(<replaceable class="parameter">expression</replaceable>)</function>
9809 <entry>concatenation of XML values (see also <xref linkend="functions-xml-xmlagg">)</entry>
9816 It should be noted that except for <function>count</function>,
9817 these functions return a null value when no rows are selected. In
9818 particular, <function>sum</function> of no rows returns null, not
9819 zero as one might expect, and <function>array_agg</function>
9820 returns null rather than an empty array when there are no input
9821 rows. The <function>coalesce</function> function can be used to
9822 substitute zero or an empty array for null when necessary.
9827 <primary>ANY</primary>
9830 <primary>SOME</primary>
9833 Boolean aggregates <function>bool_and</function> and
9834 <function>bool_or</function> correspond to standard SQL aggregates
9835 <function>every</function> and <function>any</function> or
9836 <function>some</function>.
9837 As for <function>any</function> and <function>some</function>,
9838 it seems that there is an ambiguity built into the standard syntax:
9840 SELECT b1 = ANY((SELECT b2 FROM t2 ...)) FROM t1 ...;
9842 Here <function>ANY</function> can be considered either as introducing
9843 a subquery, or as being an aggregate function, if the sub-select
9844 returns one row with a boolean value.
9845 Thus the standard name cannot be given to these aggregates.
9851 Users accustomed to working with other SQL database management
9852 systems might be disappointed by the performance of the
9853 <function>count</function> aggregate when it is applied to the
9854 entire table. A query like:
9856 SELECT count(*) FROM sometable;
9858 will be executed by <productname>PostgreSQL</productname> using a
9859 sequential scan of the entire table.
9864 The aggregate functions <function>array_agg</function>
9865 and <function>xmlagg</function>, as well as similar user-defined
9866 aggregate functions, produce meaningfully different result values
9867 depending on the order of the input values. In the current
9868 implementation, the order of the input is in principle unspecified.
9869 Supplying the input values from a sorted subquery
9870 will usually work, however. For example:
9873 SELECT xmlagg(x) FROM (SELECT x FROM test ORDER BY y DESC) AS tab;
9876 But this syntax is not allowed in the SQL standard, and is
9877 not portable to other database systems. A future version of
9878 <productname>PostgreSQL</> might provide an additional feature to control
9879 the order in a better-defined way (<literal>xmlagg(expr ORDER BY expr, expr,
9884 <xref linkend="functions-aggregate-statistics-table"> shows
9885 aggregate functions typically used in statistical analysis.
9886 (These are separated out merely to avoid cluttering the listing
9887 of more-commonly-used aggregates.) Where the description mentions
9888 <replaceable class="parameter">N</replaceable>, it means the
9889 number of input rows for which all the input expressions are non-null.
9890 In all cases, null is returned if the computation is meaningless,
9891 for example when <replaceable class="parameter">N</replaceable> is zero.
9895 <primary>statistics</primary>
9898 <primary>linear regression</primary>
9901 <table id="functions-aggregate-statistics-table">
9902 <title>Aggregate Functions for Statistics</title>
9907 <entry>Function</entry>
9908 <entry>Argument Type</entry>
9909 <entry>Return Type</entry>
9910 <entry>Description</entry>
9919 <primary>correlation</primary>
9921 <function>corr(<replaceable class="parameter">Y</replaceable>, <replaceable class="parameter">X</replaceable>)</function>
9924 <type>double precision</type>
9927 <type>double precision</type>
9929 <entry>correlation coefficient</entry>
9935 <primary>covariance</primary>
9936 <secondary>population</secondary>
9938 <function>covar_pop(<replaceable class="parameter">Y</replaceable>, <replaceable class="parameter">X</replaceable>)</function>
9941 <type>double precision</type>
9944 <type>double precision</type>
9946 <entry>population covariance</entry>
9952 <primary>covariance</primary>
9953 <secondary>sample</secondary>
9955 <function>covar_samp(<replaceable class="parameter">Y</replaceable>, <replaceable class="parameter">X</replaceable>)</function>
9958 <type>double precision</type>
9961 <type>double precision</type>
9963 <entry>sample covariance</entry>
9968 <function>regr_avgx(<replaceable class="parameter">Y</replaceable>, <replaceable class="parameter">X</replaceable>)</function>
9971 <type>double precision</type>
9974 <type>double precision</type>
9976 <entry>average of the independent variable
9977 (<literal>sum(<replaceable class="parameter">X</replaceable>)/<replaceable class="parameter">N</replaceable></literal>)</entry>
9982 <function>regr_avgy(<replaceable class="parameter">Y</replaceable>, <replaceable class="parameter">X</replaceable>)</function>
9985 <type>double precision</type>
9988 <type>double precision</type>
9990 <entry>average of the dependent variable
9991 (<literal>sum(<replaceable class="parameter">Y</replaceable>)/<replaceable class="parameter">N</replaceable></literal>)</entry>
9996 <function>regr_count(<replaceable class="parameter">Y</replaceable>, <replaceable class="parameter">X</replaceable>)</function>
9999 <type>double precision</type>
10002 <type>bigint</type>
10004 <entry>number of input rows in which both expressions are nonnull</entry>
10010 <primary>regression intercept</primary>
10012 <function>regr_intercept(<replaceable class="parameter">Y</replaceable>, <replaceable class="parameter">X</replaceable>)</function>
10015 <type>double precision</type>
10018 <type>double precision</type>
10020 <entry>y-intercept of the least-squares-fit linear equation
10021 determined by the (<replaceable
10022 class="parameter">X</replaceable>, <replaceable
10023 class="parameter">Y</replaceable>) pairs</entry>
10028 <function>regr_r2(<replaceable class="parameter">Y</replaceable>, <replaceable class="parameter">X</replaceable>)</function>
10031 <type>double precision</type>
10034 <type>double precision</type>
10036 <entry>square of the correlation coefficient</entry>
10042 <primary>regression slope</primary>
10044 <function>regr_slope(<replaceable class="parameter">Y</replaceable>, <replaceable class="parameter">X</replaceable>)</function>
10047 <type>double precision</type>
10050 <type>double precision</type>
10052 <entry>slope of the least-squares-fit linear equation determined
10053 by the (<replaceable class="parameter">X</replaceable>,
10054 <replaceable class="parameter">Y</replaceable>) pairs</entry>
10059 <function>regr_sxx(<replaceable class="parameter">Y</replaceable>, <replaceable class="parameter">X</replaceable>)</function>
10062 <type>double precision</type>
10065 <type>double precision</type>
10067 <entry><literal>sum(<replaceable
10068 class="parameter">X</replaceable>^2) - sum(<replaceable
10069 class="parameter">X</replaceable>)^2/<replaceable
10070 class="parameter">N</replaceable></literal> (<quote>sum of
10071 squares</quote> of the independent variable)</entry>
10076 <function>regr_sxy(<replaceable class="parameter">Y</replaceable>, <replaceable class="parameter">X</replaceable>)</function>
10079 <type>double precision</type>
10082 <type>double precision</type>
10084 <entry><literal>sum(<replaceable
10085 class="parameter">X</replaceable>*<replaceable
10086 class="parameter">Y</replaceable>) - sum(<replaceable
10087 class="parameter">X</replaceable>) * sum(<replaceable
10088 class="parameter">Y</replaceable>)/<replaceable
10089 class="parameter">N</replaceable></literal> (<quote>sum of
10090 products</quote> of independent times dependent
10096 <function>regr_syy(<replaceable class="parameter">Y</replaceable>, <replaceable class="parameter">X</replaceable>)</function>
10099 <type>double precision</type>
10102 <type>double precision</type>
10104 <entry><literal>sum(<replaceable
10105 class="parameter">Y</replaceable>^2) - sum(<replaceable
10106 class="parameter">Y</replaceable>)^2/<replaceable
10107 class="parameter">N</replaceable></literal> (<quote>sum of
10108 squares</quote> of the dependent variable)</entry>
10114 <primary>standard deviation</primary>
10116 <function>stddev(<replaceable class="parameter">expression</replaceable>)</function>
10119 <type>smallint</type>, <type>int</type>,
10120 <type>bigint</type>, <type>real</type>, <type>double
10121 precision</type>, or <type>numeric</type>
10124 <type>double precision</type> for floating-point arguments,
10125 otherwise <type>numeric</type>
10127 <entry>historical alias for <function>stddev_samp</function></entry>
10133 <primary>standard deviation</primary>
10134 <secondary>population</secondary>
10136 <function>stddev_pop(<replaceable class="parameter">expression</replaceable>)</function>
10139 <type>smallint</type>, <type>int</type>,
10140 <type>bigint</type>, <type>real</type>, <type>double
10141 precision</type>, or <type>numeric</type>
10144 <type>double precision</type> for floating-point arguments,
10145 otherwise <type>numeric</type>
10147 <entry>population standard deviation of the input values</entry>
10153 <primary>standard deviation</primary>
10154 <secondary>sample</secondary>
10156 <function>stddev_samp(<replaceable class="parameter">expression</replaceable>)</function>
10159 <type>smallint</type>, <type>int</type>,
10160 <type>bigint</type>, <type>real</type>, <type>double
10161 precision</type>, or <type>numeric</type>
10164 <type>double precision</type> for floating-point arguments,
10165 otherwise <type>numeric</type>
10167 <entry>sample standard deviation of the input values</entry>
10173 <primary>variance</primary>
10175 <function>variance</function>(<replaceable class="parameter">expression</replaceable>)
10178 <type>smallint</type>, <type>int</type>,
10179 <type>bigint</type>, <type>real</type>, <type>double
10180 precision</type>, or <type>numeric</type>
10183 <type>double precision</type> for floating-point arguments,
10184 otherwise <type>numeric</type>
10186 <entry>historical alias for <function>var_samp</function></entry>
10192 <primary>variance</primary>
10193 <secondary>population</secondary>
10195 <function>var_pop</function>(<replaceable class="parameter">expression</replaceable>)
10198 <type>smallint</type>, <type>int</type>,
10199 <type>bigint</type>, <type>real</type>, <type>double
10200 precision</type>, or <type>numeric</type>
10203 <type>double precision</type> for floating-point arguments,
10204 otherwise <type>numeric</type>
10206 <entry>population variance of the input values (square of the population standard deviation)</entry>
10212 <primary>variance</primary>
10213 <secondary>sample</secondary>
10215 <function>var_samp</function>(<replaceable class="parameter">expression</replaceable>)
10218 <type>smallint</type>, <type>int</type>,
10219 <type>bigint</type>, <type>real</type>, <type>double
10220 precision</type>, or <type>numeric</type>
10223 <type>double precision</type> for floating-point arguments,
10224 otherwise <type>numeric</type>
10226 <entry>sample variance of the input values (square of the sample standard deviation)</entry>
10234 <sect1 id="functions-window">
10235 <title>Window Functions</title>
10237 <indexterm zone="functions-window">
10238 <primary>window function</primary>
10239 <secondary>built-in</secondary>
10243 <firstterm>Window functions</firstterm> provide the ability to perform
10244 calculations across sets of rows that are related to the current query
10245 row. See <xref linkend="tutorial-window"> for an introduction to this
10250 The built-in window functions are listed in
10251 <xref linkend="functions-window-table">. Note that these functions
10252 <emphasis>must</> be invoked using window function syntax; that is an
10253 <literal>OVER</> clause is required.
10257 In addition to these functions, any built-in or user-defined aggregate
10258 function can be used as a window function (see
10259 <xref linkend="functions-aggregate"> for a list of the built-in aggregates).
10260 Aggregate functions act as window functions only when an <literal>OVER</>
10261 clause follows the call; otherwise they act as regular aggregates.
10264 <table id="functions-window-table">
10265 <title>General-Purpose Window Functions</title>
10270 <entry>Function</entry>
10271 <entry>Return Type</entry>
10272 <entry>Description</entry>
10280 <primary>row_number</primary>
10282 <function>row_number()</function>
10285 <type>bigint</type>
10287 <entry>number of the current row within its partition, counting from 1</entry>
10293 <primary>rank</primary>
10295 <function>rank()</function>
10298 <type>bigint</type>
10300 <entry>rank of the current row with gaps; same as <function>row_number</> of its first peer</entry>
10306 <primary>dense_rank</primary>
10308 <function>dense_rank()</function>
10311 <type>bigint</type>
10313 <entry>rank of the current row without gaps; this function counts peer groups</entry>
10319 <primary>percent_rank</primary>
10321 <function>percent_rank()</function>
10324 <type>double precision</type>
10326 <entry>relative rank of the current row: (<function>rank</> - 1) / (total rows - 1)</entry>
10332 <primary>cume_dist</primary>
10334 <function>cume_dist()</function>
10337 <type>double precision</type>
10339 <entry>relative rank of the current row: (number of rows preceding or peer with current row) / (total rows)</entry>
10345 <primary>ntile</primary>
10347 <function>ntile(<replaceable class="parameter">num_buckets</replaceable> <type>integer</>)</function>
10350 <type>integer</type>
10352 <entry>integer ranging from 1 to the argument value, dividing the
10353 partition as equally as possible</entry>
10359 <primary>lag</primary>
10362 lag(<replaceable class="parameter">value</replaceable> <type>any</>
10363 [, <replaceable class="parameter">offset</replaceable> <type>integer</>
10364 [, <replaceable class="parameter">default</replaceable> <type>any</> ]])
10368 <type>same type as <replaceable class="parameter">value</replaceable></type>
10371 returns <replaceable class="parameter">value</replaceable> evaluated at
10372 the row that is <replaceable class="parameter">offset</replaceable>
10373 rows before the current row within the partition; if there is no such
10374 row, instead return <replaceable class="parameter">default</replaceable>.
10375 Both <replaceable class="parameter">offset</replaceable> and
10376 <replaceable class="parameter">default</replaceable> are evaluated
10377 with respect to the current row. If omitted,
10378 <replaceable class="parameter">offset</replaceable> defaults to 1 and
10379 <replaceable class="parameter">default</replaceable> to null
10386 <primary>lead</primary>
10389 lead(<replaceable class="parameter">value</replaceable> <type>any</>
10390 [, <replaceable class="parameter">offset</replaceable> <type>integer</>
10391 [, <replaceable class="parameter">default</replaceable> <type>any</> ]])
10395 <type>same type as <replaceable class="parameter">value</replaceable></type>
10398 returns <replaceable class="parameter">value</replaceable> evaluated at
10399 the row that is <replaceable class="parameter">offset</replaceable>
10400 rows after the current row within the partition; if there is no such
10401 row, instead return <replaceable class="parameter">default</replaceable>.
10402 Both <replaceable class="parameter">offset</replaceable> and
10403 <replaceable class="parameter">default</replaceable> are evaluated
10404 with respect to the current row. If omitted,
10405 <replaceable class="parameter">offset</replaceable> defaults to 1 and
10406 <replaceable class="parameter">default</replaceable> to null
10413 <primary>first_value</primary>
10415 <function>first_value(<replaceable class="parameter">value</replaceable> <type>any</>)</function>
10418 <type>same type as <replaceable class="parameter">value</replaceable></type>
10421 returns <replaceable class="parameter">value</replaceable> evaluated
10422 at the row that is the first row of the window frame
10429 <primary>last_value</primary>
10431 <function>last_value(<replaceable class="parameter">value</replaceable> <type>any</>)</function>
10434 <type>same type as <replaceable class="parameter">value</replaceable></type>
10437 returns <replaceable class="parameter">value</replaceable> evaluated
10438 at the row that is the last row of the window frame
10445 <primary>nth_value</primary>
10448 nth_value(<replaceable class="parameter">value</replaceable> <type>any</>, <replaceable class="parameter">nth</replaceable> <type>integer</>)
10452 <type>same type as <replaceable class="parameter">value</replaceable></type>
10455 returns <replaceable class="parameter">value</replaceable> evaluated
10456 at the row that is the <replaceable class="parameter">nth</replaceable>
10457 row of the window frame (counting from 1); null if no such row
10465 All of the functions listed in
10466 <xref linkend="functions-window-table"> depend on the sort ordering
10467 specified by the <literal>ORDER BY</> clause of the associated window
10468 definition. Rows that are not distinct in the <literal>ORDER BY</>
10469 ordering are said to be <firstterm>peers</>; the four ranking functions
10470 are defined so that they give the same answer for any two peer rows.
10474 Note that <function>first_value</>, <function>last_value</>, and
10475 <function>nth_value</> consider only the rows within the <quote>window
10476 frame</>, which by default contains the rows from the start of the
10477 partition through the last peer of the current row. This is
10478 likely to give unhelpful results for <function>nth_value</> and
10479 particularly <function>last_value</>. You can redefine the frame as
10480 being the whole partition by adding <literal>ROWS BETWEEN UNBOUNDED
10481 PRECEDING AND UNBOUNDED FOLLOWING</> to the <literal>OVER</> clause.
10482 See <xref linkend="syntax-window-functions"> for more information.
10486 When an aggregate function is used as a window function, it aggregates
10487 over the rows within the current row's window frame. To obtain
10488 aggregation over the whole partition, omit <literal>ORDER BY</> or use
10489 <literal>ROWS BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING</>.
10490 An aggregate used with <literal>ORDER BY</> and the default window frame
10491 definition produces a <quote>running sum</> type of behavior, which may or
10492 may not be what's wanted.
10497 The SQL standard defines a <literal>RESPECT NULLS</> or
10498 <literal>IGNORE NULLS</> option for <function>lead</>, <function>lag</>,
10499 <function>first_value</>, <function>last_value</>, and
10500 <function>nth_value</>. This is not implemented in
10501 <productname>PostgreSQL</productname>: the behavior is always the
10502 same as the standard's default, namely <literal>RESPECT NULLS</>.
10503 Likewise, the standard's <literal>FROM FIRST</> or <literal>FROM LAST</>
10504 option for <function>nth_value</> is not implemented: only the
10505 default <literal>FROM FIRST</> behavior is supported. (You can achieve
10506 the result of <literal>FROM LAST</> by reversing the <literal>ORDER BY</>
10513 <sect1 id="functions-subquery">
10514 <title>Subquery Expressions</title>
10517 <primary>EXISTS</primary>
10521 <primary>IN</primary>
10525 <primary>NOT IN</primary>
10529 <primary>ANY</primary>
10533 <primary>ALL</primary>
10537 <primary>SOME</primary>
10541 <primary>subquery</primary>
10545 This section describes the <acronym>SQL</acronym>-compliant subquery
10546 expressions available in <productname>PostgreSQL</productname>.
10547 All of the expression forms documented in this section return
10548 Boolean (true/false) results.
10552 <title><literal>EXISTS</literal></title>
10555 EXISTS (<replaceable>subquery</replaceable>)
10559 The argument of <token>EXISTS</token> is an arbitrary <command>SELECT</> statement,
10560 or <firstterm>subquery</firstterm>. The
10561 subquery is evaluated to determine whether it returns any rows.
10562 If it returns at least one row, the result of <token>EXISTS</token> is
10563 <quote>true</>; if the subquery returns no rows, the result of <token>EXISTS</token>
10564 is <quote>false</>.
10568 The subquery can refer to variables from the surrounding query,
10569 which will act as constants during any one evaluation of the subquery.
10573 The subquery will generally only be executed long enough to determine
10574 whether at least one row is returned, not all the way to completion.
10575 It is unwise to write a subquery that has side effects (such as
10576 calling sequence functions); whether the side effects occur
10577 might be unpredictable.
10581 Since the result depends only on whether any rows are returned,
10582 and not on the contents of those rows, the output list of the
10583 subquery is normally unimportant. A common coding convention is
10584 to write all <literal>EXISTS</> tests in the form
10585 <literal>EXISTS(SELECT 1 WHERE ...)</literal>. There are exceptions to
10586 this rule however, such as subqueries that use <token>INTERSECT</token>.
10590 This simple example is like an inner join on <literal>col2</>, but
10591 it produces at most one output row for each <literal>tab1</> row,
10592 even if there are several matching <literal>tab2</> rows:
10596 WHERE EXISTS (SELECT 1 FROM tab2 WHERE col2 = tab1.col2);
10602 <title><literal>IN</literal></title>
10605 <replaceable>expression</replaceable> IN (<replaceable>subquery</replaceable>)
10609 The right-hand side is a parenthesized
10610 subquery, which must return exactly one column. The left-hand expression
10611 is evaluated and compared to each row of the subquery result.
10612 The result of <token>IN</token> is <quote>true</> if any equal subquery row is found.
10613 The result is <quote>false</> if no equal row is found (including the
10614 case where the subquery returns no rows).
10618 Note that if the left-hand expression yields null, or if there are
10619 no equal right-hand values and at least one right-hand row yields
10620 null, the result of the <token>IN</token> construct will be null, not false.
10621 This is in accordance with SQL's normal rules for Boolean combinations
10626 As with <token>EXISTS</token>, it's unwise to assume that the subquery will
10627 be evaluated completely.
10631 <replaceable>row_constructor</replaceable> IN (<replaceable>subquery</replaceable>)
10635 The left-hand side of this form of <token>IN</token> is a row constructor,
10636 as described in <xref linkend="sql-syntax-row-constructors">.
10637 The right-hand side is a parenthesized
10638 subquery, which must return exactly as many columns as there are
10639 expressions in the left-hand row. The left-hand expressions are
10640 evaluated and compared row-wise to each row of the subquery result.
10641 The result of <token>IN</token> is <quote>true</> if any equal subquery row is found.
10642 The result is <quote>false</> if no equal row is found (including the
10643 case where the subquery returns no rows).
10647 As usual, null values in the rows are combined per
10648 the normal rules of SQL Boolean expressions. Two rows are considered
10649 equal if all their corresponding members are non-null and equal; the rows
10650 are unequal if any corresponding members are non-null and unequal;
10651 otherwise the result of that row comparison is unknown (null).
10652 If all the per-row results are either unequal or null, with at least one
10653 null, then the result of <token>IN</token> is null.
10658 <title><literal>NOT IN</literal></title>
10661 <replaceable>expression</replaceable> NOT IN (<replaceable>subquery</replaceable>)
10665 The right-hand side is a parenthesized
10666 subquery, which must return exactly one column. The left-hand expression
10667 is evaluated and compared to each row of the subquery result.
10668 The result of <token>NOT IN</token> is <quote>true</> if only unequal subquery rows
10669 are found (including the case where the subquery returns no rows).
10670 The result is <quote>false</> if any equal row is found.
10674 Note that if the left-hand expression yields null, or if there are
10675 no equal right-hand values and at least one right-hand row yields
10676 null, the result of the <token>NOT IN</token> construct will be null, not true.
10677 This is in accordance with SQL's normal rules for Boolean combinations
10682 As with <token>EXISTS</token>, it's unwise to assume that the subquery will
10683 be evaluated completely.
10687 <replaceable>row_constructor</replaceable> NOT IN (<replaceable>subquery</replaceable>)
10691 The left-hand side of this form of <token>NOT IN</token> is a row constructor,
10692 as described in <xref linkend="sql-syntax-row-constructors">.
10693 The right-hand side is a parenthesized
10694 subquery, which must return exactly as many columns as there are
10695 expressions in the left-hand row. The left-hand expressions are
10696 evaluated and compared row-wise to each row of the subquery result.
10697 The result of <token>NOT IN</token> is <quote>true</> if only unequal subquery rows
10698 are found (including the case where the subquery returns no rows).
10699 The result is <quote>false</> if any equal row is found.
10703 As usual, null values in the rows are combined per
10704 the normal rules of SQL Boolean expressions. Two rows are considered
10705 equal if all their corresponding members are non-null and equal; the rows
10706 are unequal if any corresponding members are non-null and unequal;
10707 otherwise the result of that row comparison is unknown (null).
10708 If all the per-row results are either unequal or null, with at least one
10709 null, then the result of <token>NOT IN</token> is null.
10714 <title><literal>ANY</literal>/<literal>SOME</literal></title>
10717 <replaceable>expression</replaceable> <replaceable>operator</replaceable> ANY (<replaceable>subquery</replaceable>)
10718 <replaceable>expression</replaceable> <replaceable>operator</replaceable> SOME (<replaceable>subquery</replaceable>)
10722 The right-hand side is a parenthesized
10723 subquery, which must return exactly one column. The left-hand expression
10724 is evaluated and compared to each row of the subquery result using the
10725 given <replaceable>operator</replaceable>, which must yield a Boolean
10727 The result of <token>ANY</token> is <quote>true</> if any true result is obtained.
10728 The result is <quote>false</> if no true result is found (including the
10729 case where the subquery returns no rows).
10733 <token>SOME</token> is a synonym for <token>ANY</token>.
10734 <token>IN</token> is equivalent to <literal>= ANY</literal>.
10738 Note that if there are no successes and at least one right-hand row yields
10739 null for the operator's result, the result of the <token>ANY</token> construct
10740 will be null, not false.
10741 This is in accordance with SQL's normal rules for Boolean combinations
10746 As with <token>EXISTS</token>, it's unwise to assume that the subquery will
10747 be evaluated completely.
10751 <replaceable>row_constructor</replaceable> <replaceable>operator</> ANY (<replaceable>subquery</replaceable>)
10752 <replaceable>row_constructor</replaceable> <replaceable>operator</> SOME (<replaceable>subquery</replaceable>)
10756 The left-hand side of this form of <token>ANY</token> is a row constructor,
10757 as described in <xref linkend="sql-syntax-row-constructors">.
10758 The right-hand side is a parenthesized
10759 subquery, which must return exactly as many columns as there are
10760 expressions in the left-hand row. The left-hand expressions are
10761 evaluated and compared row-wise to each row of the subquery result,
10762 using the given <replaceable>operator</replaceable>.
10763 The result of <token>ANY</token> is <quote>true</> if the comparison
10764 returns true for any subquery row.
10765 The result is <quote>false</> if the comparison returns false for every
10766 subquery row (including the case where the subquery returns no
10768 The result is NULL if the comparison does not return true for any row,
10769 and it returns NULL for at least one row.
10773 See <xref linkend="row-wise-comparison"> for details about the meaning
10774 of a row-wise comparison.
10779 <title><literal>ALL</literal></title>
10782 <replaceable>expression</replaceable> <replaceable>operator</replaceable> ALL (<replaceable>subquery</replaceable>)
10786 The right-hand side is a parenthesized
10787 subquery, which must return exactly one column. The left-hand expression
10788 is evaluated and compared to each row of the subquery result using the
10789 given <replaceable>operator</replaceable>, which must yield a Boolean
10791 The result of <token>ALL</token> is <quote>true</> if all rows yield true
10792 (including the case where the subquery returns no rows).
10793 The result is <quote>false</> if any false result is found.
10794 The result is NULL if the comparison does not return false for any row,
10795 and it returns NULL for at least one row.
10799 <token>NOT IN</token> is equivalent to <literal><> ALL</literal>.
10803 As with <token>EXISTS</token>, it's unwise to assume that the subquery will
10804 be evaluated completely.
10808 <replaceable>row_constructor</replaceable> <replaceable>operator</replaceable> ALL (<replaceable>subquery</replaceable>)
10812 The left-hand side of this form of <token>ALL</token> is a row constructor,
10813 as described in <xref linkend="sql-syntax-row-constructors">.
10814 The right-hand side is a parenthesized
10815 subquery, which must return exactly as many columns as there are
10816 expressions in the left-hand row. The left-hand expressions are
10817 evaluated and compared row-wise to each row of the subquery result,
10818 using the given <replaceable>operator</replaceable>.
10819 The result of <token>ALL</token> is <quote>true</> if the comparison
10820 returns true for all subquery rows (including the
10821 case where the subquery returns no rows).
10822 The result is <quote>false</> if the comparison returns false for any
10824 The result is NULL if the comparison does not return false for any
10825 subquery row, and it returns NULL for at least one row.
10829 See <xref linkend="row-wise-comparison"> for details about the meaning
10830 of a row-wise comparison.
10835 <title>Row-wise Comparison</title>
10837 <indexterm zone="functions-subquery">
10838 <primary>comparison</primary>
10839 <secondary>subquery result row</secondary>
10843 <replaceable>row_constructor</replaceable> <replaceable>operator</replaceable> (<replaceable>subquery</replaceable>)
10847 The left-hand side is a row constructor,
10848 as described in <xref linkend="sql-syntax-row-constructors">.
10849 The right-hand side is a parenthesized subquery, which must return exactly
10850 as many columns as there are expressions in the left-hand row. Furthermore,
10851 the subquery cannot return more than one row. (If it returns zero rows,
10852 the result is taken to be null.) The left-hand side is evaluated and
10853 compared row-wise to the single subquery result row.
10857 See <xref linkend="row-wise-comparison"> for details about the meaning
10858 of a row-wise comparison.
10864 <sect1 id="functions-comparisons">
10865 <title>Row and Array Comparisons</title>
10868 <primary>IN</primary>
10872 <primary>NOT IN</primary>
10876 <primary>ANY</primary>
10880 <primary>ALL</primary>
10884 <primary>SOME</primary>
10888 <primary>row-wise comparison</primary>
10892 <primary>comparison</primary>
10893 <secondary>row-wise</secondary>
10897 <primary>IS DISTINCT FROM</primary>
10901 <primary>IS NOT DISTINCT FROM</primary>
10905 This section describes several specialized constructs for making
10906 multiple comparisons between groups of values. These forms are
10907 syntactically related to the subquery forms of the previous section,
10908 but do not involve subqueries.
10909 The forms involving array subexpressions are
10910 <productname>PostgreSQL</productname> extensions; the rest are
10911 <acronym>SQL</acronym>-compliant.
10912 All of the expression forms documented in this section return
10913 Boolean (true/false) results.
10917 <title><literal>IN</literal></title>
10920 <replaceable>expression</replaceable> IN (<replaceable>value</replaceable> <optional>, ...</optional>)
10924 The right-hand side is a parenthesized list
10925 of scalar expressions. The result is <quote>true</> if the left-hand expression's
10926 result is equal to any of the right-hand expressions. This is a shorthand
10930 <replaceable>expression</replaceable> = <replaceable>value1</replaceable>
10932 <replaceable>expression</replaceable> = <replaceable>value2</replaceable>
10939 Note that if the left-hand expression yields null, or if there are
10940 no equal right-hand values and at least one right-hand expression yields
10941 null, the result of the <token>IN</token> construct will be null, not false.
10942 This is in accordance with SQL's normal rules for Boolean combinations
10948 <title><literal>NOT IN</literal></title>
10951 <replaceable>expression</replaceable> NOT IN (<replaceable>value</replaceable> <optional>, ...</optional>)
10955 The right-hand side is a parenthesized list
10956 of scalar expressions. The result is <quote>true</quote> if the left-hand expression's
10957 result is unequal to all of the right-hand expressions. This is a shorthand
10961 <replaceable>expression</replaceable> <> <replaceable>value1</replaceable>
10963 <replaceable>expression</replaceable> <> <replaceable>value2</replaceable>
10970 Note that if the left-hand expression yields null, or if there are
10971 no equal right-hand values and at least one right-hand expression yields
10972 null, the result of the <token>NOT IN</token> construct will be null, not true
10973 as one might naively expect.
10974 This is in accordance with SQL's normal rules for Boolean combinations
10980 <literal>x NOT IN y</literal> is equivalent to <literal>NOT (x IN y)</literal> in all
10981 cases. However, null values are much more likely to trip up the novice when
10982 working with <token>NOT IN</token> than when working with <token>IN</token>.
10983 It is best to express your condition positively if possible.
10989 <title><literal>ANY</literal>/<literal>SOME</literal> (array)</title>
10992 <replaceable>expression</replaceable> <replaceable>operator</replaceable> ANY (<replaceable>array expression</replaceable>)
10993 <replaceable>expression</replaceable> <replaceable>operator</replaceable> SOME (<replaceable>array expression</replaceable>)
10997 The right-hand side is a parenthesized expression, which must yield an
10999 The left-hand expression
11000 is evaluated and compared to each element of the array using the
11001 given <replaceable>operator</replaceable>, which must yield a Boolean
11003 The result of <token>ANY</token> is <quote>true</> if any true result is obtained.
11004 The result is <quote>false</> if no true result is found (including the
11005 case where the array has zero elements).
11009 If the array expression yields a null array, the result of
11010 <token>ANY</token> will be null. If the left-hand expression yields null,
11011 the result of <token>ANY</token> is ordinarily null (though a non-strict
11012 comparison operator could possibly yield a different result).
11013 Also, if the right-hand array contains any null elements and no true
11014 comparison result is obtained, the result of <token>ANY</token>
11015 will be null, not false (again, assuming a strict comparison operator).
11016 This is in accordance with SQL's normal rules for Boolean combinations
11021 <token>SOME</token> is a synonym for <token>ANY</token>.
11026 <title><literal>ALL</literal> (array)</title>
11029 <replaceable>expression</replaceable> <replaceable>operator</replaceable> ALL (<replaceable>array expression</replaceable>)
11033 The right-hand side is a parenthesized expression, which must yield an
11035 The left-hand expression
11036 is evaluated and compared to each element of the array using the
11037 given <replaceable>operator</replaceable>, which must yield a Boolean
11039 The result of <token>ALL</token> is <quote>true</> if all comparisons yield true
11040 (including the case where the array has zero elements).
11041 The result is <quote>false</> if any false result is found.
11045 If the array expression yields a null array, the result of
11046 <token>ALL</token> will be null. If the left-hand expression yields null,
11047 the result of <token>ALL</token> is ordinarily null (though a non-strict
11048 comparison operator could possibly yield a different result).
11049 Also, if the right-hand array contains any null elements and no false
11050 comparison result is obtained, the result of <token>ALL</token>
11051 will be null, not true (again, assuming a strict comparison operator).
11052 This is in accordance with SQL's normal rules for Boolean combinations
11057 <sect2 id="row-wise-comparison">
11058 <title>Row-wise Comparison</title>
11061 <replaceable>row_constructor</replaceable> <replaceable>operator</replaceable> <replaceable>row_constructor</replaceable>
11065 Each side is a row constructor,
11066 as described in <xref linkend="sql-syntax-row-constructors">.
11067 The two row values must have the same number of fields.
11068 Each side is evaluated and they are compared row-wise. Row comparisons
11069 are allowed when the <replaceable>operator</replaceable> is
11071 <literal><></>,
11074 <literal>></> or
11076 or has semantics similar to one of these. (To be specific, an operator
11077 can be a row comparison operator if it is a member of a B-Tree operator
11078 class, or is the negator of the <literal>=</> member of a B-Tree operator
11083 The <literal>=</> and <literal><></> cases work slightly differently
11084 from the others. Two rows are considered
11085 equal if all their corresponding members are non-null and equal; the rows
11086 are unequal if any corresponding members are non-null and unequal;
11087 otherwise the result of the row comparison is unknown (null).
11091 For the <literal><</>, <literal><=</>, <literal>></> and
11092 <literal>>=</> cases, the row elements are compared left-to-right,
11093 stopping as soon as an unequal or null pair of elements is found.
11094 If either of this pair of elements is null, the result of the
11095 row comparison is unknown (null); otherwise comparison of this pair
11096 of elements determines the result. For example,
11097 <literal>ROW(1,2,NULL) < ROW(1,3,0)</>
11098 yields true, not null, because the third pair of elements are not
11104 Prior to <productname>PostgreSQL</productname> 8.2, the
11105 <literal><</>, <literal><=</>, <literal>></> and <literal>>=</>
11106 cases were not handled per SQL specification. A comparison like
11107 <literal>ROW(a,b) < ROW(c,d)</>
11109 <literal>a < c AND b < d</>
11110 whereas the correct behavior is equivalent to
11111 <literal>a < c OR (a = c AND b < d)</>.
11116 <replaceable>row_constructor</replaceable> IS DISTINCT FROM <replaceable>row_constructor</replaceable>
11120 This construct is similar to a <literal><></literal> row comparison,
11121 but it does not yield null for null inputs. Instead, any null value is
11122 considered unequal to (distinct from) any non-null value, and any two
11123 nulls are considered equal (not distinct). Thus the result will
11124 either be true or false, never null.
11128 <replaceable>row_constructor</replaceable> IS NOT DISTINCT FROM <replaceable>row_constructor</replaceable>
11132 This construct is similar to a <literal>=</literal> row comparison,
11133 but it does not yield null for null inputs. Instead, any null value is
11134 considered unequal to (distinct from) any non-null value, and any two
11135 nulls are considered equal (not distinct). Thus the result will always
11136 be either true or false, never null.
11141 The SQL specification requires row-wise comparison to return NULL if the
11142 result depends on comparing two NULL values or a NULL and a non-NULL.
11143 <productname>PostgreSQL</productname> does this only when comparing the
11144 results of two row constructors or comparing a row constructor to the
11145 output of a subquery (as in <xref linkend="functions-subquery">).
11146 In other contexts where two composite-type values are compared, two
11147 NULL field values are considered equal, and a NULL is considered larger
11148 than a non-NULL. This is necessary in order to have consistent sorting
11149 and indexing behavior for composite types.
11156 <sect1 id="functions-srf">
11157 <title>Set Returning Functions</title>
11159 <indexterm zone="functions-srf">
11160 <primary>set returning functions</primary>
11161 <secondary>functions</secondary>
11165 <primary>generate_series</primary>
11169 This section describes functions that possibly return more than one row.
11170 Currently the only functions in this class are series generating functions,
11171 as detailed in <xref linkend="functions-srf-series"> and
11172 <xref linkend="functions-srf-subscripts">.
11175 <table id="functions-srf-series">
11176 <title>Series Generating Functions</title>
11180 <entry>Function</entry>
11181 <entry>Argument Type</entry>
11182 <entry>Return Type</entry>
11183 <entry>Description</entry>
11189 <entry><literal><function>generate_series</function>(<parameter>start</parameter>, <parameter>stop</parameter>)</literal></entry>
11190 <entry><type>int</type> or <type>bigint</type></entry>
11191 <entry><type>setof int</type> or <type>setof bigint</type> (same as argument type)</entry>
11193 Generate a series of values, from <parameter>start</parameter> to <parameter>stop</parameter>
11194 with a step size of one
11199 <entry><literal><function>generate_series</function>(<parameter>start</parameter>, <parameter>stop</parameter>, <parameter>step</parameter>)</literal></entry>
11200 <entry><type>int</type> or <type>bigint</type></entry>
11201 <entry><type>setof int</type> or <type>setof bigint</type> (same as argument type)</entry>
11203 Generate a series of values, from <parameter>start</parameter> to <parameter>stop</parameter>
11204 with a step size of <parameter>step</parameter>
11209 <entry><literal><function>generate_series</function>(<parameter>start</parameter>, <parameter>stop</parameter>, <parameter>step</parameter> <type>interval</>)</literal></entry>
11210 <entry><type>timestamp</type> or <type>timestamp with time zone</type></entry>
11211 <entry><type>setof timestamp</type> or <type>setof timestamp with time zone</type> (same as argument type)</entry>
11213 Generate a series of values, from <parameter>start</parameter> to <parameter>stop</parameter>
11214 with a step size of <parameter>step</parameter>
11223 When <parameter>step</parameter> is positive, zero rows are returned if
11224 <parameter>start</parameter> is greater than <parameter>stop</parameter>.
11225 Conversely, when <parameter>step</parameter> is negative, zero rows are
11226 returned if <parameter>start</parameter> is less than <parameter>stop</parameter>.
11227 Zero rows are also returned for <literal>NULL</literal> inputs. It is an error
11228 for <parameter>step</parameter> to be zero. Some examples follow:
11230 SELECT * FROM generate_series(2,4);
11238 SELECT * FROM generate_series(5,1,-2);
11246 SELECT * FROM generate_series(4,3);
11251 -- this example relies on the date-plus-integer operator
11252 SELECT current_date + s.a AS dates FROM generate_series(0,14,7) AS s(a);
11260 SELECT * FROM generate_series('2008-03-01 00:00'::timestamp,
11261 '2008-03-04 12:00', '10 hours');
11263 ---------------------
11264 2008-03-01 00:00:00
11265 2008-03-01 10:00:00
11266 2008-03-01 20:00:00
11267 2008-03-02 06:00:00
11268 2008-03-02 16:00:00
11269 2008-03-03 02:00:00
11270 2008-03-03 12:00:00
11271 2008-03-03 22:00:00
11272 2008-03-04 08:00:00
11277 <table id="functions-srf-subscripts">
11278 <title>Subscript Generating Functions</title>
11282 <entry>Function</entry>
11283 <entry>Return Type</entry>
11284 <entry>Description</entry>
11290 <entry><literal><function>generate_subscripts</function>(<parameter>array anyarray</parameter>, <parameter>dim int</parameter>)</literal></entry>
11291 <entry><type>setof int</type></entry>
11293 Generate a series comprising the given array's subscripts.
11298 <entry><literal><function>generate_subscripts</function>(<parameter>array anyarray</parameter>, <parameter>dim int</parameter>, <parameter>reverse boolean</parameter>)</literal></entry>
11299 <entry><type>setof int</type></entry>
11301 Generate a series comprising the given array's subscripts. When
11302 <parameter>reverse</parameter> is true, the series is returned in
11312 <primary>generate_subscripts</primary>
11316 <function>generate_subscripts</> is a convenience function that generates
11317 the set of valid subscripts for the specified dimension of the given
11319 Zero rows are returned for arrays that do not have the requested dimension,
11320 or for NULL arrays (but valid subscripts are returned for NULL array
11321 elements). Some examples follow:
11324 select generate_subscripts('{NULL,1,NULL,2}'::int[], 1) as s;
11333 -- presenting an array, the subscript and the subscripted
11334 -- value requires a subquery
11335 select * from arrays;
11337 --------------------
11342 select a as array, s as subscript, a[s] as value
11343 from (select generate_subscripts(a, 1) as s, a from arrays) foo;
11344 array | subscript | value
11345 -----------+-----------+-------
11348 {100,200} | 1 | 100
11349 {100,200} | 2 | 200
11352 -- unnest a 2D array
11353 create or replace function unnest2(anyarray)
11354 returns setof anyelement as $$
11356 from generate_subscripts($1,1) g1(i),
11357 generate_subscripts($1,2) g2(j);
11358 $$ language sql immutable;
11360 postgres=# select * from unnest2(array[[1,2],[3,4]]);
11373 <sect1 id="functions-info">
11374 <title>System Information Functions</title>
11377 <xref linkend="functions-info-session-table"> shows several
11378 functions that extract session and system information.
11382 In addition to the functions listed in this section, there are a number of
11383 functions related to the statistics system that also provide system
11384 information. See <xref linkend="monitoring-stats-views"> for more
11388 <table id="functions-info-session-table">
11389 <title>Session Information Functions</title>
11392 <row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry></row>
11397 <entry><literal><function>current_catalog</function></literal></entry>
11398 <entry><type>name</type></entry>
11399 <entry>name of current database (called <quote>catalog</quote> in the SQL standard)</entry>
11403 <entry><literal><function>current_database</function>()</literal></entry>
11404 <entry><type>name</type></entry>
11405 <entry>name of current database</entry>
11409 <entry><literal><function>current_schema</function>[()]</literal></entry>
11410 <entry><type>name</type></entry>
11411 <entry>name of current schema</entry>
11415 <entry><literal><function>current_schemas</function>(<type>boolean</type>)</literal></entry>
11416 <entry><type>name[]</type></entry>
11417 <entry>names of schemas in search path optionally including implicit schemas</entry>
11421 <entry><literal><function>current_user</function></literal></entry>
11422 <entry><type>name</type></entry>
11423 <entry>user name of current execution context</entry>
11427 <entry><literal><function>current_query</function></literal></entry>
11428 <entry><type>text</type></entry>
11429 <entry>text of the currently executing query, as submitted
11430 by the client (might contain more than one statement)</entry>
11434 <!-- See also the entry for this in monitoring.sgml -->
11435 <entry><literal><function>pg_backend_pid</function>()</literal></entry>
11436 <entry><type>int</type></entry>
11438 Process ID of the server process attached to the current session
11443 <entry><literal><function>inet_client_addr</function>()</literal></entry>
11444 <entry><type>inet</type></entry>
11445 <entry>address of the remote connection</entry>
11449 <entry><literal><function>inet_client_port</function>()</literal></entry>
11450 <entry><type>int</type></entry>
11451 <entry>port of the remote connection</entry>
11455 <entry><literal><function>inet_server_addr</function>()</literal></entry>
11456 <entry><type>inet</type></entry>
11457 <entry>address of the local connection</entry>
11461 <entry><literal><function>inet_server_port</function>()</literal></entry>
11462 <entry><type>int</type></entry>
11463 <entry>port of the local connection</entry>
11467 <entry><literal><function>pg_my_temp_schema</function>()</literal></entry>
11468 <entry><type>oid</type></entry>
11469 <entry>OID of session's temporary schema, or 0 if none</entry>
11473 <entry><literal><function>pg_is_other_temp_schema</function>(<type>oid</type>)</literal></entry>
11474 <entry><type>boolean</type></entry>
11475 <entry>is schema another session's temporary schema?</entry>
11479 <entry><literal><function>pg_postmaster_start_time</function>()</literal></entry>
11480 <entry><type>timestamp with time zone</type></entry>
11481 <entry>server start time</entry>
11485 <entry><literal><function>pg_conf_load_time</function>()</literal></entry>
11486 <entry><type>timestamp with time zone</type></entry>
11487 <entry>configuration load time</entry>
11491 <entry><literal><function>session_user</function></literal></entry>
11492 <entry><type>name</type></entry>
11493 <entry>session user name</entry>
11497 <entry><literal><function>user</function></literal></entry>
11498 <entry><type>name</type></entry>
11499 <entry>equivalent to <function>current_user</function></entry>
11503 <entry><literal><function>version</function>()</literal></entry>
11504 <entry><type>text</type></entry>
11505 <entry><productname>PostgreSQL</> version information</entry>
11512 <primary>user</primary>
11513 <secondary>current</secondary>
11517 <primary>schema</primary>
11518 <secondary>current</secondary>
11522 <primary>search path</primary>
11523 <secondary>current</secondary>
11527 <primary>current_catalog</primary>
11531 <primary>current_database</primary>
11535 <primary>current_schema</primary>
11539 <primary>current_user</primary>
11543 The <function>session_user</function> is normally the user who initiated
11544 the current database connection; but superusers can change this setting
11545 with <xref linkend="sql-set-session-authorization" endterm="sql-set-session-authorization-title">.
11546 The <function>current_user</function> is the user identifier
11547 that is applicable for permission checking. Normally it is equal
11548 to the session user, but it can be changed with
11549 <xref linkend="sql-set-role" endterm="sql-set-role-title">.
11550 It also changes during the execution of
11551 functions with the attribute <literal>SECURITY DEFINER</literal>.
11552 In Unix parlance, the session user is the <quote>real user</quote> and
11553 the current user is the <quote>effective user</quote>.
11558 <function>current_catalog</function>, <function>current_schema</function>,
11559 <function>current_user</function>, <function>session_user</function>,
11560 and <function>user</function> have special syntactic status
11561 in <acronym>SQL</acronym>: they must be called without trailing
11562 parentheses (optional in PostgreSQL in the case
11563 of <function>current_schema</function>).
11568 <function>current_schema</function> returns the name of the schema that is
11569 first in the search path (or a null value if the search path is
11570 empty). This is the schema that will be used for any tables or
11571 other named objects that are created without specifying a target schema.
11572 <function>current_schemas(boolean)</function> returns an array of the names of all
11573 schemas presently in the search path. The Boolean option determines whether or not
11574 implicitly included system schemas such as <literal>pg_catalog</> are included in the
11575 returned search path.
11580 The search path can be altered at run time. The command is:
11582 SET search_path TO <replaceable>schema</> <optional>, <replaceable>schema</>, ...</optional>
11588 <primary>inet_client_addr</primary>
11592 <primary>inet_client_port</primary>
11596 <primary>inet_server_addr</primary>
11600 <primary>inet_server_port</primary>
11604 <function>inet_client_addr</function> returns the IP address of the
11605 current client, and <function>inet_client_port</function> returns the
11607 <function>inet_server_addr</function> returns the IP address on which
11608 the server accepted the current connection, and
11609 <function>inet_server_port</function> returns the port number.
11610 All these functions return NULL if the current connection is via a
11611 Unix-domain socket.
11615 <primary>pg_my_temp_schema</primary>
11619 <primary>pg_is_other_temp_schema</primary>
11623 <function>pg_my_temp_schema</function> returns the OID of the current
11624 session's temporary schema, or zero if it has none (because it has not
11625 created any temporary tables).
11626 <function>pg_is_other_temp_schema</function> returns true if the
11627 given OID is the OID of another session's temporary schema.
11628 (This can be useful, for example, to exclude other sessions' temporary
11629 tables from a catalog display.)
11633 <primary>pg_postmaster_start_time</primary>
11637 <function>pg_postmaster_start_time</function> returns the
11638 <type>timestamp with time zone</type> when the
11643 <primary>pg_conf_load_time</primary>
11647 <function>pg_conf_load_time</function> returns the
11648 <type>timestamp with time zone</type> when the
11649 server configuration files were last loaded.
11650 (If the current session was alive at the time, this will be the time
11651 when the session itself re-read the configuration files, so the
11652 reading will vary a little in different sessions. Otherwise it is
11653 the time when the postmaster process re-read the configuration files.)
11657 <primary>version</primary>
11661 <function>version</function> returns a string describing the
11662 <productname>PostgreSQL</productname> server's version.
11666 <primary>privilege</primary>
11667 <secondary>querying</secondary>
11671 <xref linkend="functions-info-access-table"> lists functions that
11672 allow the user to query object access privileges programmatically.
11673 See <xref linkend="ddl-priv"> for more information about
11677 <table id="functions-info-access-table">
11678 <title>Access Privilege Inquiry Functions</title>
11681 <row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry></row>
11686 <entry><literal><function>has_any_column_privilege</function>(<parameter>user</parameter>,
11687 <parameter>table</parameter>,
11688 <parameter>privilege</parameter>)</literal>
11690 <entry><type>boolean</type></entry>
11691 <entry>does user have privilege for any column of table</entry>
11694 <entry><literal><function>has_any_column_privilege</function>(<parameter>table</parameter>,
11695 <parameter>privilege</parameter>)</literal>
11697 <entry><type>boolean</type></entry>
11698 <entry>does current user have privilege for any column of table</entry>
11701 <entry><literal><function>has_column_privilege</function>(<parameter>user</parameter>,
11702 <parameter>table</parameter>,
11703 <parameter>column</parameter>,
11704 <parameter>privilege</parameter>)</literal>
11706 <entry><type>boolean</type></entry>
11707 <entry>does user have privilege for column</entry>
11710 <entry><literal><function>has_column_privilege</function>(<parameter>table</parameter>,
11711 <parameter>column</parameter>,
11712 <parameter>privilege</parameter>)</literal>
11714 <entry><type>boolean</type></entry>
11715 <entry>does current user have privilege for column</entry>
11718 <entry><literal><function>has_database_privilege</function>(<parameter>user</parameter>,
11719 <parameter>database</parameter>,
11720 <parameter>privilege</parameter>)</literal>
11722 <entry><type>boolean</type></entry>
11723 <entry>does user have privilege for database</entry>
11726 <entry><literal><function>has_database_privilege</function>(<parameter>database</parameter>,
11727 <parameter>privilege</parameter>)</literal>
11729 <entry><type>boolean</type></entry>
11730 <entry>does current user have privilege for database</entry>
11733 <entry><literal><function>has_foreign_data_wrapper_privilege</function>(<parameter>user</parameter>,
11734 <parameter>fdw</parameter>,
11735 <parameter>privilege</parameter>)</literal>
11737 <entry><type>boolean</type></entry>
11738 <entry>does user have privilege for foreign-data wrapper</entry>
11741 <entry><literal><function>has_foreign_data_wrapper_privilege</function>(<parameter>fdw</parameter>,
11742 <parameter>privilege</parameter>)</literal>
11744 <entry><type>boolean</type></entry>
11745 <entry>does current user have privilege for foreign-data wrapper</entry>
11748 <entry><literal><function>has_function_privilege</function>(<parameter>user</parameter>,
11749 <parameter>function</parameter>,
11750 <parameter>privilege</parameter>)</literal>
11752 <entry><type>boolean</type></entry>
11753 <entry>does user have privilege for function</entry>
11756 <entry><literal><function>has_function_privilege</function>(<parameter>function</parameter>,
11757 <parameter>privilege</parameter>)</literal>
11759 <entry><type>boolean</type></entry>
11760 <entry>does current user have privilege for function</entry>
11763 <entry><literal><function>has_language_privilege</function>(<parameter>user</parameter>,
11764 <parameter>language</parameter>,
11765 <parameter>privilege</parameter>)</literal>
11767 <entry><type>boolean</type></entry>
11768 <entry>does user have privilege for language</entry>
11771 <entry><literal><function>has_language_privilege</function>(<parameter>language</parameter>,
11772 <parameter>privilege</parameter>)</literal>
11774 <entry><type>boolean</type></entry>
11775 <entry>does current user have privilege for language</entry>
11778 <entry><literal><function>has_schema_privilege</function>(<parameter>user</parameter>,
11779 <parameter>schema</parameter>,
11780 <parameter>privilege</parameter>)</literal>
11782 <entry><type>boolean</type></entry>
11783 <entry>does user have privilege for schema</entry>
11786 <entry><literal><function>has_schema_privilege</function>(<parameter>schema</parameter>,
11787 <parameter>privilege</parameter>)</literal>
11789 <entry><type>boolean</type></entry>
11790 <entry>does current user have privilege for schema</entry>
11793 <entry><literal><function>has_server_privilege</function>(<parameter>user</parameter>,
11794 <parameter>server</parameter>,
11795 <parameter>privilege</parameter>)</literal>
11797 <entry><type>boolean</type></entry>
11798 <entry>does user have privilege for foreign server</entry>
11801 <entry><literal><function>has_server_privilege</function>(<parameter>server</parameter>,
11802 <parameter>privilege</parameter>)</literal>
11804 <entry><type>boolean</type></entry>
11805 <entry>does current user have privilege for foreign server</entry>
11808 <entry><literal><function>has_sequence_privilege</function>(<parameter>user</parameter>,
11809 <parameter>sequence</parameter>,
11810 <parameter>privilege</parameter>)</literal>
11812 <entry><type>boolean</type></entry>
11813 <entry>does user have privilege for sequence</entry>
11816 <entry><literal><function>has_sequence_privilege</function>(<parameter>sequence</parameter>,
11817 <parameter>privilege</parameter>)</literal>
11819 <entry><type>boolean</type></entry>
11820 <entry>does current user have privilege for sequence</entry>
11823 <entry><literal><function>has_table_privilege</function>(<parameter>user</parameter>,
11824 <parameter>table</parameter>,
11825 <parameter>privilege</parameter>)</literal>
11827 <entry><type>boolean</type></entry>
11828 <entry>does user have privilege for table</entry>
11831 <entry><literal><function>has_table_privilege</function>(<parameter>table</parameter>,
11832 <parameter>privilege</parameter>)</literal>
11834 <entry><type>boolean</type></entry>
11835 <entry>does current user have privilege for table</entry>
11838 <entry><literal><function>has_tablespace_privilege</function>(<parameter>user</parameter>,
11839 <parameter>tablespace</parameter>,
11840 <parameter>privilege</parameter>)</literal>
11842 <entry><type>boolean</type></entry>
11843 <entry>does user have privilege for tablespace</entry>
11846 <entry><literal><function>has_tablespace_privilege</function>(<parameter>tablespace</parameter>,
11847 <parameter>privilege</parameter>)</literal>
11849 <entry><type>boolean</type></entry>
11850 <entry>does current user have privilege for tablespace</entry>
11853 <entry><literal><function>pg_has_role</function>(<parameter>user</parameter>,
11854 <parameter>role</parameter>,
11855 <parameter>privilege</parameter>)</literal>
11857 <entry><type>boolean</type></entry>
11858 <entry>does user have privilege for role</entry>
11861 <entry><literal><function>pg_has_role</function>(<parameter>role</parameter>,
11862 <parameter>privilege</parameter>)</literal>
11864 <entry><type>boolean</type></entry>
11865 <entry>does current user have privilege for role</entry>
11872 <primary>has_any_column_privilege</primary>
11875 <primary>has_column_privilege</primary>
11878 <primary>has_database_privilege</primary>
11881 <primary>has_function_privilege</primary>
11884 <primary>has_foreign_data_wrapper_privilege</primary>
11887 <primary>has_language_privilege</primary>
11890 <primary>has_schema_privilege</primary>
11893 <primary>has_server_privilege</primary>
11896 <primary>has_sequence_privilege</primary>
11899 <primary>has_table_privilege</primary>
11902 <primary>has_tablespace_privilege</primary>
11905 <primary>pg_has_role</primary>
11909 <function>has_table_privilege</function> checks whether a user
11910 can access a table in a particular way. The user can be
11911 specified by name or by OID
11912 (<literal>pg_authid.oid</literal>), or if the argument is
11914 <function>current_user</function> is assumed. The table can be specified
11915 by name or by OID. (Thus, there are actually six variants of
11916 <function>has_table_privilege</function>, which can be distinguished by
11917 the number and types of their arguments.) When specifying by name,
11918 the name can be schema-qualified if necessary.
11919 The desired access privilege type
11920 is specified by a text string, which must evaluate to one of the
11921 values <literal>SELECT</literal>, <literal>INSERT</literal>,
11922 <literal>UPDATE</literal>, <literal>DELETE</literal>, <literal>TRUNCATE</>,
11923 <literal>REFERENCES</literal>, or <literal>TRIGGER</literal>. Optionally,
11924 <literal>WITH GRANT OPTION</> can be added to a privilege type to test
11925 whether the privilege is held with grant option. Also, multiple privilege
11926 types can be listed separated by commas, in which case the result will
11927 be <literal>true</> if any of the listed privileges is held.
11928 (Case of the privilege string is not significant, and extra whitespace
11929 is allowed between but not within privilege names.)
11932 SELECT has_table_privilege('myschema.mytable', 'select');
11933 SELECT has_table_privilege('joe', 'mytable', 'INSERT, SELECT WITH GRANT OPTION');
11938 <function>has_sequence_privilege</function> checks whether a user
11939 can access a sequence in a particular way. The possibilities for its
11940 arguments are analogous to <function>has_table_privilege</function>.
11941 The desired access privilege type must evaluate to one of
11942 <literal>USAGE</literal>,
11943 <literal>SELECT</literal>, or
11944 <literal>UPDATE</literal>.
11948 <function>has_any_column_privilege</function> checks whether a user can
11949 access any column of a table in a particular way.
11950 Its argument possibilities
11951 are analogous to <function>has_table_privilege</>,
11952 except that the desired access privilege type must evaluate to some
11954 <literal>SELECT</literal>,
11955 <literal>INSERT</literal>,
11956 <literal>UPDATE</literal>, or
11957 <literal>REFERENCES</literal>. Note that having any of these privileges
11958 at the table level implicitly grants it for each column of the table,
11959 so <function>has_any_column_privilege</function> will always return
11960 <literal>true</> if <function>has_table_privilege</> does for the same
11961 arguments. But <function>has_any_column_privilege</> also succeeds if
11962 there is a column-level grant of the privilege for at least one column.
11966 <function>has_column_privilege</function> checks whether a user
11967 can access a column in a particular way.
11968 Its argument possibilities
11969 are analogous to <function>has_table_privilege</function>,
11970 with the addition that the column can be specified either by name
11971 or attribute number.
11972 The desired access privilege type must evaluate to some combination of
11973 <literal>SELECT</literal>,
11974 <literal>INSERT</literal>,
11975 <literal>UPDATE</literal>, or
11976 <literal>REFERENCES</literal>. Note that having any of these privileges
11977 at the table level implicitly grants it for each column of the table.
11981 <function>has_database_privilege</function> checks whether a user
11982 can access a database in a particular way.
11983 Its argument possibilities
11984 are analogous to <function>has_table_privilege</function>.
11985 The desired access privilege type must evaluate to some combination of
11986 <literal>CREATE</literal>,
11987 <literal>CONNECT</literal>,
11988 <literal>TEMPORARY</literal>, or
11989 <literal>TEMP</literal> (which is equivalent to
11990 <literal>TEMPORARY</literal>).
11994 <function>has_function_privilege</function> checks whether a user
11995 can access a function in a particular way.
11996 Its argument possibilities
11997 are analogous to <function>has_table_privilege</function>.
11998 When specifying a function by a text string rather than by OID,
11999 the allowed input is the same as for the <type>regprocedure</> data type
12000 (see <xref linkend="datatype-oid">).
12001 The desired access privilege type must evaluate to
12002 <literal>EXECUTE</literal>.
12005 SELECT has_function_privilege('joeuser', 'myfunc(int, text)', 'execute');
12010 <function>has_foreign_data_wrapper_privilege</function> checks whether a user
12011 can access a foreign-data wrapper in a particular way.
12012 Its argument possibilities
12013 are analogous to <function>has_table_privilege</function>.
12014 The desired access privilege type must evaluate to
12015 <literal>USAGE</literal>.
12019 <function>has_language_privilege</function> checks whether a user
12020 can access a procedural language in a particular way.
12021 Its argument possibilities
12022 are analogous to <function>has_table_privilege</function>.
12023 The desired access privilege type must evaluate to
12024 <literal>USAGE</literal>.
12028 <function>has_schema_privilege</function> checks whether a user
12029 can access a schema in a particular way.
12030 Its argument possibilities
12031 are analogous to <function>has_table_privilege</function>.
12032 The desired access privilege type must evaluate to some combination of
12033 <literal>CREATE</literal> or
12034 <literal>USAGE</literal>.
12038 <function>has_server_privilege</function> checks whether a user
12039 can access a foreign server in a particular way.
12040 Its argument possibilities
12041 are analogous to <function>has_table_privilege</function>.
12042 The desired access privilege type must evaluate to
12043 <literal>USAGE</literal>.
12047 <function>has_tablespace_privilege</function> checks whether a user
12048 can access a tablespace in a particular way.
12049 Its argument possibilities
12050 are analogous to <function>has_table_privilege</function>.
12051 The desired access privilege type must evaluate to
12052 <literal>CREATE</literal>.
12056 <function>pg_has_role</function> checks whether a user
12057 can access a role in a particular way.
12058 Its argument possibilities
12059 are analogous to <function>has_table_privilege</function>.
12060 The desired access privilege type must evaluate to some combination of
12061 <literal>MEMBER</literal> or
12062 <literal>USAGE</literal>.
12063 <literal>MEMBER</literal> denotes direct or indirect membership in
12064 the role (that is, the right to do <command>SET ROLE</>), while
12065 <literal>USAGE</literal> denotes whether the privileges of the role
12066 are immediately available without doing <command>SET ROLE</>.
12070 <xref linkend="functions-info-schema-table"> shows functions that
12071 determine whether a certain object is <firstterm>visible</> in the
12072 current schema search path.
12073 For example, a table is said to be visible if its
12074 containing schema is in the search path and no table of the same
12075 name appears earlier in the search path. This is equivalent to the
12076 statement that the table can be referenced by name without explicit
12077 schema qualification. To list the names of all visible tables:
12079 SELECT relname FROM pg_class WHERE pg_table_is_visible(oid);
12083 <table id="functions-info-schema-table">
12084 <title>Schema Visibility Inquiry Functions</title>
12087 <row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry></row>
12092 <entry><literal><function>pg_conversion_is_visible</function>(<parameter>conversion_oid</parameter>)</literal>
12094 <entry><type>boolean</type></entry>
12095 <entry>is conversion visible in search path</entry>
12098 <entry><literal><function>pg_function_is_visible</function>(<parameter>function_oid</parameter>)</literal>
12100 <entry><type>boolean</type></entry>
12101 <entry>is function visible in search path</entry>
12104 <entry><literal><function>pg_operator_is_visible</function>(<parameter>operator_oid</parameter>)</literal>
12106 <entry><type>boolean</type></entry>
12107 <entry>is operator visible in search path</entry>
12110 <entry><literal><function>pg_opclass_is_visible</function>(<parameter>opclass_oid</parameter>)</literal>
12112 <entry><type>boolean</type></entry>
12113 <entry>is operator class visible in search path</entry>
12116 <entry><literal><function>pg_table_is_visible</function>(<parameter>table_oid</parameter>)</literal>
12118 <entry><type>boolean</type></entry>
12119 <entry>is table visible in search path</entry>
12122 <entry><literal><function>pg_ts_config_is_visible</function>(<parameter>config_oid</parameter>)</literal>
12124 <entry><type>boolean</type></entry>
12125 <entry>is text search configuration visible in search path</entry>
12128 <entry><literal><function>pg_ts_dict_is_visible</function>(<parameter>dict_oid</parameter>)</literal>
12130 <entry><type>boolean</type></entry>
12131 <entry>is text search dictionary visible in search path</entry>
12134 <entry><literal><function>pg_ts_parser_is_visible</function>(<parameter>parser_oid</parameter>)</literal>
12136 <entry><type>boolean</type></entry>
12137 <entry>is text search parser visible in search path</entry>
12140 <entry><literal><function>pg_ts_template_is_visible</function>(<parameter>template_oid</parameter>)</literal>
12142 <entry><type>boolean</type></entry>
12143 <entry>is text search template visible in search path</entry>
12146 <entry><literal><function>pg_type_is_visible</function>(<parameter>type_oid</parameter>)</literal>
12148 <entry><type>boolean</type></entry>
12149 <entry>is type (or domain) visible in search path</entry>
12156 <primary>pg_conversion_is_visible</primary>
12159 <primary>pg_function_is_visible</primary>
12162 <primary>pg_operator_is_visible</primary>
12165 <primary>pg_opclass_is_visible</primary>
12168 <primary>pg_table_is_visible</primary>
12171 <primary>pg_ts_config_is_visible</primary>
12174 <primary>pg_ts_dict_is_visible</primary>
12177 <primary>pg_ts_parser_is_visible</primary>
12180 <primary>pg_ts_template_is_visible</primary>
12183 <primary>pg_type_is_visible</primary>
12187 Each function performs the visibility check for one type of database
12188 object. Note that <function>pg_table_is_visible</function> can also be used
12189 with views, indexes and sequences; <function>pg_type_is_visible</function>
12190 can also be used with domains. For functions and operators, an object in
12191 the search path is visible if there is no object of the same name
12192 <emphasis>and argument data type(s)</> earlier in the path. For operator
12193 classes, both name and associated index access method are considered.
12197 All these functions require object OIDs to identify the object to be
12198 checked. If you want to test an object by name, it is convenient to use
12199 the OID alias types (<type>regclass</>, <type>regtype</>,
12200 <type>regprocedure</>, <type>regoperator</>, <type>regconfig</>,
12201 or <type>regdictionary</>),
12204 SELECT pg_type_is_visible('myschema.widget'::regtype);
12206 Note that it would not make much sense to test a non-schema-qualified
12207 type name in this way — if the name can be recognized at all, it must be visible.
12211 <primary>format_type</primary>
12215 <primary>pg_get_keywords</primary>
12219 <primary>pg_get_viewdef</primary>
12223 <primary>pg_get_ruledef</primary>
12227 <primary>pg_get_functiondef</primary>
12231 <primary>pg_get_function_arguments</primary>
12235 <primary>pg_get_function_identity_arguments</primary>
12239 <primary>pg_get_function_result</primary>
12243 <primary>pg_get_indexdef</primary>
12247 <primary>pg_get_triggerdef</primary>
12251 <primary>pg_get_constraintdef</primary>
12255 <primary>pg_get_expr</primary>
12259 <primary>pg_get_userbyid</primary>
12263 <primary>pg_get_serial_sequence</primary>
12267 <primary>pg_tablespace_databases</primary>
12271 <primary>pg_typeof</primary>
12275 <xref linkend="functions-info-catalog-table"> lists functions that
12276 extract information from the system catalogs.
12279 <table id="functions-info-catalog-table">
12280 <title>System Catalog Information Functions</title>
12283 <row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry></row>
12288 <entry><literal><function>format_type</function>(<parameter>type_oid</parameter>, <parameter>typemod</>)</literal></entry>
12289 <entry><type>text</type></entry>
12290 <entry>get SQL name of a data type</entry>
12293 <entry><literal><function>pg_get_keywords</function>()</literal></entry>
12294 <entry><type>setof record</type></entry>
12295 <entry>get list of SQL keywords and their categories</entry>
12298 <entry><literal><function>pg_get_constraintdef</function>(<parameter>constraint_oid</parameter>)</literal></entry>
12299 <entry><type>text</type></entry>
12300 <entry>get definition of a constraint</entry>
12303 <entry><literal><function>pg_get_constraintdef</function>(<parameter>constraint_oid</parameter>, <parameter>pretty_bool</>)</literal></entry>
12304 <entry><type>text</type></entry>
12305 <entry>get definition of a constraint</entry>
12308 <entry><literal><function>pg_get_expr</function>(<parameter>expr_text</parameter>, <parameter>relation_oid</>)</literal></entry>
12309 <entry><type>text</type></entry>
12310 <entry>decompile internal form of an expression, assuming that any Vars
12311 in it refer to the relation indicated by the second parameter</entry>
12314 <entry><literal><function>pg_get_expr</function>(<parameter>expr_text</parameter>, <parameter>relation_oid</>, <parameter>pretty_bool</>)</literal></entry>
12315 <entry><type>text</type></entry>
12316 <entry>decompile internal form of an expression, assuming that any Vars
12317 in it refer to the relation indicated by the second parameter</entry>
12320 <entry><literal><function>pg_get_functiondef</function>(<parameter>func_oid</parameter>)</literal></entry>
12321 <entry><type>text</type></entry>
12322 <entry>get definition of a function</entry>
12325 <entry><literal><function>pg_get_function_arguments</function>(<parameter>func_oid</parameter>)</literal></entry>
12326 <entry><type>text</type></entry>
12327 <entry>get argument list of function's definition (with default values)</entry>
12330 <entry><literal><function>pg_get_function_identity_arguments</function>(<parameter>func_oid</parameter>)</literal></entry>
12331 <entry><type>text</type></entry>
12332 <entry>get argument list to identify a function (without default values)</entry>
12335 <entry><literal><function>pg_get_function_result</function>(<parameter>func_oid</parameter>)</literal></entry>
12336 <entry><type>text</type></entry>
12337 <entry>get <literal>RETURNS</> clause for function</entry>
12340 <entry><literal><function>pg_get_indexdef</function>(<parameter>index_oid</parameter>)</literal></entry>
12341 <entry><type>text</type></entry>
12342 <entry>get <command>CREATE INDEX</> command for index</entry>
12345 <entry><literal><function>pg_get_indexdef</function>(<parameter>index_oid</parameter>, <parameter>column_no</>, <parameter>pretty_bool</>)</literal></entry>
12346 <entry><type>text</type></entry>
12347 <entry>get <command>CREATE INDEX</> command for index,
12348 or definition of just one index column when
12349 <parameter>column_no</> is not zero</entry>
12352 <entry><literal><function>pg_get_ruledef</function>(<parameter>rule_oid</parameter>)</literal></entry>
12353 <entry><type>text</type></entry>
12354 <entry>get <command>CREATE RULE</> command for rule</entry>
12357 <entry><literal><function>pg_get_ruledef</function>(<parameter>rule_oid</parameter>, <parameter>pretty_bool</>)</literal></entry>
12358 <entry><type>text</type></entry>
12359 <entry>get <command>CREATE RULE</> command for rule</entry>
12362 <entry><literal><function>pg_get_serial_sequence</function>(<parameter>table_name</parameter>, <parameter>column_name</parameter>)</literal></entry>
12363 <entry><type>text</type></entry>
12364 <entry>get name of the sequence that a <type>serial</type> or <type>bigserial</type> column
12368 <entry><function>pg_get_triggerdef</function>(<parameter>trigger_oid</parameter>)</entry>
12369 <entry><type>text</type></entry>
12370 <entry>get <command>CREATE [ CONSTRAINT ] TRIGGER</> command for trigger</entry>
12373 <entry><literal><function>pg_get_userbyid</function>(<parameter>role_oid</parameter>)</literal></entry>
12374 <entry><type>name</type></entry>
12375 <entry>get role name with given OID</entry>
12378 <entry><literal><function>pg_get_viewdef</function>(<parameter>view_name</parameter>)</literal></entry>
12379 <entry><type>text</type></entry>
12380 <entry>get underlying <command>SELECT</command> command for view (<emphasis>deprecated</emphasis>)</entry>
12383 <entry><literal><function>pg_get_viewdef</function>(<parameter>view_name</parameter>, <parameter>pretty_bool</>)</literal></entry>
12384 <entry><type>text</type></entry>
12385 <entry>get underlying <command>SELECT</command> command for view (<emphasis>deprecated</emphasis>)</entry>
12388 <entry><literal><function>pg_get_viewdef</function>(<parameter>view_oid</parameter>)</literal></entry>
12389 <entry><type>text</type></entry>
12390 <entry>get underlying <command>SELECT</command> command for view</entry>
12393 <entry><literal><function>pg_get_viewdef</function>(<parameter>view_oid</parameter>, <parameter>pretty_bool</>)</literal></entry>
12394 <entry><type>text</type></entry>
12395 <entry>get underlying <command>SELECT</command> command for view</entry>
12398 <entry><literal><function>pg_tablespace_databases</function>(<parameter>tablespace_oid</parameter>)</literal></entry>
12399 <entry><type>setof oid</type></entry>
12400 <entry>get the set of database OIDs that have objects in the tablespace</entry>
12403 <entry><literal><function>pg_typeof</function>(<parameter>any</parameter>)</literal></entry>
12404 <entry><type>regtype</type></entry>
12405 <entry>get the data type of any value</entry>
12412 <function>format_type</function> returns the SQL name of a data type that
12413 is identified by its type OID and possibly a type modifier. Pass NULL
12414 for the type modifier if no specific modifier is known.
12418 <function>pg_get_keywords</function> returns a set of records describing
12419 the SQL keywords recognized by the server. The <structfield>word</> column
12420 contains the keyword. The <structfield>catcode</> column contains a
12421 category code: <literal>U</> for unreserved, <literal>C</> for column name,
12422 <literal>T</> for type or function name, or <literal>R</> for reserved.
12423 The <structfield>catdesc</> column contains a possibly-localized string
12424 describing the category.
12428 <function>pg_get_constraintdef</function>,
12429 <function>pg_get_indexdef</function>, <function>pg_get_ruledef</function>,
12430 and <function>pg_get_triggerdef</function>, respectively reconstruct the
12431 creating command for a constraint, index, rule, or trigger. (Note that this
12432 is a decompiled reconstruction, not the original text of the command.)
12433 <function>pg_get_expr</function> decompiles the internal form of an
12434 individual expression, such as the default value for a column. It can be
12435 useful when examining the contents of system catalogs. If the expression
12436 might contain Vars, specify the OID of the relation they refer to as the
12437 second parameter; if no Vars are expected, zero is sufficient.
12438 <function>pg_get_viewdef</function> reconstructs the <command>SELECT</>
12439 query that defines a view. Most of these functions come in two variants,
12440 one of which can optionally <quote>pretty-print</> the result. The
12441 pretty-printed format is more readable, but the default format is more
12442 likely to be interpreted the same way by future versions of
12443 <productname>PostgreSQL</>; avoid using pretty-printed output for dump
12444 purposes. Passing <literal>false</> for the pretty-print parameter yields
12445 the same result as the variant that does not have the parameter at all.
12449 <function>pg_get_functiondef</> returns a complete
12450 <command>CREATE OR REPLACE FUNCTION</> statement for a function.
12451 <function>pg_get_function_arguments</function> returns the argument list
12452 of a function, in the form it would need to appear in within
12453 <command>CREATE FUNCTION</>.
12454 <function>pg_get_function_result</function> similarly returns the
12455 appropriate <literal>RETURNS</> clause for the function.
12456 <function>pg_get_function_identity_arguments</function> returns the
12457 argument list necessary to identify a function, in the form it
12458 would need to appear in within <command>ALTER FUNCTION</>, for
12459 instance. This form omits default values.
12463 <function>pg_get_serial_sequence</function> returns the name of the
12464 sequence associated with a column, or NULL if no sequence is associated
12465 with the column. The first input parameter is a table name with
12466 optional schema, and the second parameter is a column name. Because
12467 the first parameter is potentially a schema and table, it is not treated
12468 as a double-quoted identifier, meaning it is lowercased by default,
12469 while the second parameter, being just a column name, is treated as
12470 double-quoted and has its case preserved. The function returns a value
12471 suitably formatted for passing to sequence functions (see <xref
12472 linkend="functions-sequence">). This association can be modified or
12473 removed with <command>ALTER SEQUENCE OWNED BY</>. (The function
12474 probably should have been called
12475 <function>pg_get_owned_sequence</function>; its current name reflects the fact
12476 that it's typically used with <type>serial</> or <type>bigserial</>
12481 <function>pg_get_userbyid</function> extracts a role's name given
12486 <function>pg_tablespace_databases</function> allows a tablespace to be
12487 examined. It returns the set of OIDs of databases that have objects stored
12488 in the tablespace. If this function returns any rows, the tablespace is not
12489 empty and cannot be dropped. To display the specific objects populating the
12490 tablespace, you will need to connect to the databases identified by
12491 <function>pg_tablespace_databases</function> and query their
12492 <structname>pg_class</> catalogs.
12496 <function>pg_typeof</function> returns the OID of the data type of the
12497 value that is passed to it. This can be helpful for troubleshooting or
12498 dynamically constructing SQL queries. The function is declared as
12499 returning <type>regtype</>, which is an OID alias type (see
12500 <xref linkend="datatype-oid">); this means that it is the same as an
12501 OID for comparison purposes but displays as a type name. For example:
12503 SELECT pg_typeof(33);
12510 SELECT typlen FROM pg_type WHERE oid = pg_typeof(33);
12519 <primary>col_description</primary>
12523 <primary>obj_description</primary>
12527 <primary>shobj_description</primary>
12531 <primary>comment</primary>
12532 <secondary sortas="database objects">about database objects</secondary>
12536 The functions shown in <xref linkend="functions-info-comment-table">
12537 extract comments previously stored with the <xref linkend="sql-comment"
12538 endterm="sql-comment-title"> command. A null value is returned if no
12539 comment could be found for the specified parameters.
12542 <table id="functions-info-comment-table">
12543 <title>Comment Information Functions</title>
12546 <row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry></row>
12551 <entry><literal><function>col_description</function>(<parameter>table_oid</parameter>, <parameter>column_number</parameter>)</literal></entry>
12552 <entry><type>text</type></entry>
12553 <entry>get comment for a table column</entry>
12556 <entry><literal><function>obj_description</function>(<parameter>object_oid</parameter>, <parameter>catalog_name</parameter>)</literal></entry>
12557 <entry><type>text</type></entry>
12558 <entry>get comment for a database object</entry>
12561 <entry><literal><function>obj_description</function>(<parameter>object_oid</parameter>)</literal></entry>
12562 <entry><type>text</type></entry>
12563 <entry>get comment for a database object (<emphasis>deprecated</emphasis>)</entry>
12566 <entry><literal><function>shobj_description</function>(<parameter>object_oid</parameter>, <parameter>catalog_name</parameter>)</literal></entry>
12567 <entry><type>text</type></entry>
12568 <entry>get comment for a shared database object</entry>
12575 <function>col_description</function> returns the comment for a table column,
12576 which is specified by the OID of its table and its column number.
12577 <function>obj_description</function> cannot be used for table columns since
12578 columns do not have OIDs of their own.
12582 The two-parameter form of <function>obj_description</function> returns the
12583 comment for a database object specified by its OID and the name of the
12584 containing system catalog. For example,
12585 <literal>obj_description(123456,'pg_class')</literal>
12586 would retrieve the comment for the table with OID 123456.
12587 The one-parameter form of <function>obj_description</function> requires only
12588 the object OID. It is deprecated since there is no guarantee that
12589 OIDs are unique across different system catalogs; therefore, the wrong
12590 comment might be returned.
12594 <function>shobj_description</function> is used just like
12595 <function>obj_description</function> except it is used for retrieving
12596 comments on shared objects. Some system catalogs are global to all
12597 databases within each cluster and their descriptions are stored globally
12602 <primary>txid_current</primary>
12606 <primary>txid_current_snapshot</primary>
12610 <primary>txid_snapshot_xmin</primary>
12614 <primary>txid_snapshot_xmax</primary>
12618 <primary>txid_snapshot_xip</primary>
12622 <primary>txid_visible_in_snapshot</primary>
12626 The functions shown in <xref linkend="functions-txid-snapshot">
12627 provide server transaction information in an exportable form. The main
12628 use of these functions is to determine which transactions were committed
12629 between two snapshots.
12632 <table id="functions-txid-snapshot">
12633 <title>Transaction IDs and snapshots</title>
12636 <row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry></row>
12641 <entry><literal><function>txid_current</function>()</literal></entry>
12642 <entry><type>bigint</type></entry>
12643 <entry>get current transaction ID</entry>
12646 <entry><literal><function>txid_current_snapshot</function>()</literal></entry>
12647 <entry><type>txid_snapshot</type></entry>
12648 <entry>get current snapshot</entry>
12651 <entry><literal><function>txid_snapshot_xmin</function>(<parameter>txid_snapshot</parameter>)</literal></entry>
12652 <entry><type>bigint</type></entry>
12653 <entry>get xmin of snapshot</entry>
12656 <entry><literal><function>txid_snapshot_xmax</function>(<parameter>txid_snapshot</parameter>)</literal></entry>
12657 <entry><type>bigint</type></entry>
12658 <entry>get xmax of snapshot</entry>
12661 <entry><literal><function>txid_snapshot_xip</function>(<parameter>txid_snapshot</parameter>)</literal></entry>
12662 <entry><type>setof bigint</type></entry>
12663 <entry>get in-progress transaction IDs in snapshot</entry>
12666 <entry><literal><function>txid_visible_in_snapshot</function>(<parameter>bigint</parameter>, <parameter>txid_snapshot</parameter>)</literal></entry>
12667 <entry><type>boolean</type></entry>
12668 <entry>is transaction ID visible in snapshot? (do not use with subtransaction ids)</entry>
12675 The internal transaction ID type (<type>xid</>) is 32 bits wide and
12676 wraps around every 4 billion transactions. However, these functions
12677 export a 64-bit format that is extended with an <quote>epoch</> counter
12678 so it will not wrap around during the life of an installation.
12679 The data type used by these functions, <type>txid_snapshot</type>,
12680 stores information about transaction ID
12681 visibility at a particular moment in time. Its components are
12682 described in <xref linkend="functions-txid-snapshot-parts">.
12685 <table id="functions-txid-snapshot-parts">
12686 <title>Snapshot components</title>
12690 <entry>Name</entry>
12691 <entry>Description</entry>
12698 <entry><type>xmin</type></entry>
12700 Earliest transaction ID (txid) that is still active. All earlier
12701 transactions will either be committed and visible, or rolled
12707 <entry><type>xmax</type></entry>
12709 First as-yet-unassigned txid. All txids greater than or equal to this
12710 are not yet started as of the time of the snapshot, and thus invisible.
12715 <entry><type>xip_list</type></entry>
12717 Active txids at the time of the snapshot. The list
12718 includes only those active txids between <literal>xmin</>
12719 and <literal>xmax</>; there might be active txids higher
12720 than <literal>xmax</>. A txid that is <literal>xmin <= txid <
12721 xmax</literal> and not in this list was already completed
12722 at the time of the snapshot, and thus either visible or
12723 dead according to its commit status. The list does not
12724 include txids of subtransactions.
12733 <type>txid_snapshot</>'s textual representation is
12734 <literal><replaceable>xmin</>:<replaceable>xmax</>:<replaceable>xip_list</></literal>.
12735 For example <literal>10:20:10,14,15</literal> means
12736 <literal>xmin=10, xmax=20, xip_list=10, 14, 15</literal>.
12740 <sect1 id="functions-admin">
12741 <title>System Administration Functions</title>
12744 <xref linkend="functions-admin-set-table"> shows the functions
12745 available to query and alter run-time configuration parameters.
12748 <table id="functions-admin-set-table">
12749 <title>Configuration Settings Functions</title>
12752 <row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry></row>
12758 <literal><function>current_setting</function>(<parameter>setting_name</parameter>)</literal>
12760 <entry><type>text</type></entry>
12761 <entry>get current value of setting</entry>
12765 <literal><function>set_config(<parameter>setting_name</parameter>,
12766 <parameter>new_value</parameter>,
12767 <parameter>is_local</parameter>)</function></literal>
12769 <entry><type>text</type></entry>
12770 <entry>set parameter and return new value</entry>
12777 <primary>SET</primary>
12781 <primary>SHOW</primary>
12785 <primary>configuration</primary>
12786 <secondary sortas="server">of the server</secondary>
12787 <tertiary>functions</tertiary>
12791 The function <function>current_setting</function> yields the
12792 current value of the setting <parameter>setting_name</parameter>.
12793 It corresponds to the <acronym>SQL</acronym> command
12794 <command>SHOW</command>. An example:
12796 SELECT current_setting('datestyle');
12806 <function>set_config</function> sets the parameter
12807 <parameter>setting_name</parameter> to
12808 <parameter>new_value</parameter>. If
12809 <parameter>is_local</parameter> is <literal>true</literal>, the
12810 new value will only apply to the current transaction. If you want
12811 the new value to apply for the current session, use
12812 <literal>false</literal> instead. The function corresponds to the
12813 SQL command <command>SET</command>. An example:
12815 SELECT set_config('log_statement_stats', 'off', false);
12825 <primary>pg_cancel_backend</primary>
12828 <primary>pg_terminate_backend</primary>
12831 <primary>pg_reload_conf</primary>
12834 <primary>pg_rotate_logfile</primary>
12838 <primary>signal</primary>
12839 <secondary sortas="backend">backend processes</secondary>
12843 The functions shown in <xref
12844 linkend="functions-admin-signal-table"> send control signals to
12845 other server processes. Use of these functions is restricted
12849 <table id="functions-admin-signal-table">
12850 <title>Server Signalling Functions</title>
12853 <row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry>
12860 <literal><function>pg_cancel_backend</function>(<parameter>pid</parameter> <type>int</>)</literal>
12862 <entry><type>boolean</type></entry>
12863 <entry>Cancel a backend's current query</entry>
12867 <literal><function>pg_terminate_backend</function>(<parameter>pid</parameter> <type>int</>)</literal>
12869 <entry><type>boolean</type></entry>
12870 <entry>Terminate a backend</entry>
12874 <literal><function>pg_reload_conf</function>()</literal>
12876 <entry><type>boolean</type></entry>
12877 <entry>Cause server processes to reload their configuration files</entry>
12881 <literal><function>pg_rotate_logfile</function>()</literal>
12883 <entry><type>boolean</type></entry>
12884 <entry>Rotate server's log file</entry>
12891 Each of these functions returns <literal>true</literal> if
12892 successful and <literal>false</literal> otherwise.
12896 <function>pg_cancel_backend</> and <function>pg_terminate_backend</>
12897 send signals (<systemitem>SIGINT</> or <systemitem>SIGTERM</>
12898 respectively) to backend processes identified by process ID.
12899 The process ID of an active backend can be found from
12900 the <structfield>procpid</structfield> column of the
12901 <structname>pg_stat_activity</structname> view, or by listing the
12902 <command>postgres</command> processes on the server (using
12903 <application>ps</> on Unix or the <application>Task
12904 Manager</> on <productname>Windows</>).
12908 <function>pg_reload_conf</> sends a <systemitem>SIGHUP</> signal
12909 to the server, causing configuration files
12910 to be reloaded by all server processes.
12914 <function>pg_rotate_logfile</> signals the log-file manager to switch
12915 to a new output file immediately. This works only when the built-in
12916 log collector is running, since otherwise there is no log-file manager
12921 <primary>pg_start_backup</primary>
12924 <primary>pg_stop_backup</primary>
12927 <primary>pg_switch_xlog</primary>
12930 <primary>pg_current_xlog_location</primary>
12933 <primary>pg_current_xlog_insert_location</primary>
12936 <primary>pg_xlogfile_name_offset</primary>
12939 <primary>pg_xlogfile_name</primary>
12942 <primary>backup</primary>
12946 The functions shown in <xref
12947 linkend="functions-admin-backup-table"> assist in making on-line backups.
12948 Use of the first three functions is restricted to superusers.
12951 <table id="functions-admin-backup-table">
12952 <title>Backup Control Functions</title>
12955 <row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry>
12962 <literal><function>pg_start_backup</function>(<parameter>label</> <type>text</> <optional>, <parameter>fast</> <type>boolean</> </optional>)</literal>
12964 <entry><type>text</type></entry>
12965 <entry>Prepare for performing on-line backup</entry>
12969 <literal><function>pg_stop_backup</function>()</literal>
12971 <entry><type>text</type></entry>
12972 <entry>Finish performing on-line backup</entry>
12976 <literal><function>pg_switch_xlog</function>()</literal>
12978 <entry><type>text</type></entry>
12979 <entry>Force switch to a new transaction log file</entry>
12983 <literal><function>pg_current_xlog_location</function>()</literal>
12985 <entry><type>text</type></entry>
12986 <entry>Get current transaction log write location</entry>
12990 <literal><function>pg_current_xlog_insert_location</function>()</literal>
12992 <entry><type>text</type></entry>
12993 <entry>Get current transaction log insert location</entry>
12997 <literal><function>pg_xlogfile_name_offset</function>(<parameter>location</> <type>text</>)</literal>
12999 <entry><type>text</>, <type>integer</></entry>
13000 <entry>Convert transaction log location string to file name and decimal byte offset within file</entry>
13004 <literal><function>pg_xlogfile_name</function>(<parameter>location</> <type>text</>)</literal>
13006 <entry><type>text</type></entry>
13007 <entry>Convert transaction log location string to file name</entry>
13014 <function>pg_start_backup</> accepts an
13015 arbitrary user-defined label for the backup. (Typically this would be
13016 the name under which the backup dump file will be stored.) The function
13017 writes a backup label file (<filename>backup_label</>) into the
13018 database cluster's data directory, performs a checkpoint,
13019 and then returns the backup's starting transaction log location as text.
13020 The user can ignore this result value, but it is
13021 provided in case it is useful.
13023 postgres=# select pg_start_backup('label_goes_here');
13029 There is an optional boolean second parameter. If <literal>true</>,
13030 it specifies executing <function>pg_start_backup</> as quickly as
13031 possible. This forces an immediate checkpoint which will cause a
13032 spike in I/O operations, slowing any concurrently executing queries.
13036 <function>pg_stop_backup</> removes the label file created by
13037 <function>pg_start_backup</>, and creates a backup history file in
13038 the transaction log archive area. The history file includes the label given to
13039 <function>pg_start_backup</>, the starting and ending transaction log locations for
13040 the backup, and the starting and ending times of the backup. The return
13041 value is the backup's ending transaction log location (which again
13042 can be ignored). After recording the ending location, the current
13043 transaction log insertion
13044 point is automatically advanced to the next transaction log file, so that the
13045 ending transaction log file can be archived immediately to complete the backup.
13049 <function>pg_switch_xlog</> moves to the next transaction log file, allowing the
13050 current file to be archived (assuming you are using continuous archiving).
13051 The return value is the ending transaction log location + 1 within the just-completed transaction log file.
13052 If there has been no transaction log activity since the last transaction log switch,
13053 <function>pg_switch_xlog</> does nothing and returns the start location
13054 of the transaction log file currently in use.
13058 <function>pg_current_xlog_location</> displays the current transaction log write
13059 location in the same format used by the above functions. Similarly,
13060 <function>pg_current_xlog_insert_location</> displays the current transaction log
13061 insertion point. The insertion point is the <quote>logical</> end
13062 of the transaction log
13063 at any instant, while the write location is the end of what has actually
13064 been written out from the server's internal buffers. The write location
13065 is the end of what can be examined from outside the server, and is usually
13066 what you want if you are interested in archiving partially-complete transaction log
13067 files. The insertion point is made available primarily for server
13068 debugging purposes. These are both read-only operations and do not
13069 require superuser permissions.
13073 You can use <function>pg_xlogfile_name_offset</> to extract the
13074 corresponding transaction log file name and byte offset from the results of any of the
13075 above functions. For example:
13077 postgres=# SELECT * FROM pg_xlogfile_name_offset(pg_stop_backup());
13078 file_name | file_offset
13079 --------------------------+-------------
13080 00000001000000000000000D | 4039624
13083 Similarly, <function>pg_xlogfile_name</> extracts just the transaction log file name.
13084 When the given transaction log location is exactly at a transaction log file boundary, both
13085 these functions return the name of the preceding transaction log file.
13086 This is usually the desired behavior for managing transaction log archiving
13087 behavior, since the preceding file is the last one that currently
13088 needs to be archived.
13092 For details about proper usage of these functions, see
13093 <xref linkend="continuous-archiving">.
13097 The functions shown in <xref linkend="functions-admin-dbsize"> calculate
13098 the disk space usage of database objects.
13102 <primary>pg_column_size</primary>
13105 <primary>pg_database_size</primary>
13108 <primary>pg_relation_size</primary>
13111 <primary>pg_size_pretty</primary>
13114 <primary>pg_tablespace_size</primary>
13117 <primary>pg_total_relation_size</primary>
13120 <table id="functions-admin-dbsize">
13121 <title>Database Object Size Functions</title>
13124 <row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry>
13130 <entry><literal><function>pg_column_size</function>(<type>any</type>)</literal></entry>
13131 <entry><type>int</type></entry>
13132 <entry>Number of bytes used to store a particular value (possibly compressed)</entry>
13136 <literal><function>pg_database_size</function>(<type>oid</type>)</literal>
13138 <entry><type>bigint</type></entry>
13139 <entry>Disk space used by the database with the specified OID</entry>
13143 <literal><function>pg_database_size</function>(<type>name</type>)</literal>
13145 <entry><type>bigint</type></entry>
13146 <entry>Disk space used by the database with the specified name</entry>
13150 <literal><function>pg_relation_size</function>(<parameter>relation</parameter> <type>regclass</type>, <parameter>fork</parameter> <type>text</type>)</literal>
13152 <entry><type>bigint</type></entry>
13154 Disk space used by the specified fork (<literal>'main'</literal>,
13155 <literal>'fsm'</literal> or <literal>'vm'</>)
13156 of the table or index with the specified OID or name
13161 <literal><function>pg_relation_size</function>(<parameter>relation</parameter> <type>regclass</type>)</literal>
13163 <entry><type>bigint</type></entry>
13165 Shorthand for <literal>pg_relation_size(..., 'main')</literal>
13170 <literal><function>pg_size_pretty</function>(<type>bigint</type>)</literal>
13172 <entry><type>text</type></entry>
13173 <entry>Converts a size in bytes into a human-readable format with size units</entry>
13177 <literal><function>pg_tablespace_size</function>(<type>oid</type>)</literal>
13179 <entry><type>bigint</type></entry>
13180 <entry>Disk space used by the tablespace with the specified OID</entry>
13184 <literal><function>pg_tablespace_size</function>(<type>name</type>)</literal>
13186 <entry><type>bigint</type></entry>
13187 <entry>Disk space used by the tablespace with the specified name</entry>
13191 <literal><function>pg_total_relation_size</function>(<type>regclass</type>)</literal>
13193 <entry><type>bigint</type></entry>
13195 Total disk space used by the table with the specified OID or name,
13196 including indexes and <acronym>TOAST</> data
13204 <function>pg_column_size</> shows the space used to store any individual
13209 <function>pg_database_size</function> and <function>pg_tablespace_size</>
13210 accept the OID or name of a database or tablespace, and return the total
13211 disk space used therein.
13215 <function>pg_relation_size</> accepts the OID or name of a table, index or
13216 toast table, and returns the size in bytes. Specifying
13217 <literal>'main'</literal> or leaving out the second argument returns the
13218 size of the main data fork of the relation. Specifying
13219 <literal>'fsm'</literal> returns the size of the
13220 Free Space Map (see <xref linkend="storage-fsm">) associated with the
13221 relation. Specifying <literal>'vm'</literal> returns the size of the
13222 Visibility Map (see <xref linkend="storage-vm">) associated with the
13227 <function>pg_size_pretty</> can be used to format the result of one of
13228 the other functions in a human-readable way, using kB, MB, GB or TB as
13233 <function>pg_total_relation_size</> accepts the OID or name of a
13234 table or toast table, and returns the size in bytes of the data
13235 and all associated indexes and toast tables.
13239 The functions shown in <xref
13240 linkend="functions-admin-genfile"> provide native access to
13241 files on the machine hosting the server. Only files within the
13242 database cluster directory and the <varname>log_directory</> can be
13243 accessed. Use a relative path for files in the cluster directory,
13244 and a path matching the <varname>log_directory</> configuration setting
13245 for log files. Use of these functions is restricted to superusers.
13248 <table id="functions-admin-genfile">
13249 <title>Generic File Access Functions</title>
13252 <row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry>
13259 <literal><function>pg_ls_dir</function>(<parameter>dirname</> <type>text</>)</literal>
13261 <entry><type>setof text</type></entry>
13262 <entry>List the contents of a directory</entry>
13266 <literal><function>pg_read_file</function>(<parameter>filename</> <type>text</>, <parameter>offset</> <type>bigint</>, <parameter>length</> <type>bigint</>)</literal>
13268 <entry><type>text</type></entry>
13269 <entry>Return the contents of a text file</entry>
13273 <literal><function>pg_stat_file</function>(<parameter>filename</> <type>text</>)</literal>
13275 <entry><type>record</type></entry>
13276 <entry>Return information about a file</entry>
13283 <primary>pg_ls_dir</primary>
13286 <function>pg_ls_dir</> returns all the names in the specified
13287 directory, except the special entries <quote><literal>.</></> and
13288 <quote><literal>..</></>.
13292 <primary>pg_read_file</primary>
13295 <function>pg_read_file</> returns part of a text file, starting
13296 at the given <parameter>offset</>, returning at most <parameter>length</>
13297 bytes (less if the end of file is reached first). If <parameter>offset</>
13298 is negative, it is relative to the end of the file.
13302 <primary>pg_stat_file</primary>
13305 <function>pg_stat_file</> returns a record containing the file
13306 size, last accessed time stamp, last modified time stamp,
13307 last file status change time stamp (Unix platforms only),
13308 file creation time stamp (Windows only), and a <type>boolean</type>
13309 indicating if it is a directory. Typical usages include:
13311 SELECT * FROM pg_stat_file('filename');
13312 SELECT (pg_stat_file('filename')).modification;
13317 The functions shown in <xref linkend="functions-advisory-locks"> manage
13318 advisory locks. For details about proper use of these functions, see
13319 <xref linkend="advisory-locks">.
13322 <table id="functions-advisory-locks">
13323 <title>Advisory Lock Functions</title>
13326 <row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry>
13333 <literal><function>pg_advisory_lock</function>(<parameter>key</> <type>bigint</>)</literal>
13335 <entry><type>void</type></entry>
13336 <entry>Obtain exclusive advisory lock</entry>
13340 <literal><function>pg_advisory_lock</function>(<parameter>key1</> <type>int</>, <parameter>key2</> <type>int</>)</literal>
13342 <entry><type>void</type></entry>
13343 <entry>Obtain exclusive advisory lock</entry>
13348 <literal><function>pg_advisory_lock_shared</function>(<parameter>key</> <type>bigint</>)</literal>
13350 <entry><type>void</type></entry>
13351 <entry>Obtain shared advisory lock</entry>
13355 <literal><function>pg_advisory_lock_shared</function>(<parameter>key1</> <type>int</>, <parameter>key2</> <type>int</>)</literal>
13357 <entry><type>void</type></entry>
13358 <entry>Obtain shared advisory lock</entry>
13363 <literal><function>pg_try_advisory_lock</function>(<parameter>key</> <type>bigint</>)</literal>
13365 <entry><type>boolean</type></entry>
13366 <entry>Obtain exclusive advisory lock if available</entry>
13370 <literal><function>pg_try_advisory_lock</function>(<parameter>key1</> <type>int</>, <parameter>key2</> <type>int</>)</literal>
13372 <entry><type>boolean</type></entry>
13373 <entry>Obtain exclusive advisory lock if available</entry>
13378 <literal><function>pg_try_advisory_lock_shared</function>(<parameter>key</> <type>bigint</>)</literal>
13380 <entry><type>boolean</type></entry>
13381 <entry>Obtain shared advisory lock if available</entry>
13385 <literal><function>pg_try_advisory_lock_shared</function>(<parameter>key1</> <type>int</>, <parameter>key2</> <type>int</>)</literal>
13387 <entry><type>boolean</type></entry>
13388 <entry>Obtain shared advisory lock if available</entry>
13393 <literal><function>pg_advisory_unlock</function>(<parameter>key</> <type>bigint</>)</literal>
13395 <entry><type>boolean</type></entry>
13396 <entry>Release an exclusive advisory lock</entry>
13400 <literal><function>pg_advisory_unlock</function>(<parameter>key1</> <type>int</>, <parameter>key2</> <type>int</>)</literal>
13402 <entry><type>boolean</type></entry>
13403 <entry>Release an exclusive advisory lock</entry>
13408 <literal><function>pg_advisory_unlock_shared</function>(<parameter>key</> <type>bigint</>)</literal>
13410 <entry><type>boolean</type></entry>
13411 <entry>Release a shared advisory lock</entry>
13415 <literal><function>pg_advisory_unlock_shared</function>(<parameter>key1</> <type>int</>, <parameter>key2</> <type>int</>)</literal>
13417 <entry><type>boolean</type></entry>
13418 <entry>Release a shared advisory lock</entry>
13423 <literal><function>pg_advisory_unlock_all</function>()</literal>
13425 <entry><type>void</type></entry>
13426 <entry>Release all advisory locks held by the current session</entry>
13434 <primary>pg_advisory_lock</primary>
13437 <function>pg_advisory_lock</> locks an application-defined resource,
13438 which can be identified either by a single 64-bit key value or two
13439 32-bit key values (note that these two key spaces do not overlap).
13440 The key type is specified in <literal>pg_locks.objid</>. If
13441 another session already holds a lock on the same resource, the
13442 function will wait until the resource becomes available. The lock
13443 is exclusive. Multiple lock requests stack, so that if the same resource
13444 is locked three times it must be also unlocked three times to be
13445 released for other sessions' use.
13449 <primary>pg_advisory_lock_shared</primary>
13452 <function>pg_advisory_lock_shared</> works the same as
13453 <function>pg_advisory_lock</>,
13454 except the lock can be shared with other sessions requesting shared locks.
13455 Only would-be exclusive lockers are locked out.
13459 <primary>pg_try_advisory_lock</primary>
13462 <function>pg_try_advisory_lock</> is similar to
13463 <function>pg_advisory_lock</>, except the function will not wait for the
13464 lock to become available. It will either obtain the lock immediately and
13465 return <literal>true</>, or return <literal>false</> if the lock cannot be
13466 acquired immediately.
13470 <primary>pg_try_advisory_lock_shared</primary>
13473 <function>pg_try_advisory_lock_shared</> works the same as
13474 <function>pg_try_advisory_lock</>, except it attempts to acquire
13475 a shared rather than an exclusive lock.
13479 <primary>pg_advisory_unlock</primary>
13482 <function>pg_advisory_unlock</> will release a previously-acquired
13483 exclusive advisory lock. It
13484 returns <literal>true</> if the lock is successfully released.
13485 If the lock was not held, it will return <literal>false</>,
13486 and in addition, an SQL warning will be raised by the server.
13490 <primary>pg_advisory_unlock_shared</primary>
13493 <function>pg_advisory_unlock_shared</> works the same as
13494 <function>pg_advisory_unlock</>,
13495 except it releases a shared advisory lock.
13499 <primary>pg_advisory_unlock_all</primary>
13502 <function>pg_advisory_unlock_all</> will release all advisory locks
13503 held by the current session. (This function is implicitly invoked
13504 at session end, even if the client disconnects ungracefully.)
13509 <sect1 id="functions-trigger">
13510 <title>Trigger Functions</title>
13513 <primary>suppress_redundant_updates_trigger</primary>
13517 Currently <productname>PostgreSQL</> provides one built in trigger
13518 function, <function>suppress_redundant_updates_trigger</>,
13519 which will prevent any update
13520 that does not actually change the data in the row from taking place, in
13521 contrast to the normal behaviour which always performs the update
13522 regardless of whether or not the data has changed. (This normal behaviour
13523 makes updates run faster, since no checking is required, and is also
13524 useful in certain cases.)
13528 Ideally, you should normally avoid running updates that don't actually
13529 change the data in the record. Redundant updates can cost considerable
13530 unnecessary time, especially if there are lots of indexes to alter,
13531 and space in dead rows that will eventually have to be vacuumed.
13532 However, detecting such situations in client code is not
13533 always easy, or even possible, and writing expressions to detect
13534 them can be error-prone. An alternative is to use
13535 <function>suppress_redundant_updates_trigger</>, which will skip
13536 updates that don't change the data. You should use this with care,
13537 however. The trigger takes a small but non-trivial time for each record,
13538 so if most of the records affected by an update are actually changed,
13539 use of this trigger will actually make the update run slower.
13543 The <function>suppress_redundant_updates_trigger</> function can be
13544 added to a table like this:
13546 CREATE TRIGGER z_min_update
13547 BEFORE UPDATE ON tablename
13548 FOR EACH ROW EXECUTE PROCEDURE suppress_redundant_updates_trigger();
13550 In most cases, you would want to fire this trigger last for each row.
13551 Bearing in mind that triggers fire in name order, you would then
13552 choose a trigger name that comes after the name of any other trigger
13553 you might have on the table.
13556 For more information about creating triggers, see
13557 <xref linkend="SQL-CREATETRIGGER">.