Log Message:
---
Add trailing zero byte in Unicode codepoint conversion.
Modified Files:
--
pgsql/src/backend/utils/adt:
xml.c (r1.22 -> r1.23)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/xml.c.diff?r1=1.22&r2=1.23)
Log Message:
---
Reactivate libxml memory management via palloc, now that I think I've
classified the conditions under which this is safe to do (see source
code comment).
Modified Files:
--
pgsql/src/backend/utils/adt:
xml.c (r1.23 -> r1.24)
(http://develop
Log Message:
---
remove unnecessary and now inaccurate cast which I should have removed with
other old code.
Modified Files:
--
pgsql/src/pl/plperl:
plperl.c (r1.124 -> r1.125)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plperl/plperl.c.diff?r
Log Message:
---
Fixed expected files, so they are in sync with tests again.
Modified Files:
--
pgsql/src/interfaces/ecpg/test/expected:
compat_informix-dec_test-MinGW32.stdout (r1.1 -> r1.2)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/
Log Message:
---
Back-port changes of Jan 16 and 17 to "revoke" pending fsync requests during
DROP TABLE and DROP DATABASE. Should prevent unexpected "permission denied"
failures on Windows, and is cleaner on other platforms too since we no longer
have to take it on faith that ENOENT is ok
Log Message:
---
Back-port changes of Jan 16 and 17 to "revoke" pending fsync requests during
DROP TABLE and DROP DATABASE. Should prevent unexpected "permission denied"
failures on Windows, and is cleaner on other platforms too since we no longer
have to take it on faith that ENOENT is ok
Log Message:
---
Correct an old logic error in btree page splitting: when considering a split
exactly at the point where we need to insert a new item, the calculation used
the wrong size for the "high key" of the new left page. This could lead to
choosing an unworkable split, resulting in
Log Message:
---
Correct an old logic error in btree page splitting: when considering a split
exactly at the point where we need to insert a new item, the calculation used
the wrong size for the "high key" of the new left page. This could lead to
choosing an unworkable split, resulting in
Log Message:
---
Correct an old logic error in btree page splitting: when considering a split
exactly at the point where we need to insert a new item, the calculation used
the wrong size for the "high key" of the new left page. This could lead to
choosing an unworkable split, resulting in
Log Message:
---
Correct an old logic error in btree page splitting: when considering a split
exactly at the point where we need to insert a new item, the calculation used
the wrong size for the "high key" of the new left page. This could lead to
choosing an unworkable split, resulting in
Log Message:
---
Correct an old logic error in btree page splitting: when considering a split
exactly at the point where we need to insert a new item, the calculation used
the wrong size for the "high key" of the new left page. This could lead to
choosing an unworkable split, resulting in
Log Message:
---
Correct an old logic error in btree page splitting: when considering a split
exactly at the point where we need to insert a new item, the calculation used
the wrong size for the "high key" of the new left page. This could lead to
choosing an unworkable split, resulting in
Log Message:
---
Replaced old .spec file with more correct one.
Thanks, Devrim GUNDUZ!
Added Files:
---
dbi-link:
postgresql-dbi-link.spec (r1.1)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/dbi-link/dbi-link/postgresql-dbi-link.spec?rev=1.1&content-type=text/
Log Message:
---
Changed .spec file to point to the right spot.
Modified Files:
--
dbi-link:
postgresql-dbi-link.spec (r1.1 -> r1.2)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/dbi-link/dbi-link/postgresql-dbi-link.spec.diff?r1=1.1&r2=1.2)
---
Log Message:
---
Modify SGML makefile to allow 'gmake draft' to build draft html ('draft'
is now a target, no longer a modifier).
Modified Files:
--
pgsql/doc/src/sgml:
Makefile (r1.93 -> r1.94)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgm
Log Message:
---
Use sys_siglist[] to print out signal names for signal exits, rather
than just numbers.
Modified Files:
--
pgsql:
configure (r1.530 -> r1.531)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/configure.diff?r1=1.530&r2=1.531)
confi
Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> Could you please point me the discussion why we do not care 8.0
> regarding Windows specific issues? I could not find it...
It's not a completely done deal, but the folks listening in this
afternoon seemed to agree:
http://archives.postgresql.org/pgsql-ge
Log Message:
---
Fix scalararraysel() to cope with binary-compatible cases, such as text[]
versus varchar[]. This oversight probably explains Ryan Holmes' recent
complaint --- he was getting a generic selectivity estimate instead of
anything intelligent.
Modified Files:
--
Log Message:
---
Fix scalararraysel() to cope with binary-compatible cases, such as text[]
versus varchar[]. This oversight probably explains Ryan Holmes' recent
complaint --- he was getting a generic selectivity estimate instead of
anything intelligent.
Tags:
REL8_2_STABLE
Modified
Log Message:
---
Add signal.h for sys_siglist reference.
Modified Files:
--
pgsql/src/port:
exec.c (r1.49 -> r1.50)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/port/exec.c.diff?r1=1.49&r2=1.50)
---(end of broadcast)---
Log Message:
---
Add a delay at the start of the stats test, to let any prior stats
activity quiesce. Possibly this will fix the large increase in
non-reproducible stats test failures we've noted since turning on
stats_row_level by default.
Modified Files:
--
pgsql/src/tes
Log Message:
---
Dept of second thoughts: the IQ of estimate_array_length() needs to be
kept on par with that of scalararraysel(), else estimates that should
track might not. Hence teach it about binary-compatible cases, too.
Modified Files:
--
pgsql/src/backend/utils/adt:
Log Message:
---
Dept of second thoughts: the IQ of estimate_array_length() needs to be
kept on par with that of scalararraysel(), else estimates that should
track might not. Hence teach it about binary-compatible cases, too.
Tags:
REL8_2_STABLE
Modified Files:
--
pg
Log Message:
---
Use autoconf build-in sys_siglist macro AC_DECL_SYS_SIGLIST, rather than
create our own.
Modified Files:
--
pgsql:
configure (r1.531 -> r1.532)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/configure.diff?r1=1.531&r2=1.532)
conf
Log Message:
---
Clean up broken usage of HAVE_DECL_SYS_SIGLIST and inconsistent/poorly
formatted error messages.
Modified Files:
--
pgsql/src/port:
exec.c (r1.51 -> r1.52)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/port/exec.c.diff?r1=1.51&r2=1.
Log Message:
---
Drat, can't fit an additional argument into log_error. Is it worth an
sprintf pushup to be sure we can report something useful for out-of-range
exitstatus?
Modified Files:
--
pgsql/src/port:
exec.c (r1.52 -> r1.53)
(http://developer.postgr
26 matches
Mail list logo
