summaryrefslogtreecommitdiff
path: root/contrib
AgeCommit message (Collapse)Author
2010-07-13On Win32, pg_upgrade cannot sent any server log output to the log fileBruce Momjian
because of file access limitations on that platform.
2010-07-13Remove incorrect email address for pg_upgrade bug reports.Bruce Momjian
2010-07-13In pg_upgrade, report /bin directory checks independent of /data checks.Bruce Momjian
2010-07-13In pg_upgrade, prevent psql AUTOCOMMIT=off by not loading .psqlrc.Bruce Momjian
2010-07-09Properly report errno/out-of-disk-space error from pg_upgrade when inBruce Momjian
copy mode, per report from depstein@alliedtesting.com. Patch suggestion from Magnus. Backpatch to 9.0.X.
2010-07-06pgindent run for 9.0, second runBruce Momjian
2010-07-05Fix a few single-file (MODULES, not MODULE_big) contrib makefiles that wereTom Lane
supposing that they should set SHLIB_LINK rather than LDFLAGS_SL. Since these don't go through Makefile.shlib that was a no-op on most platforms. Also regularize the few platform-specific Makefiles that did pay attention to SHLIB_LINK: it seems that the real value of that is to pull in BE_DLLLIBS, so do that instead. Per buildfarm failures on cygwin.
2010-07-03Make pg_upgrade copyrights just 2010, not 2010-2010.Bruce Momjian
2010-07-03Add copyrights to pg_upgrade and pg_upgrade_tools files, per Tom.Bruce Momjian
2010-07-03Add CVS tags to pg_upgrade and pg_upgrade_support files, per requestBruce Momjian
from Tom.
2010-07-02Remove hstore % text[] operator; use slice() function instead.Robert Haas
David Wheeler, with one small correction by me.
2010-07-01Get rid of some more stuff that duplicates c.h or port.h.Tom Lane
2010-07-01Remove port.h prototypes from pg_upgrade.h, per report from Robert Haas.Bruce Momjian
2010-06-23Add username designations to all pg_upgrade utility calls that support it.Bruce Momjian
2010-06-22Fix pg_upgrade's use of pg_ctl on Win32 to not send command and severBruce Momjian
output to the same file, because it is impossible. Also set user name for pg_dumpall in pg_upgrade.
2010-06-22Updated expected-output file for hstore.Robert Haas
This is an oversight in my previous patch to deprecate => as an operator name. Per buildfarm.
2010-06-18Rename hstore => text[] operator to %Robert Haas
This is not yet in any released version, so we still have the option to change the name. We may want to reserve the token => in a future release.
2010-06-17Clean up pg_archivecleanup's error and logging output: put newlines inTom Lane
sane places, make messages follow project's message style guidelines. Also, avoid closedir(NULL). Fujii Masao and Tom Lane
2010-06-16Fix pg_upgrade to remove malloc(0) call.Bruce Momjian
2010-06-15Fix storage of getopt() return, should be 'int', for pg_upgrade.Bruce Momjian
Steve Singer
2010-06-15Change the interpretation of the primary_key_attnums parameter ofTom Lane
dblink_build_sql_insert() and related functions. Now the column numbers are treated as logical not physical column numbers. This will provide saner behavior in the presence of dropped columns; furthermore, if we ever get around to allowing rearrangement of logical column ordering, the original definition would become nearly untenable from a usability standpoint. Per recent discussion of dblink's handling of dropped columns. Not back-patched for fear of breaking existing applications.
2010-06-15Remove hstore's text[] => text[] operator.Robert Haas
This is not yet in any released version, so we still have the option to backtrack. Instead, document hstore(text[], text[]). Per discussion.
2010-06-15Fix dblink_build_sql_insert() and related functions to handle droppedTom Lane
columns correctly. In passing, get rid of some dead logic in the underlying get_sql_insert() etc functions --- there is no caller that will pass null value-arrays to them. Per bug report from Robert Voinea.
2010-06-15Consolidate and improve checking of key-column-attnum arguments forTom Lane
dblink_build_sql_insert() and related functions. In particular, be sure to reject references to dropped and out-of-range column numbers. The numbers are still interpreted as physical column numbers, though, for backward compatibility. This patch replaces Joe's patch of 2010-02-03, which handled only some aspects of the problem.
2010-06-15Properly define pg_upgrade global variable, per bug report from ChrisBruce Momjian
Ruprecht on Mac (64 bit).
2010-06-14Rearrange dblink's dblink_build_sql_insert() and related routines to open andTom Lane
lock the target relation just once per SQL function call. The original coding obtained and released lock several times per call. Aside from saving a not-insignificant number of cycles, this eliminates possible race conditions if someone tries to modify the relation's schema concurrently. Also centralize locking and permission-checking logic. Problem noted while investigating a trouble report from Robert Voinea --- his problem is still to be fixed, though.
2010-06-14Files for pg_archivecleanupSimon Riggs
2010-06-14New contrib module for use as an archive_cleanup_command, or as aSimon Riggs
standalone utility for removing files from archive.
2010-06-12Update pg_upgrade C comment about cwd.Bruce Momjian
2010-06-12Have pg_upgrade create its output files in the current directory, ratherBruce Momjian
than in a subdirectory of the $HOME directory, or $TMP in Windows.
2010-06-09Avoid "identifier will be truncated" warning in dblinkItagaki Takahiro
when connection string is longer than NAMEDATALEN. The previous fix for long connection name broke the behavior.
2010-06-09Fix connection leak in dblink when dblink_connect() or dblink_connect_u()Itagaki Takahiro
end with "duplicate connection name" errors. Backported to release 7.4.
2010-06-07Add missed function dblink_connect_u(text[,text]) to uninstall scriptTeodor Sigaev
2010-06-03Fix dblink to treat connection names longer than NAMEDATALEN-2 (62 bytes).Itagaki Takahiro
Now long names are adjusted with truncate_identifier() and NOTICE messages are raised if names are actually truncated. Backported to release 8.0.
2010-05-25Remove IMPLEMENTATION.jp file from pg_upgrade docs; still in pgFoundryBruce Momjian
for pg_migrator, per suggestion from Magnus.
2010-05-25Update pg_upgrade IMPLEMENTATION doc file to match current 9.0 behavior.Bruce Momjian
2010-05-25Modify pg_standby, pgbench, and pg_upgrade manual pages to be consistentBruce Momjian
in their display of command-line options with other client applications.
2010-05-25Add Japanese Implementation file to CVS.Bruce Momjian
2010-05-25Re-order pg_upgrade 'help' options to be alphabetical.Bruce Momjian
2010-05-24In pg_upgrade, test for datallowconn instead of hardcoding template0.Bruce Momjian
2010-05-24Split apart pg_upgrade user lookup and root check so '--help' showsBruce Momjian
proper default username.
2010-05-23issue_warnings() has no business freeing its parameter, especially not whenTom Lane
its sole caller does that too. Jan Matousek, via Pavel Stehule
2010-05-19Simplify pg_upgrade queries by using IN instead of multiple OR clausesBruce Momjian
comparing the same column to multiple values.
2010-05-19For pg_upgrade, update template0's datfrozenxid and its relfrozenxids toBruce Momjian
match the behavior of autovacuum, which does this as the xid advances even if autovacuum is turned off.
2010-05-18Use a 'datallowconn' check for avoiding 'template0', rather thanBruce Momjian
hardcoding a 'template0' check, per suggestion from Alvaro. This might fix a problem where someone has allowed 'template0' connections, but it is a cleaner approach even if doesn't fix the bug.
2010-05-18Add pg_upgrade TESTING files explaining a testing method.Bruce Momjian
2010-05-15Adjust pg_upgrade BSD defines for scandir(), per report from Giles LeanBruce Momjian
2010-05-15Change bsdi define to __bsdi__Bruce Momjian
2010-05-15Fix typos in comments, spotted by Josh Kupershmidt.Heikki Linnakangas
2010-05-14Fix another obvious bug pointed out by a compiler warning.Tom Lane
generated by cgit v1.2.3 (git 2.46.0) at 2025-08-31 18:21:38 +0000