30f96e3f96
please see the HISTORY file included in the Release, but a summary
consists of:
* Change encoding function signature to prevent misuse
* Change "contrib/tsearch2" to avoid unsafe use of INTERNAL function
results
* Repair race condition between relation extension and VACUUM
This could theoretically have caused loss of a page's worth of
freshly-inserted data, although the scenario seems of very low
probability. There are no known cases of it having caused more than
an Assert failure.
Security: http://www.postgresql.org/about/news.315
9 lines
556 B
Plaintext
9 lines
556 B
Plaintext
MD5 (postgresql/postgresql-base-7.4.8.tar.bz2) = c066dd74a746e15a49e0fded93a45329
|
|
SIZE (postgresql/postgresql-base-7.4.8.tar.bz2) = 6588745
|
|
MD5 (postgresql/postgresql-docs-7.4.8.tar.bz2) = c395130c09c98fdf333ef3ab1621b341
|
|
SIZE (postgresql/postgresql-docs-7.4.8.tar.bz2) = 2424249
|
|
MD5 (postgresql/postgresql-opt-7.4.8.tar.bz2) = b178144bdb13a2dd8eb0d17a49532296
|
|
SIZE (postgresql/postgresql-opt-7.4.8.tar.bz2) = 332225
|
|
MD5 (postgresql/postgresql-test-7.4.8.tar.bz2) = 9efb8ea9fb8a9424b98a0b4712d307b4
|
|
SIZE (postgresql/postgresql-test-7.4.8.tar.bz2) = 944435
|