Eliminate xmin from hash tag for predicate locks on heap tuples.
If a tuple was frozen while its predicate locks mattered,
read-write dependencies could be missed, resulting in failure to
detect conflicts which could lead to anomalies in committed
serializable transactions.
This field was added t
Eliminate xmin from hash tag for predicate locks on heap tuples.
If a tuple was frozen while its predicate locks mattered,
read-write dependencies could be missed, resulting in failure to
detect conflicts which could lead to anomalies in committed
serializable transactions.
This field was added t
Eliminate xmin from hash tag for predicate locks on heap tuples.
If a tuple was frozen while its predicate locks mattered,
read-write dependencies could be missed, resulting in failure to
detect conflicts which could lead to anomalies in committed
serializable transactions.
This field was added t
Eliminate xmin from hash tag for predicate locks on heap tuples.
If a tuple was frozen while its predicate locks mattered,
read-write dependencies could be missed, resulting in failure to
detect conflicts which could lead to anomalies in committed
serializable transactions.
This field was added t
plpgsql: Add new option print_strict_params.
This option provides more detailed error messages when STRICT is used
and the number of rows returned is not one.
Marko Tiikkaja, reviewed by Ian Lawrence Barwick
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/689746c045
Make DISCARD SEQUENCES also discard the last used sequence.
Otherwise, we access already-freed memory. Oops.
Report by Michael Paquier. Fix by me.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/16a906f535082fcf3d8c6732d8e941e037bc6d5e
Modified Files
Translation updates
Branch
--
REL8_4_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/45336e837a99c6363c1914e5211389619d8d1009
Modified Files
--
src/backend/po/de.po|9 +-
src/backend/po/fr.po| 5699 +++
Translation updates
Branch
--
REL9_0_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/676f3d2e5a60f79527257af60548736c9c7ba87f
Modified Files
--
src/backend/po/de.po | 556 +-
src/backend/po/fr.po | 6556 +-
src/backend/po/it.po
Translation updates
Branch
--
REL9_3_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/4750eae3504e9d74eec883434cf275657d57bd25
Modified Files
--
src/backend/po/es.po|4 +-
src/backend/po/it.po| 524 ---
src/backend/po/z
Translation updates
Branch
--
REL9_2_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/4dd5c312fc0c661ab6e4a8dc4f104ce0c1abfc36
Modified Files
--
src/backend/po/de.po | 1206 ++---
src/backend/po/es.po | 6193
sr
Translation updates
Branch
--
REL9_1_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/1c4dfd19a6ebb3c2a0471f0a57b9f13d0ccd9d02
Modified Files
--
src/backend/po/de.po | 717 +-
src/backend/po/es.po | 1099 +-
src/backend/po/fr.po
Translation updates
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/0b109c822b599d64ff042e5535d9268b27e70969
Modified Files
--
src/backend/po/es.po|4 +-
src/backend/po/it.po| 524 ---
src/backend/po/zh_TW.po
Fix bugs in SSI tuple locking.
1. In heap_hot_search_buffer(), the PredicateLockTuple() call is passed
wrong offset number. heapTuple->t_self is set to the tid of the first
tuple in the chain that's visited, not the one actually being read.
2. CheckForSerializableConflictIn() uses the tuple's t_c
Fix bugs in SSI tuple locking.
1. In heap_hot_search_buffer(), the PredicateLockTuple() call is passed
wrong offset number. heapTuple->t_self is set to the tid of the first
tuple in the chain that's visited, not the one actually being read.
2. CheckForSerializableConflictIn() uses the tuple's t_c
Fix bugs in SSI tuple locking.
1. In heap_hot_search_buffer(), the PredicateLockTuple() call is passed
wrong offset number. heapTuple->t_self is set to the tid of the first
tuple in the chain that's visited, not the one actually being read.
2. CheckForSerializableConflictIn() uses the tuple's t_c
Fix bugs in SSI tuple locking.
1. In heap_hot_search_buffer(), the PredicateLockTuple() call is passed
wrong offset number. heapTuple->t_self is set to the tid of the first
tuple in the chain that's visited, not the one actually being read.
2. CheckForSerializableConflictIn() uses the tuple's t_c
TYPEALIGN doesn't work on int64 on 32-bit platforms.
The TYPEALIGN macro, and the related ones like MAXALIGN, don't work with
values larger than intptr_t, because TYPEALIGN casts the argument to
intptr_t to do the arithmetic. That's not a problem when dealing with
pointers or lengths or offsets re
Oops. Unbreak the 9.1 build.
I forgot to "git add" latest changes after backpatching the changes
for previous commit.
Branch
--
REL9_1_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/d81855129ba6115fe27cf204ca2912f9369bfa47
Modified Files
--
src/backend/access/hea
docs: update release notes for 8.4.18, 9.0.14, 9.1.10, 9.2.5, 9.3.1
Branch
--
REL9_2_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/df9ede9063915bca311a14a482d97ef51d2082d3
Modified Files
--
doc/src/sgml/release-8.4.sgml | 193
doc/src/sgml/r
docs: update release notes for 8.4.18, 9.0.14, 9.1.10, 9.2.5, 9.3.1
Branch
--
REL9_3_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/2589a5a59b9023b66710227750dab15cec68310f
Modified Files
--
doc/src/sgml/release-8.4.sgml | 193
doc/src/sgml/r
docs: update release notes for 8.4.18, 9.0.14, 9.1.10, 9.2.5, 9.3.1
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/1732ce4906c54937c5f36860e9f1493f693d5ba7
Modified Files
--
doc/src/sgml/release-8.4.sgml | 193
doc/src/sgml/release-
docs: update release notes for 8.4.18, 9.0.14, 9.1.10, 9.2.5, 9.3.1
Branch
--
REL9_0_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/b7854a0722c58c36b726a251e76fdb813e3081c1
Modified Files
--
doc/src/sgml/release-8.4.sgml | 193 +++
doc
docs: update release notes for 8.4.18, 9.0.14, 9.1.10, 9.2.5, 9.3.1
Branch
--
REL8_4_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/3ac00d87014ad8fcfce85a68a91f6f9f570c57cb
Modified Files
--
doc/src/sgml/release-8.4.sgml | 193 +++
docs: update release notes for 8.4.18, 9.0.14, 9.1.10, 9.2.5, 9.3.1
Branch
--
REL9_1_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/56e90da8da137c5a91c4086970b721c5ef7d6871
Modified Files
--
doc/src/sgml/release-8.4.sgml | 193 +
doc/src/s
Revert "Document support for VPATH builds of extensions."
This reverts commit 6ed3c5f7b2846be9e176ea1c99b2d45bba0d6972.
Branch
--
REL9_1_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/4a72c60e4a4ab3b60c809079924d019367428315
Modified Files
--
doc/src/sgml/extend.
Revert "Backpatch pgxs vpath build and installation fixes (v2)"
This reverts commit dd9abd3c995dbc4d32cfc97fde03fe3583e2717c.
pending resolution of
http://www.postgresql.org/message-id/[email protected]
Branch
--
REL9_2_STABLE
Details
---
http://git.postgresql.o
Revert "Backpatch pgxs vpath build and installation fixes (v2)"
This reverts commit 176c70b9f2ce382a5590e42afd7ba4edb87efecb.
pending resolution of
http://www.postgresql.org/message-id/[email protected]
Branch
--
REL9_1_STABLE
Details
---
http://git.postgresql.o
Revert "Backpatch pgxs vpath build and installation fixes."
This reverts commit f8110c5f66ad079e3dbc0b66bed06207c43643ef.
pending resolution of
http://www.postgresql.org/message-id/[email protected]
Branch
--
REL9_3_STABLE
Details
---
http://git.postgresql.org/p
Revert "Document support for VPATH builds of extensions."
This reverts commit 9598134e3030a883ff6eea8a822466ce5143ffeb.
Branch
--
REL9_3_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/4e80950042ff70a8d9825c1d9549692b8124dd40
Modified Files
--
doc/src/sgml/extend.
Revert "Ensure installation dirs are built before contents are installed (v2)"
This reverts commit 7f165f2587f6dafe7d4d438136dd959ed5610979.
pending resolution of
http://www.postgresql.org/message-id/[email protected]
Branch
--
REL9_3_STABLE
Details
---
http://g
Revert "Document support for VPATH builds of extensions."
This reverts commit 565beb41bdd73611ddb26165b7f6bb8b6157e49d.
Branch
--
REL9_2_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/e2ccba06ac73e0cd833c700467b0fead8b8bfdf2
Modified Files
--
doc/src/sgml/extend.
Stamp 9.2.5.
Branch
--
REL9_2_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/7800229b36d0444cf2c61f5c5895108ee5e8ee2a
Modified Files
--
configure| 18 +-
configure.in |2 +-
doc/bug.template
Stamp 9.0.14.
Branch
--
REL9_0_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/a65e6c8217bd9fdcdfc2cb69a39e7f6787f572c1
Modified Files
--
configure| 18 +-
configure.in |2 +-
doc/bug.template
Stamp 9.3.1.
Branch
--
REL9_3_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/b7f59e6d3e7c10ef0e222ce8ee6d19e8be304e29
Modified Files
--
configure| 18 +-
configure.in |2 +-
doc/bug.template
Stamp 8.4.18.
Branch
--
REL8_4_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/e6a8de2854bc94fc59b18c3643fd1d08ebfe268f
Modified Files
--
configure| 18 +-
configure.in |2 +-
doc/bug.template
Stamp 9.1.10.
Branch
--
REL9_1_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/b444726ef6642ed2289a1dc10fe53644dba05623
Modified Files
--
configure| 18 +-
configure.in |2 +-
doc/bug.template
(2013/10/08 10:35), Bruce Momjian wrote:
docs: update release notes for 8.4.18, 9.0.14, 9.1.10, 9.2.5, 9.3.1
Thank you for createing good release note. I have one comment.
In 9.1 and 9.2 release note, Is "Improve WAL segment timeline handling during
recovery" means commit which is "Install re
37 matches
Mail list logo
