~ubuntu-branches/ubuntu/utopic/postgresql-9.4/utopic-security

« back to all changes in this revision

Viewing changes to doc/src/sgml/html/functions-conditional.html

  • Committer: Package Import Robot
  • Author(s): Martin Pitt, CVE-2014-8161
  • Date: 2015-02-06 12:31:46 UTC
  • mfrom: (1.1.5) (7.1.2 utopic-proposed)
  • Revision ID: package-import@ubuntu.com-20150206123146-vtmf30jbkm7w16p8
Tags: 9.4.1-0ubuntu0.14.10
* New upstream security/bug fix release (LP: #1418928)
  - Fix buffer overruns in to_char() [CVE-2015-0241]
  - Fix buffer overruns in contrib/pgcrypto [CVE-2015-0243]
  - Fix possible loss of frontend/backend protocol synchronization after an
    error [CVE-2015-0244]
  - Fix information leak via constraint-violation error messages
    [CVE-2014-8161]
  - See release notes for details about other fixes:
    http://www.postgresql.org/about/news/1569/

Show diffs side-by-side

added added

removed removed

Lines of Context:
9
9
REV="MADE"
10
10
HREF="mailto:pgsql-docs@postgresql.org"><LINK
11
11
REL="HOME"
12
 
TITLE="PostgreSQL 9.4beta3 Documentation"
 
12
TITLE="PostgreSQL 9.4.1 Documentation"
13
13
HREF="index.html"><LINK
14
14
REL="UP"
15
15
TITLE="Functions and Operators"
26
26
HTTP-EQUIV="Content-Type"
27
27
CONTENT="text/html; charset=ISO-8859-1"><META
28
28
NAME="creation"
29
 
CONTENT="2014-10-06T18:35:22"></HEAD
 
29
CONTENT="2015-02-02T20:51:01"></HEAD
30
30
><BODY
31
31
CLASS="SECT1"
32
32
><DIV
44
44
VALIGN="bottom"
45
45
><A
46
46
HREF="index.html"
47
 
>PostgreSQL 9.4beta3 Documentation</A
 
47
>PostgreSQL 9.4.1 Documentation</A
48
48
></TH
49
49
></TR
50
50
><TR
388
388
><B
389
389
>Note: </B
390
390
>     As described in <A
391
 
HREF="xfunc-volatility.html"
392
 
>Section 35.6</A
393
 
>, functions and
394
 
     operators marked <TT
 
391
HREF="sql-expressions.html#SYNTAX-EXPRESS-EVAL"
 
392
>Section 4.2.14</A
 
393
>, there are various
 
394
     situations in which subexpressions of an expression are evaluated at
 
395
     different times, so that the principle that <SPAN
 
396
CLASS="QUOTE"
 
397
>"<TT
 
398
CLASS="TOKEN"
 
399
>CASE</TT
 
400
>
 
401
     evaluates only necessary subexpressions"</SPAN
 
402
> is not ironclad.  For
 
403
     example a constant <TT
395
404
CLASS="LITERAL"
396
 
>IMMUTABLE</TT
397
 
> can be evaluated when
398
 
     the query is planned rather than when it is executed.  This means
399
 
     that constant parts of a subexpression that is not evaluated during
400
 
     query execution might still be evaluated during query planning.
 
405
>1/0</TT
 
406
> subexpression will usually result in
 
407
     a division-by-zero failure at planning time, even if it's within
 
408
     a <TT
 
409
CLASS="TOKEN"
 
410
>CASE</TT
 
411
> arm that would never be entered at run time.
401
412
    </P
402
413
></BLOCKQUOTE
403
414
></DIV