Fix the size of predicate lock manager's shared memory hash tables at creation.
This way they don't compete with the regular lock manager for the slack shared
memory, making the behavior more predictable.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/7c797e7194d969
TransferPredicateLocksToNewTarget should initialize a new lock
entry's commitSeqNo to that of the old one being transferred, or take
the minimum commitSeqNo if it is merging two lock entries.
Also, CreatePredicateLock should initialize commitSeqNo for to
InvalidSerCommitSeqNo instead of to 0. (I d
Teach pattern_fixed_prefix() about collations.
This is necessary, not optional, now that ILIKE and regexes are collation
aware --- else we might derive a wrong comparison constant for index
optimized pattern matches.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/3c
Log Message:
---
added PQclearTypes, PQclearSpecs, PQinitTypes, deprecated PQtypesRegister,
added SO version info to Makefile.am, bunped version to 1.5.0, and removed
automatic re-registration of types during a PQresetXXX
Modified Files:
--
libpqtypes:
ChangeLog (
Log Message:
---
removed expandRegisterTypes, changed return type of pqt_cleartypes to void,
passed -avoid-version and -no-undefined to linker in Makefile.am
Modified Files:
--
libpqtypes:
Makefile.am (r1.21 -> r1.22)
(http://cvs.pgfoundry.org/cgi-bin/cvsw
Log Message:
---
updated PQclearTypes.3 to point at PQinitTypes rather than PQregisterTypes man
page
Modified Files:
--
libpqtypes/docs/man3:
PQclearTypes.3 (r1.1 -> r1.2)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/libpqtypes/libpqtypes/docs/man3/PQclear
Clean up most -Wunused-but-set-variable warnings from gcc 4.6
This warning is new in gcc 4.6 and part of -Wall. This patch cleans
up most of the noise, but there are some still warnings that are
trickier to remove.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/5ca
Log Message:
---
updated changelog to reflect the correct changes made to Makefile.am
Modified Files:
--
libpqtypes:
ChangeLog (r1.57 -> r1.58)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/libpqtypes/libpqtypes/ChangeLog?r1=1.57&r2=1.58)
--
Sent via pgsql
Fix RI_Initial_Check to use a COLLATE clause when needed in its query.
If the referencing and referenced columns have different collations,
the parser will be unable to resolve which collation to use unless it's
helped out in this way. The effects are sometimes masked, if we end up
using a non-co
Be more wary of missing statistics in eqjoinsel_semi().
In particular, if we don't have real ndistinct estimates for both sides,
fall back to assuming that half of the left-hand rows have join partners.
This is what was done in 8.2 and 8.3 (cf nulltestsel() in those versions).
It's pretty stupid b
Be more wary of missing statistics in eqjoinsel_semi().
In particular, if we don't have real ndistinct estimates for both sides,
fall back to assuming that half of the left-hand rows have join partners.
This is what was done in 8.2 and 8.3 (cf nulltestsel() in those versions).
It's pretty stupid b
Be more wary of missing statistics in eqjoinsel_semi().
In particular, if we don't have real ndistinct estimates for both sides,
fall back to assuming that half of the left-hand rows have join partners.
This is what was done in 8.2 and 8.3 (cf nulltestsel() in those versions).
It's pretty stupid b
Suppress compiler warnings about "value computed is not used".
The recent patch to remove gcc 4.6 warnings created some new ones, at
least on my rather old gcc version. Try to make everybody happy by
casting to "void" when we just want to discard the result.
Branch
--
master
Details
---
13 matches
Mail list logo
