Log Message:
---
attached a META file for PGXN Manager
Added Files:
---
orafce:
META.json (r1.1)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/orafce/orafce/META.json?rev=1.1&content-type=text/x-cvsweb-markup)
--
Sent via pgsql-committers mailing list (pgsql-c
Fix bug introduced by recent SSI patch to merge ROLLED_BACK and
MARKED_FOR_DEATH flags into one. We still need the ROLLED_BACK flag to
mark transactions that are in the process of being rolled back. To be
precise, ROLLED_BACK now means that a transaction has already been
discounted from the count o
Fix bug in PreCommit_CheckForSerializationFailure. A transaction that has
already been marked as PREPARED cannot be killed. Kill the current
transaction instead.
One of the prepared_xacts regression tests actually hits this bug. I
removed the anomaly from the duplicate-gids test so that it fails i
Fix bug in PreCommit_CheckForSerializationFailure. A transaction that has
already been marked as PREPARED cannot be killed. Kill the current
transaction instead.
One of the prepared_xacts regression tests actually hits this bug. I
removed the anomaly from the duplicate-gids test so that it fails i
Fix bug introduced by recent SSI patch to merge ROLLED_BACK and
MARKED_FOR_DEATH flags into one. We still need the ROLLED_BACK flag to
mark transactions that are in the process of being rolled back. To be
precise, ROLLED_BACK now means that a transaction has already been
discounted from the count o
Adjust the alternative expected output file for prepared_xacts test case,
used when max_prepared_transactions=0, for the recent changes in the test
case.
Branch
--
REL9_1_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/35dd6d48eccbfcd2cb5b4e571e760e1c1f1534fc
Modified Files
--
Adjust the alternative expected output file for prepared_xacts test case,
used when max_prepared_transactions=0, for the recent changes in the test
case.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/38c0e7218065d9be47b16f2b36264bcefbabd046
Modified Files
-
Apply upstream fix for blowfish signed-character bug (CVE-2011-2483).
A password containing a character with the high bit set was misprocessed
on machines where char is signed (which is most). This could cause the
preceding one to three characters to fail to affect the hashed result,
thus weakeni
Apply upstream fix for blowfish signed-character bug (CVE-2011-2483).
A password containing a character with the high bit set was misprocessed
on machines where char is signed (which is most). This could cause the
preceding one to three characters to fail to affect the hashed result,
thus weakeni
Apply upstream fix for blowfish signed-character bug (CVE-2011-2483).
A password containing a character with the high bit set was misprocessed
on machines where char is signed (which is most). This could cause the
preceding one to three characters to fail to affect the hashed result,
thus weakeni
Apply upstream fix for blowfish signed-character bug (CVE-2011-2483).
A password containing a character with the high bit set was misprocessed
on machines where char is signed (which is most). This could cause the
preceding one to three characters to fail to affect the hashed result,
thus weakeni
Apply upstream fix for blowfish signed-character bug (CVE-2011-2483).
A password containing a character with the high bit set was misprocessed
on machines where char is signed (which is most). This could cause the
preceding one to three characters to fail to affect the hashed result,
thus weakeni
Apply upstream fix for blowfish signed-character bug (CVE-2011-2483).
A password containing a character with the high bit set was misprocessed
on machines where char is signed (which is most). This could cause the
preceding one to three characters to fail to affect the hashed result,
thus weakeni
Message style and spelling improvements
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/e2a0cb1a803b8a4a2b705728e13d61e6d2b17a71
Modified Files
--
src/backend/access/gist/gist.c |2 +-
src/backend/access/gist/gistvacuum.c |2 +-
sr
Message style and spelling improvements
Branch
--
REL9_1_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/a0b5146b25cd5924c5e5107c06b8777eec9f0a2f
Modified Files
--
src/backend/access/gist/gist.c |2 +-
src/backend/access/gist/gistvacuum.c |
Minor editing for README-SSI.
Fix some grammatical issues, try to clarify a couple of proofs, make the
terminology more consistent.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/a3290f655e12f43943bdabc9fd91477316af24a7
Modified Files
--
src/backend/sto
Minor editing for README-SSI.
Fix some grammatical issues, try to clarify a couple of proofs, make the
terminology more consistent.
Branch
--
REL9_1_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/0272fd1c008a616fd6f0c361645a335f86c5fe29
Modified Files
--
src/back
Performance tuning advice for SSI.
Kevin Grittner, with additional wordsmithing by me.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/771a9f69f70e0b4fa95347df7ab346e5bdbc85f2
Modified Files
--
doc/src/sgml/mvcc.sgml | 20
1 files c
Performance tuning advice for SSI.
Kevin Grittner, with additional wordsmithing by me.
Branch
--
REL9_1_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/66370f5158f2bca02202376204bfccdfdafd2bd4
Modified Files
--
doc/src/sgml/mvcc.sgml | 20
1
Add notion of a "transform function" that can simplify function calls.
Initially, we use this only to eliminate calls to the varchar()
function in cases where the length is not being reduced and, therefore,
the function call is equivalent to a RelabelType operation. The most
significant effect of
Make deadlock_timeout PGC_SUSET rather than PGC_SIGHUP.
This allows deadlock_timeout to be reduced for transactions that are
particularly likely to be involved in a deadlock, thus detecting it
more quickly. It is also potentially useful as a poor-man's deadlock
priority mechanism: a transaction w
Add smallserial pseudotype.
This is just like serial and bigserial, except it generates an int2
column rather than int4 or int8.
Mike Pultz, reviewed by Brar Piening and Josh Kupershmidt
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/61307dccc5f2f352d7dfed5c13abf3f
Add some regression tests for serial pseudotypes.
Josh Kupershmidt
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/431ab0e82819b31fcd1e33ecb52c2cd3b4b41da7
Modified Files
--
src/test/regress/expected/sequence.out | 108 ++--
s
Make the visibility map crash-safe.
This involves two main changes from the previous behavior. First,
when we set a bit in the visibility map, emit a new WAL record of type
XLOG_HEAP2_VISIBLE. Replay sets the page-level PD_ALL_VISIBLE bit and
the visibility map bit. Second, when inserting, upda
24 matches
Mail list logo
