Update of /cvsroot/conference/conference/planning
In directory pgfoundry.org:/tmp/cvs-serv96405
Log Message:
Init
Status:
Vendor Tag: plan
Release Tags: start
No conflicts created by this import
---(end of broadcast)---
TI
Log Message:
---
We neglected to apply domain constraints on UNKNOWN parameters to
prepared statements, per report from David Wheeler.
Tags:
REL7_4_STABLE
Modified Files:
--
pgsql/src/backend/parser:
parse_coerce.c (r2.111.2.1 -> r2.111.2.2)
(http://d
Log Message:
---
We neglected to apply domain constraints on UNKNOWN parameters to
prepared statements, per report from David Wheeler.
Tags:
REL8_0_STABLE
Modified Files:
--
pgsql/src/backend/parser:
parse_coerce.c (r2.126 -> r2.126.4.1)
(http://devel
Log Message:
---
We neglected to apply domain constraints on UNKNOWN parameters to
prepared statements, per report from David Wheeler.
Tags:
REL8_1_STABLE
Modified Files:
--
pgsql/src/backend/parser:
parse_coerce.c (r2.132.2.1 -> r2.132.2.2)
(http://d
Log Message:
---
We neglected to apply domain constraints on UNKNOWN parameters to
prepared statements, per report from David Wheeler.
Modified Files:
--
pgsql/src/backend/parser:
parse_coerce.c (r2.133 -> r2.134)
(http://developer.postgresql.org/cvsweb.cgi
Log Message:
---
Clear up remaining compile warning for plperl on Windows.
Modified Files:
--
pgsql/src/pl/plperl:
plperl.h (r1.1 -> r1.2)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plperl/plperl.h.diff?r1=1.1&r2=1.2)
Log Message:
---
mbutils was previously doing some allocations, including invoking
fmgr_info(), in the TopMemoryContext. I couldn't see that the code
actually leaked, but in general I think it's fragile to assume that
pfree'ing an FmgrInfo along with its fn_extra field is enough to
reclaim
Log Message:
---
Repair "Halloween problem" in EvalPlanQual: a tuple that's been inserted by
our own command (or more generally, xmin = our xact and cmin >= current
command ID) should not be seen as good. Else we may try to update rows
we already updated. This error was inserted last Augu
Log Message:
---
Repair "Halloween problem" in EvalPlanQual: a tuple that's been inserted by
our own command (or more generally, xmin = our xact and cmin >= current
command ID) should not be seen as good. Else we may try to update rows
we already updated. This error was inserted last Augu
Log Message:
---
Repair "Halloween problem" in EvalPlanQual: a tuple that's been inserted by
our own command (or more generally, xmin = our xact and cmin >= current
command ID) should not be seen as good. Else we may try to update rows
we already updated. This error was inserted last Augu
Log Message:
---
Repair "Halloween problem" in EvalPlanQual: a tuple that's been inserted by
our own command (or more generally, xmin = our xact and cmin >= current
command ID) should not be seen as good. Else we may try to update rows
we already updated. This error was inserted last Augu
Log Message:
---
Repair "Halloween problem" in EvalPlanQual: a tuple that's been inserted by
our own command (or more generally, xmin = our xact and cmin >= current
command ID) should not be seen as good. Else we may try to update rows
we already updated. This error was inserted last Augu
Log Message:
---
Use a more bulletproof test for whether finite() and isinf() are present.
It seems that recent gcc versions can optimize away calls to these functions
even when the functions do not exist on the platform, resulting in a bogus
positive result. Avoid this by using a non-cons
Log Message:
---
Use a more bulletproof test for whether finite() and isinf() are present.
It seems that recent gcc versions can optimize away calls to these functions
even when the functions do not exist on the platform, resulting in a bogus
positive result. Avoid this by using a non-cons
Log Message:
---
Use a more bulletproof test for whether finite() and isinf() are present.
It seems that recent gcc versions can optimize away calls to these functions
even when the functions do not exist on the platform, resulting in a bogus
positive result. Avoid this by using a non-cons
Log Message:
---
Use a more bulletproof test for whether finite() and isinf() are present.
It seems that recent gcc versions can optimize away calls to these functions
even when the functions do not exist on the platform, resulting in a bogus
positive result. Avoid this by using a non-cons
Log Message:
---
Use a more bulletproof test for whether finite() and isinf() are present.
It seems that recent gcc versions can optimize away calls to these functions
even when the functions do not exist on the platform, resulting in a bogus
positive result. Avoid this by using a non-cons
Log Message:
---
Remove extraneous backslash from 'fixseq.sql' example --- mea culpa
certainly. Per report from George Woodring.
Tags:
REL8_1_STABLE
Modified Files:
--
pgsql/doc/src/sgml:
release.sgml (r1.400.2.17 -> r1.400.2.18)
(http://developer.po
Log Message:
---
Remove extraneous backslash from 'fixseq.sql' example --- mea culpa
certainly. Per report from George Woodring.
Modified Files:
--
pgsql/doc/src/sgml:
release.sgml (r1.417 -> r1.418)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/sr
19 matches
Mail list logo
