Log Message:
---
Restore restriction that pg_migrator must be built with the same new
server major version, because of PG_MODULE_MAGIC checks for shared
libraries.
Modified Files:
--
pg_migrator/src:
pg_migrator.c (r1.90 -> r1.91)
(http://cvs.pgfoundry.org/
Log Message:
---
Add point_ops opclass for GiST.
Modified Files:
--
pgsql/src/backend/access/gist:
gistproc.c (r1.19 -> r1.20)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/gist/gistproc.c?r1=1.19&r2=1.20)
pgsql/src/backend/utils/ad
Log Message:
---
Tags:
rel-stream-1-0
Removed Files:
-
src/externaltable/test:
Buffer.cc
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgexternaltable/src/externaltable/test/Buffer.cc)
Buffer.h
(http://cvs.pgfoundry.org/cgi-bin/cvsweb
Update of /cvsroot/pgexternaltable/src/externaltable/test/testbuffer
In directory pgfoundry.org:/tmp/cvs-serv84991/testbuffer
Log Message:
Directory /cvsroot/pgexternaltable/src/externaltable/test/testbuffer added to
the repository
--> Using per-directory sticky tag `rel-stream-1-0'
--
Sent vi
Log Message:
---
Tags:
rel-stream-1-0
Modified Files:
--
src/externaltable/exttab:
Makefile (r1.8.2.1 -> r1.8.2.2)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgexternaltable/src/externaltable/exttab/Makefile?r1=1.8.2.1&r2=1.8.2.2)
--
Sent via pgs
Log Message:
---
Tags:
rel-stream-1-0
Modified Files:
--
src/externaltable/exttab:
Buffer.h (r1.2 -> r1.2.2.1)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgexternaltable/src/externaltable/exttab/Buffer.h?r1=1.2&r2=1.2.2.1)
Interface_FileBuf
Log Message:
---
del streambuffer.*
Tags:
rel-stream-1-0
Removed Files:
-
src/externaltable/exttab:
streambuffer.cc
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgexternaltable/src/externaltable/exttab/streambuffer.cc)
streambuffer.h
Log Message:
---
del test.c
Tags:
rel-stream-1-0
Modified Files:
--
src/externaltable/test:
Buffer.h (r1.2 -> r1.2.2.1)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgexternaltable/src/externaltable/test/Buffer.h?r1=1.2&r2=1.2.2.1)
Interface_F
Log Message:
---
First part of refactoring of code for ResolveRecoveryConflict. Purposes
of this are to centralise the conflict code to allow further change,
as well as to allow passing through the full reason for the conflict
through to the conflicting backends. Backend state alters how we