Fix obsolete references to old-style contrib installation methods.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/f1fb4b0e63a677cdc86de667c75142b88a4edb65
Modified Files
--
doc/src/sgml/contrib-spi.sgml | 15 +++
doc/src/sgml/contrib.sgml
Remove no-longer-needed special case hacks in MSVC build scripts.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/2ee69ff65de6e8626784d4a263953158ef480ab4
Modified Files
--
src/tools/msvc/Install.pm |3 ---
src/tools/msvc/Mkvcbuild.pm |5 -
2
More fixups for "unpackaged" conversion scripts.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/de06cfe834dfff283deddfe1eb2945ba8a4fde2a
Modified Files
--
contrib/sslinfo/sslinfo--unpackaged--1.0.sql | 12 ++--
contrib/xml2/xml2--unpackaged--1.0
Assorted fixups for "unpackaged" conversion scripts.
From first pass of testing. Notably, there seems to be no need for
adminpack--unpackaged--1.0.sql because none of the objects that the
old module creates would ever be dumped by pg_dump anyway (they are
all in pg_catalog).
Branch
--
master
Avoid use of CREATE OR REPLACE FUNCTION in extension installation files.
It was never terribly consistent to use OR REPLACE (because of the lack of
comparable functionality for data types, operators, etc), and
experimentation shows that it's now positively pernicious in the extension
world. We re
Convert contrib modules to use the extension facility.
This isn't fully tested as yet, in particular I'm not sure that the
"foo--unpackaged--1.0.sql" scripts are OK. But it's time to get some
buildfarm cycles on it.
sepgsql is not converted to an extension, mainly because it seems to
require a v
Support replacing MODULE_PATHNAME during extension script file execution.
This avoids the need to find a way to make PGXS' .sql.in-to-.sql rule
insert the right thing. We'll just deprecate use of that hack for
extensions.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitd
Change the naming convention for extension files to use double dashes.
This allows us to have an unambiguous rule for deconstructing the names
of script files and secondary control files, without having to forbid
extension and version names from containing any dashes. We do have to
forbid them fr
Clarify documentation for libpq's PQescapeBytea to mention the new hex
format.
Modify PQescapeStringConn() docs to be consisent with other escaping
functions.
Add mention problems with pre-9.0 versions of libpq using not understanding
bytea hex format to the 9.0 release notes.
Backpatch to 9.0 d
Clarify documentation for libpq's PQescapeBytea to mention the new hex
format.
Modify PQescapeStringConn() docs to be consisent with other escaping
functions.
Add mention problems with pre-9.0 versions of libpq using not understanding
bytea hex format to the 9.0 release notes.
Backpatch to 9.0 d
10 matches
Mail list logo
