Back-patch recent fixes for gistchoose and gistRelocateBuildBuffersOnSplit.
This back-ports commits c8ba697a4bdb934f0c51424c654e8db6133ea255 and
e5db11c5582b469c04a11f217a0f32c827da5dd7, which fix one definite and one
speculative bug in gistchoose, and make the code a lot more intelligible as
well
Back-patch recent fixes for gistchoose and gistRelocateBuildBuffersOnSplit.
This back-ports commits c8ba697a4bdb934f0c51424c654e8db6133ea255 and
e5db11c5582b469c04a11f217a0f32c827da5dd7, which fix one definite and one
speculative bug in gistchoose, and make the code a lot more intelligible as
well
Back-patch recent fixes for gistchoose and gistRelocateBuildBuffersOnSplit.
This back-ports commits c8ba697a4bdb934f0c51424c654e8db6133ea255 and
e5db11c5582b469c04a11f217a0f32c827da5dd7, which fix one definite and one
speculative bug in gistchoose, and make the code a lot more intelligible as
well
Back-patch recent fixes for gistchoose and gistRelocateBuildBuffersOnSplit.
This back-ports commits c8ba697a4bdb934f0c51424c654e8db6133ea255 and
e5db11c5582b469c04a11f217a0f32c827da5dd7, which fix one definite and one
speculative bug in gistchoose, and make the code a lot more intelligible as
well
Back-patch recent fixes for gistchoose and gistRelocateBuildBuffersOnSplit.
This back-ports commits c8ba697a4bdb934f0c51424c654e8db6133ea255 and
e5db11c5582b469c04a11f217a0f32c827da5dd7, which fix one definite and one
speculative bug in gistchoose, and make the code a lot more intelligible as
well
Improve coding of gistchoose and gistRelocateBuildBuffersOnSplit.
This is mostly cosmetic, but it does eliminate a speculative portability
issue. The previous coding ignored the fact that sum_grow could easily
overflow (in fact, it could be summing multiple IEEE float infinities).
On a platform w
Add Perl emacs formatting macros to src/tools/editors/emacs.samples.
Peter Eisentraut
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/5fcb58baca7a78e688b84275958c450670ba62a8
Modified Files
--
src/tools/editors/emacs.samples | 22 ++
Clarify FreeBSD instructions in pg_test_timing.
Josh Kupershmidt
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/c36b06a70d303c738f092f264585f621b6b30b29
Modified Files
--
doc/src/sgml/pgtesttiming.sgml | 11 ---
1 files changed, 8 insertions(+)
Properly document that SIGTERM is OK for users to use on a postgres
session, now that pg_terminate_backend() uses it.
Josh Kupershmidt
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/b5dc7612a5f66a08c6d46656d359fc1c69670f36
Modified Files
--
doc/src/sgml
Split tuple struct defs from htup.h to htup_details.h
This reduces unnecessary exposure of other headers through htup.h, which
is very widely included by many files.
I have chosen to move the function prototypes to the new file as well,
because that means htup.h no longer needs to include tupdesc
Revert 1fbc30f1dca6624c01a9a6a9ff711a7036c68532 because the
--enable-shared is about Plyton's configure, not ours.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/39d0653d058b87b437be05fd295ceb5bb4e9e05c
Modified Files
--
doc/src/sgml/installation.sgml |
Remove doc mention of --enable-shared, per Tom.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/1fbc30f1dca6624c01a9a6a9ff711a7036c68532
Modified Files
--
doc/src/sgml/installation.sgml |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
--
Sen
Document that max_locks_per_transaction might need to be increased for
queries on parent tables, per suggestion from Josh Berkus.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/39b42ecb059e24bb39a62d91fe57ab7b9ca5a2f5
Modified Files
--
doc/src/sgml/confi
Remove configure flag --disable-shared, as it is no longer used by any
port. The last use was QNX, per Peter Eisentraut.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/381a9ed66d8a601eb972be172e7251ca7f0e9d78
Modified Files
--
configure
Bruce Momjian writes:
> On Thu, Aug 30, 2012 at 03:02:28PM -0400, Robert Haas wrote:
>> On Thu, Aug 30, 2012 at 2:08 PM, Bruce Momjian wrote:
>>> I didn't think we backpatched error string changes because of
>>> translation churn.
>> Well, the patch that this was related to was back-patched, so
Fix checkpoint_timeout documentation to reflect current behavior.
Jeff Janes
Branch
--
REL9_2_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/d561fc5396e537452065c3531cb43edf11a8dbf0
Modified Files
--
doc/src/sgml/wal.sgml | 10 --
1 files changed, 4 inse
Fix checkpoint_timeout documentation to reflect current behavior.
Jeff Janes
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/9bedfbd02b48096f435c5b111591d4e5b717e547
Modified Files
--
doc/src/sgml/wal.sgml | 10 --
1 files changed, 4 insertions(
On Thu, Aug 30, 2012 at 03:02:28PM -0400, Robert Haas wrote:
> On Thu, Aug 30, 2012 at 2:08 PM, Bruce Momjian wrote:
> > On Thu, Aug 30, 2012 at 05:28:17PM +, Robert Haas wrote:
> >> Add missing period to detail message.
> >>
> >> Per note from Peter Eisentraut.
> >>
> >> Branch
> >> --
>
On Thu, Aug 30, 2012 at 2:08 PM, Bruce Momjian wrote:
> On Thu, Aug 30, 2012 at 05:28:17PM +, Robert Haas wrote:
>> Add missing period to detail message.
>>
>> Per note from Peter Eisentraut.
>>
>> Branch
>> --
>> REL8_3_STABLE
>>
>> Details
>> ---
>> http://git.postgresql.org/pg/commi
Document that log_autovacuum_min_duration can be used to monitor
autovacuum activity.
Per report from Marc Mamin
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/83fbfec383d7f7ef1331ba02db3d0fdf50abf112
Modified Files
--
doc/src/sgml/maintenance.sgml |
Suppress creation of backwardly-indexed paths for LATERAL join clauses.
Given a query such as
SELECT * FROM foo JOIN LATERAL (SELECT foo.var1) ss(x) ON ss.x = foo.var2
the existence of the join clause "ss.x = foo.var2" encourages indxpath.c to
build a parameterized path for foo using any index a
Document how to prevent PostgreSQL itself from exhausting memory.
The existing documentation in Linux Memory Overcommit seemed to
assume that PostgreSQL itself could never be the problem, or at
least it didn't tell you what to do about it.
Per discussion with Craig Ringer and Kevin Grittner.
Bra
Document how to prevent PostgreSQL itself from exhausting memory.
The existing documentation in Linux Memory Overcommit seemed to
assume that PostgreSQL itself could never be the problem, or at
least it didn't tell you what to do about it.
Per discussion with Craig Ringer and Kevin Grittner.
Bra
Document how to prevent PostgreSQL itself from exhausting memory.
The existing documentation in Linux Memory Overcommit seemed to
assume that PostgreSQL itself could never be the problem, or at
least it didn't tell you what to do about it.
Per discussion with Craig Ringer and Kevin Grittner.
Bra
Document how to prevent PostgreSQL itself from exhausting memory.
The existing documentation in Linux Memory Overcommit seemed to
assume that PostgreSQL itself could never be the problem, or at
least it didn't tell you what to do about it.
Per discussion with Craig Ringer and Kevin Grittner.
Bra
On Thu, Aug 30, 2012 at 05:28:17PM +, Robert Haas wrote:
> Add missing period to detail message.
>
> Per note from Peter Eisentraut.
>
> Branch
> --
> REL8_3_STABLE
>
> Details
> ---
> http://git.postgresql.org/pg/commitdiff/588fb3f01f7159990a9bfabb578615c3c32ffc6e
>
> Modified File
Add missing period to detail message.
Per note from Peter Eisentraut.
Branch
--
REL9_0_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/841ea92cba59bea8b8c9eda35960a673851dde98
Modified Files
--
src/backend/storage/lmgr/proc.c |2 +-
1 files changed, 1 insertion
Fix division by zero in the new range type histogram creation.
Report and analysis by Matthias.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/3e6eb0dd0a0982c61420a0d18d3e485bd2c2819c
Modified Files
--
src/backend/utils/adt/rangetypes_typanalyze.c |
Add missing period to detail message.
Per note from Peter Eisentraut.
Branch
--
REL9_1_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/657face6fea6e8e29944b839c4e5ceb6c63e251e
Modified Files
--
src/backend/storage/lmgr/proc.c |2 +-
1 files changed, 1 insertion
Add missing period to detail message.
Per note from Peter Eisentraut.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/a66fca3f0c8899ad360f0300d45cb1b7ac60a17f
Modified Files
--
src/backend/storage/lmgr/proc.c |2 +-
1 files changed, 1 insertions(+), 1
Add missing period to detail message.
Per note from Peter Eisentraut.
Branch
--
REL8_4_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/49ffbf52ec3dd2b15db620baba725f3623ee9fdb
Modified Files
--
src/backend/storage/lmgr/proc.c |2 +-
1 files changed, 1 insertion
Add missing period to detail message.
Per note from Peter Eisentraut.
Branch
--
REL8_3_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/588fb3f01f7159990a9bfabb578615c3c32ffc6e
Modified Files
--
src/backend/storage/lmgr/proc.c |2 +-
1 files changed, 1 insertion
Add missing period to detail message.
Per note from Peter Eisentraut.
Branch
--
REL9_2_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/640393080d863c69ae65ba0205e05cd3d4d438b0
Modified Files
--
src/backend/storage/lmgr/proc.c |2 +-
1 files changed, 1 insertion
Document that COPY OUT requires an absolute pathname.
As suggested by Etsuro Fujita, but with somewhat different wording.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/b9ea8d20fde981997425ba72de7aa23e319e753e
Modified Files
--
doc/src/sgml/ref/copy.sgm
Remove old documentation warnings about the use of bigint.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/48a9c7823e032fde54cb0658fbd488809a3fdc69
Modified Files
--
doc/src/sgml/datatype.sgml | 14 ++
1 files changed, 2 insertions(+), 12 del
Fix logic bug in gistchoose and gistRelocateBuildBuffersOnSplit.
Every time the best-tuple-found-so-far changes, we need to reset all
the penalty values in which_grow[] to the penalties for the new best
tuple. The old code failed to do this, resulting in inferior index
quality.
The original patc
Improve EXPLAIN's ability to cope with LATERAL references in plans.
push_child_plan/pop_child_plan didn't bother to adjust the "ancestors"
list of parent plan nodes when descending to a child plan node. I think
this was okay when it was written, but it's not okay in the presence of
LATERAL refere
Comment fixes.
Jeff Davis, somewhat edited by me
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/e1a6375d8f3a11f3447bea10883a4cbe1c5d3ec9
Modified Files
--
src/backend/commands/tablecmds.c |7 ---
src/backend/storage/file/reinit.c |1 -
2 file
Document that xslt-related RPMs may be needed to build docs.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/152525b5f3db9b7b58fa06e5d03725288f054b1d
Modified Files
--
doc/src/sgml/docguide.sgml |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
39 matches
Mail list logo