Release date: never released
This release contains a variety of fixes from 7.4.19. For information about new features in the 7.4 major release, see Section E.311.
A dump/restore is not required for those running 7.4.X. However, if you are upgrading from a version earlier than 7.4.11, see Section E.300.
Fix conversions between ISO-8859-5 and other encodings
to handle Cyrillic “Yo” characters (
with two dots) (Sergey Burladyan)
Fix a few datatype input functions that were allowing unused bytes in their results to contain uninitialized, unpredictable values (Tom)
This could lead to failures in which two apparently
identical literal values were not seen as equal,
resulting in the parser complaining about unmatched
ORDER BY and
Fix a corner case in regular-expression substring
The problem occurs when there is a match to the
pattern overall but the user has specified a
parenthesized subexpression and that subexpression hasn't
got a match. An example is
substring('foo' from 'foo(bar)?'). This
should return NULL, since
(bar) isn't matched, but it was
mistakenly returning the whole-pattern match instead (ie,
Fix incorrect result from ecpg's
DatumGetBool macro to
not fail with gcc 4.3
This problem affects “old style” (V0) C functions that return boolean. The fix is already in 8.3, but the need to back-patch it was not realized at the time.
NOTIFY race condition (Tom)
In rare cases a session that had just executed a
LISTEN might not get a
notification, even though one would be expected because
the concurrent transaction executing
NOTIFY was observed to commit later.
A side effect of the fix is that a transaction that
has executed a not-yet-committed
LISTEN command will not see any row in
pg_listener for the
LISTEN, should it choose to
look; formerly it would have. This behavior was never
documented one way or the other, but it is possible that
some applications depend on the old behavior.
Fix display of constant expressions in
ORDER BY and
An explicitly casted constant would be shown incorrectly. This could for example lead to corruption of a view definition during dump and reload.
Fix libpq to handle NOTICE messages correctly during COPY OUT (Tom)
This failure has only been observed to occur when a user-defined datatype's output routine issues a NOTICE, but there is no guarantee it couldn't happen due to other causes.
If you see anything in the documentation that is not correct, does not match your experience with the particular feature or requires further clarification, please use this form to report a documentation issue.