Log Message:
---
dbms_alert - first runable version
Modified Files:
--
orafce:
Makefile (r1.7 -> r1.8)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/orafce/orafce/Makefile.diff?r1=1.7&r2=1.8)
alert.c (r1.1 -> r1.2)
(http://cvs.pgfoundry.org/
Log Message:
---
Detoast query in g_intbig_consistent and copy query in g_int_consistent
Modified Files:
--
pgsql/contrib/intarray:
_int_gist.c (r1.10 -> r1.11)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/intarray/_int_gist.c.diff?r1=1.10&r2=1
Log Message:
---
Minor cleanups
Modified Files:
--
pgsql/contrib/intarray:
_int_gist.c (r1.11 -> r1.12)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/intarray/_int_gist.c.diff?r1=1.11&r2=1.12)
_intbig_gist.c (r1.9 -> r1.10)
(htt
At line 543 itup vector was filled by invalid tuple, so newly filled root
will contains only invalid tuples. Hence, reindex/vacuum full is required.
Hmm. That probably needs to be redesigned then. The problem is that as
the thing is written, you *must* reinit the buffer here --- the code
Log Message:
---
Detoast query in g_intbig_consistent and copy query in g_int_consistent.
Minor cleanups.
Tags:
REL8_1_STABLE
Modified Files:
--
pgsql/contrib/intarray:
_int_gist.c (r1.6 -> r1.6.2.1)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/c
Log Message:
---
Detoast query in g_intbig_consistent and copy query in g_int_consistent.
Minor cleanups.
Tags:
REL7_4_STABLE
Modified Files:
--
pgsql/contrib/intarray:
_int_gist.c (r1.2 -> r1.2.4.1)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/c
Log Message:
---
Detoast query in g_intbig_consistent and copy query in g_int_consistent.
Minor cleanups.
Tags:
REL8_0_STABLE
Modified Files:
--
pgsql/contrib/intarray:
_int_gist.c (r1.5 -> r1.5.4.1)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/c
>> Hmm. That probably needs to be redesigned then.
> Don't understand. Root will be fully regenerated and filled with invalid
> tuples.
Well, ISTM that if complete replay of the WAL sequence yields an invalid
index, then you've not got an adequate design for the WAL data. Special
recovery acti
Log Message:
---
Eliminate ajust scan code. Since concurrent GiST it doesn't
do real work. That was missed during concurrence development.
Modified Files:
--
pgsql/src/backend/access/gist:
gist.c (r1.131 -> r1.132)
(http://developer.postgresql.org/cvsweb.cg
Tom Lane wrote:
Hmm. That probably needs to be redesigned then.
Don't understand. Root will be fully regenerated and filled with invalid tuples.
Well, ISTM that if complete replay of the WAL sequence yields an invalid
index, then you've not got an adequate design for the WAL data. Specia
Log Message:
---
Fix thinko in gistRedoPageUpdateRecord: if XLR_BKP_BLOCK_1 is set, we
don't have anything to do to the page, but we still have to adjust the
incomplete_inserts list that we're maintaining in memory.
Modified Files:
--
pgsql/src/backend/access/gist:
Log Message:
---
Put flex'ed and bison'ed files in contrib in the distribution tarball, as
is done for the analogous files in the main distribution.
Modified Files:
--
pgsql:
GNUmakefile.in (r1.42 -> r1.43)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/
Log Message:
---
The version is now 7.03.0262.
1.Handle the converion from text-like field to SQL_C_BINARY more properly.
2.Make buffer extension in SQLPutData more effective.
3.Reply SQL_CONVERT_ correctly for SQLGetInfo request.
4.Reply DBMS_NAME, DBMS_VERSION correctly for SQLGetInfo
Log Message:
---
added a tooltip with detailed information on queries and errors
Modified Files:
--
pgfouine/include/reporting:
ReportAggregator.class.php (r1.13 -> r1.14)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/include/reporting/Repo
Log Message:
---
only display identified statistics if different from overall
Modified Files:
--
pgfouine/include/reporting/reports:
OverallStatsReport.class.php (r1.13 -> r1.14)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/include/reporti
Log Message:
---
Define a separately configurable XLOG_BLCKSZ symbol for the page size
used within WAL files. Historically this was the same as the data file
BLCKSZ, but there's no necessary connection, and it's possible that
performance gains might ensue from reducing XLOG_BLCKSZ. In any
Log Message:
---
Fix relation reference for notify warning.
Left overs from the refactor. [this one is thanks to pychecker ;]
Modified Files:
--
fe/src:
tracenull.py (r1.22 -> r1.23)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/fe/src/tracenull.py.d
17 matches
Mail list logo
