[EMAIL PROTECTED] (Bruce Momjian) writes:
> Log Message:
> ---
> Add missing descriptions for aggregates, functions and conversions.
> Bernd Helmle
> Modified Files:
> --
> pgsql/src/backend/utils/mb/conversion_procs:
> Makefile (r1.19 -> r1.20)
>
> (http:
Log Message:
---
support for more constant types
Modified Files:
--
Npgsql2/src/Npgsql/SqlGenerators:
VisitedExpression.cs (r1.8 -> r1.9)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/npgsql/Npgsql2/src/Npgsql/SqlGenerators/VisitedExpression.cs.diff?r1=1.8&r
Log Message:
---
Support for more canonical functions
Modified Files:
--
Npgsql2/src/Npgsql/SqlGenerators:
SqlBaseGenerator.cs (r1.14 -> r1.15)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/npgsql/Npgsql2/src/Npgsql/SqlGenerators/SqlBaseGenerator.cs.diff?r1=
Log Message:
---
Add missing descriptions for aggregates, functions and conversions.
Bernd Helmle
Modified Files:
--
pgsql/src/backend/utils/mb/conversion_procs:
Makefile (r1.19 -> r1.20)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/mb
Log Message:
---
Fix possible duplicate tuples while GiST scan. Now page is processed
at once and ItemPointers are collected in memory.
Remove tuple's killing by killtuple() if tuple was moved to another
page - it could produce unaceptable overhead.
Backpatch up to 8.1 because the bug wa
Log Message:
---
Fix possible duplicate tuples while GiST scan. Now page is processed
at once and ItemPointers are collected in memory.
Remove tuple's killing by killtuple() if tuple was moved to another
page - it could produce unaceptable overhead.
Backpatch up to 8.1 because the bug wa
Log Message:
---
Fix possible duplicate tuples while GiST scan. Now page is processed
at once and ItemPointers are collected in memory.
Remove tuple's killing by killtuple() if tuple was moved to another
page - it could produce unaceptable overhead.
Backpatch up to 8.1 because the bug wa
Log Message:
---
Fix possible duplicate tuples while GiST scan. Now page is processed
at once and ItemPointers are collected in memory.
Remove tuple's killing by killtuple() if tuple was moved to another
page - it could produce unaceptable overhead.
Backpatch up to 8.1 because the bug wa
