aboutsummaryrefslogtreecommitdiff
path: root/contrib
Commit message (Collapse)AuthorAge
* Fix use of unportable %m formatPeter Eisentraut2011-07-07
|
* Make the file_fdw validator check that a filename option has been provided.Tom Lane2011-07-05
| | | | | | This was already a runtime failure condition, but it's better to check at validation time if possible. Lightly modified version of a patch by Shigeru Hanada.
* Postgres -> PostgreSQL in error messagePeter Eisentraut2011-07-05
|
* Make distprep and *clean build targets recurse into all subdirectories.Tom Lane2011-07-03
| | | | | | | | | | | | | | | | | | | Certain subdirectories do not get built if corresponding options are not selected at configure time. However, "make distprep" should visit such directories anyway, so that constructing derived files to be included in the tarball happens without requiring all configure options to be given in the tarball build script. Likewise, it's better if cleanup actions unconditionally visit all directories (for example, this ensures proper cleanup if someone has done a manual make in such a subdirectory). To handle this, set up a convention that subdirectories that are conditionally included in SUBDIRS should be added to ALWAYS_SUBDIRS instead when they are excluded. Back-patch to 9.1, so that plpython's spiexceptions.h will get provided in 9.1 tarballs. There don't appear to be any instances where distprep actions got missed in previous releases, and anyway this fix requires gmake 3.80 so we don't want to apply it before 9.1.
* Async dblink functions require a named connection, and therefore shouldJoe Conway2011-06-25
| | | | | use DBLINK_GET_NAMED_CONN rather than DBLINK_GET_CONN. Problem found by Peter Eisentraut and patch by Fujii Masao.
* In pg_upgrade, check that the binary and data directories are the sameBruce Momjian2011-06-22
| | | | | | | | major version. Backpatch to 9.1. Dan McGee
* Adjust pg_upgrade check for pg_upgrade_support to happen after theBruce Momjian2011-06-22
| | | | | | | | binary directory has been validated. Backpatch to 9.1. Dan McGee
* Fix pg_upgrade status message capitalization mistake.Bruce Momjian2011-06-22
| | | | | | Backpatch to 9.1 and 9.0. Dan McGee
* Apply upstream fix for blowfish signed-character bug (CVE-2011-2483).Tom Lane2011-06-21
| | | | | | | | | | | | | | | | | | | | | A password containing a character with the high bit set was misprocessed on machines where char is signed (which is most). This could cause the preceding one to three characters to fail to affect the hashed result, thus weakening the password. The result was also unportable, and failed to match some other blowfish implementations such as OpenBSD's. Since the fix changes the output for such passwords, upstream chose to provide a compatibility hack: password salts beginning with $2x$ (instead of the usual $2a$ for blowfish) are intentionally processed "wrong" to give the same hash as before. Stored password hashes can thus be modified if necessary to still match, though it'd be better to change any affected passwords. In passing, sync a couple other upstream changes that marginally improve performance and/or tighten error checking. Back-patch to all supported branches. Since this issue is already public, no reason not to commit the fix ASAP.
* In pg_upgrade, check there are no prepared transactions.Bruce Momjian2011-06-14
| | | | Backpatch to 9.1.
* Pgindent run before 9.1 beta2.Bruce Momjian2011-06-09
|
* Make citext's equality and hashing functions collation-insensitive.Tom Lane2011-06-08
| | | | | | | | | | | | | | This is an ugly hack to get around the fact that significant parts of the core backend assume they don't need to worry about passing collation to equality and hashing functions. That's true for the core string datatypes, but citext should ideally have equality behavior that depends on the specified collation's LC_CTYPE. However, there's no chance of fixing the core before 9.2, so we'll have to live with this compromise arrangement for now. Per bug #6053 from Regina Obe. The code changes in this commit should be reverted in full once the core code is up to speed, but be careful about reverting the docs changes: I fixed a number of obsolete statements while at it.
* Recode non-ASCII characters in source to UTF-8Peter Eisentraut2011-05-31
| | | | | | For consistency, have all non-ASCII characters from contributors' names in the source be in UTF-8. But remove some other more gratuitous uses of non-ASCII characters.
* Remove literal tabs from message stringsPeter Eisentraut2011-05-28
|
* In pg_upgrade, do case-insensitive checks of locale, encoding, and ctypeBruce Momjian2011-05-24
| | | | because these are often inconsistently capitalized.
* Replace strdup() with pstrdup(), to avoid leaking memory.Heikki Linnakangas2011-05-18
| | | | | It's been like this since the seg module was introduced, so backpatch to 8.2 which is the oldest supported version.
* In pg_upgrade, clean up handling of invalid directory specification byBruce Momjian2011-05-18
| | | | checking the stat() errno value more strictly.
* Improve pg_upgrade error reporting if the bin or data directories do notBruce Momjian2011-05-18
| | | | exist or are not directories.
* /contrib/foo -> contrib/fooPeter Eisentraut2011-05-19
| | | | | Since contrib is a relative directory specification, a leading slash is inappropriate.
* Improve pg_upgrade X_OK comment.Bruce Momjian2011-05-18
|
* Fix pg_upgrade build problem on Windows when using X_OK accessBruce Momjian2011-05-18
| | | | permission check on the current directory.
* Update pg_upgrade directory check error message.Bruce Momjian2011-05-16
|
* Add pg_upgrade check to make sure the user has full access permission inBruce Momjian2011-05-16
| | | | the current directory; if not, throw an error.
* Allow pg_upgrade to honor libpq environment variables. Add 'local'Bruce Momjian2011-05-16
| | | | checks for PGHOST and PGHOSTADDR.
* Fix assorted typosAlvaro Herrera2011-05-12
|
* Put options help in alphabetical orderPeter Eisentraut2011-05-10
|
* Format pg_upgrade --version in line with conventionsPeter Eisentraut2011-05-10
|
* Add bug report line to pg_upgrade --help outputPeter Eisentraut2011-05-10
|
* Put pg_test_fsync --help and --version output in line with conventionsPeter Eisentraut2011-05-10
| | | | Foremost, it should go to stdout.
* In pg_upgrade, remove suggestion of setting pg_hba.conf to 'trust', nowBruce Momjian2011-05-10
| | | | | that we report the libpq connection failure string. Per suggestion from Robert Haas.
* In pg_upgrade, add status message about superuser check.Bruce Momjian2011-05-09
|
* Add C comment why client encoding can be set in pg_upgrade.Bruce Momjian2011-05-07
|
* In pg_upgrade, report non-super-user username in error message.Bruce Momjian2011-05-07
|
* Check that the pg_upgrade user specified is a super-user.Bruce Momjian2011-05-07
| | | | | | Also report the error message when the post-pg_ctl connection fails. Per private bug report from EnterpriseDB.
* Adjust pg_upgrade FATAL error messages to have consistent newlines.Bruce Momjian2011-05-06
| | | | Also adjust some error message capitalization for consistency.
* Improve pg_archivecleanup and pg_standby --help outputPeter Eisentraut2011-05-05
| | | | | | | | For consistency with other tools, put the options before further usage information. In pg_standby, remove the supposedly deprecated -l option from the given example invocation.
* Improve formatting of pg_upgrade --help outputPeter Eisentraut2011-05-05
|
* Now that pg_upgrade uses -w in pg_ctl, remove loop that retried testingBruce Momjian2011-04-26
| | | | | | | the connection; also restructure the libpq connection code. This patch also removes the unused variable postmasterPID and fixes a libpq structure leak that was in the testing loop.
* In pg_upgrade, avoid one start/stop of the postmaster; use the -wBruce Momjian2011-04-25
| | | | | (wait) flag for pg_ctl start/stop; remove the unused "quiet" flag in the functions for starting/stopping the postmaster.
* Support "make check" in contribPeter Eisentraut2011-04-25
| | | | | | | | | | | | | | Added a new option --extra-install to pg_regress to arrange installing the respective contrib directory into the temporary installation. This is currently not yet supported for Windows MSVC builds. Updated the .gitignore files for contrib modules to ignore the leftovers of a temp-install check run. Changed the exit status of "make check" in a pgxs build (which still does nothing) to 0 from 1. Added "make check" in contrib to top-level "make check-world".
* Add postmaster/postgres undocumented -b option for binary upgrades.Bruce Momjian2011-04-25
| | | | | | | | | | This option turns off autovacuum, prevents non-super-user connections, and enables oid setting hooks in the backend. The code continues to use the old autoavacuum disable settings for servers with earlier catalog versions. This includes a catalog version bump to identify servers that support the -b option.
* In pg_upgrade, only compile copy_file() on non-Win32 systems.Bruce Momjian2011-04-23
| | | | Per report from Andrew Dunstan.
* Fix contrib/btree_gist to handle collations properly.Tom Lane2011-04-22
| | | | | | | Make use of the collation attached to the index column, instead of hard-wiring DEFAULT_COLLATION_OID. (Note: in theory this could require reindexing btree_gist indexes on textual columns, but I rather doubt anyone has one with a non-default declared collation as yet.)
* De-kludge contrib/btree_gin for collations.Tom Lane2011-04-22
| | | | | | | | | Using DEFAULT_COLLATION_OID in the comparePartial functions was not only a lame hack, but outright wrong, because the compare functions for collation-aware types were already responding to the declared index collation. So comparePartial would have the wrong expectation about the index's sort order, possibly leading to missing matches for prefix searches.
* Pg_upgrade C comment addition.Bruce Momjian2011-04-20
| | | | | Document why we do the missing new database check during the check phase.
* Throw error for mismatched pg_upgrade clustersBruce Momjian2011-04-19
| | | | | | | | | | If someone removes the 'postgres' database from the old cluster and the new cluster has a 'postgres' database, the number of databases will not match. We actually could upgrade such a setup, but it would violate the 1-to-1 mapping of database counts, so we throw an error instead. Previously they got an error during the upgrade, and not at the check stage; PG 9.0.4 does the same.
* Add C commentBruce Momjian2011-04-19
| | | | | Add C comment about why we throw an error if the pg_upgrade old/new database counts don't match.
* Refix the unaccent regression test on MSVC properlyPeter Eisentraut2011-04-19
| | | | | | ... for some value of "properly". Instead of overriding REGRESS_OPTS, set the variables ENCODING and NO_LOCALE, which is more expressive and allows overriding by the user. Fix vcregress.pl to handle that.
* Avoid unused variable warnings for certain configurationsPeter Eisentraut2011-04-19
|
* Attempt to remedy buildfarm breakage caused by commit f536d4194.Andrew Dunstan2011-04-18
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-27 11:10:05 +0000