aboutsummaryrefslogtreecommitdiff
path: root/contrib
Commit message (Collapse)AuthorAge
* Update pageinspect--1.0.sql to match the upgrade scriptAlvaro Herrera2011-02-25
| | | | Per comment from Tom
* Fix pageinspect's heap_page_item to return infomasks as 32 bit valuesAlvaro Herrera2011-02-25
| | | | | | | | | HeapTupleHeader's t_infomask and t_infomask2 are defined as 16-bit unsigned integers, so when the 16th bit was set, heap_page_item was returning them as negative values, which was ugly. The change to pageinspect--unpackaged--1.0.sql allows a module upgraded from 9.0 to be cleanly updated from the previous definition.
* Add ENCODING option to COPY TO/FROM and file_fdw.Itagaki Takahiro2011-02-21
| | | | | | | | | | | File encodings can be specified separately from client encoding. If not specified, client encoding is used for backward compatibility. Cases when the encoding doesn't match client encoding are slower than matched cases because we don't have conversion procs for other encodings. Performance improvement would be be a future work. Original patch by Hitoshi Harada, and modified by me.
* Minor logic fix for new levenshtein implementation.Tom Lane2011-02-20
| | | | Alexander Korotkov
* Add contrib/file_fdw foreign-data wrapper for reading files via COPY.Tom Lane2011-02-20
| | | | | | | | | | | | This is both very useful in its own right, and an important test case for the core FDW support. This commit includes a small refactoring of copy.c to expose its option checking code as a separately callable function. The original patch submission duplicated hundreds of lines of that code, which seemed pretty unmaintainable. Shigeru Hanada, reviewed by Itagaki Takahiro and Tom Lane
* One more hack to make contrib upgrades from 9.0 match fresh 9.1 installs.Tom Lane2011-02-18
| | | | | | | | | | | | | | | | | intarray and tsearch2 both reference core support functions in their GIN opclasses, and the signatures of those functions changed for 9.1. We added backwards-compatible pg_proc entries for the functions in order to allow 9.0 dump files to be restored at all, but that hack leaves the opclasses pointing at pg_proc entries different from what they'd point to if the contrib modules were installed fresh in 9.1. To forestall any possibility of future problems, fix the opclasses to match fresh installs via the expedient of direct UPDATEs on pg_amproc in the update-from-unpackaged scripts. (Yech ... but the alternatives are worse, or require far more effort than seems justified right now.) Note: updating pg_amproc is sufficient because there will be no pg_depend entries corresponding to these dependencies, since the referenced functions are all pinned.
* Fix upgrade of contrib/xml2 from 9.0.Tom Lane2011-02-17
| | | | | Update script was being sloppy about two functions that have been changed since 9.0.
* Fix upgrade of contrib/intarray and contrib/unaccent from 9.0.Tom Lane2011-02-17
| | | | | Take care of a couple of discrepancies between what you get from a fresh install and what the first-draft update-from-unpackaged scripts produced.
* Fix upgrade of contrib/btree_gist from 9.0.Tom Lane2011-02-17
| | | | | | | The initial version of the update-from-unpackaged script neglected to include the <> operators that were added to the opclasses during 9.1. To make this script produce the same final state as the regular install script, use the same ALTER OPERATOR FAMILY trick as in pg_trgm.
* Fix contrib/pg_trgm to have smoother updates from 9.0.Tom Lane2011-02-17
| | | | | | | | | | | | | | | Take care of some loose ends in the update-from-unpackaged script, and apply some ugly hacks to ensure that it produces the same catalog state as the fresh-install script. Per discussion, this seems like a safer plan than having two different catalog states that both call themselves "pg_trgm 1.0", even if it's not immediately clear that the subtle differences would ever matter. Also, fix the stub function gin_extract_trgm() so that it works instead of just bleating. Needed because this function will get called during a regular dump and reload, if there are any indexes using its opclass. The user won't have an opportunity to update the extension till later, so telling him to do so is unhelpful.
* Remove rule to build sepgsql-regtest.pp.Robert Haas2011-02-17
| | | | | | Instead, document how to build it manually. Per discussion. KaiGai Kohei, with some wordsmithing by me.
* Add backwards-compatible declarations of some core GIN support functions.Tom Lane2011-02-16
| | | | | | | | | These are needed to support reloading dumps of 9.0 installations containing contrib/intarray or contrib/tsearch2. Since not only regular dump/reload but binary upgrade would fail, it seems worth the trouble to carry these stubs for awhile. Note that the contrib opclasses referencing these functions will still work fine, since GIN doesn't actually pay any attention to the declared signature of a support function.
* In pg_upgrade, no need to initialize global struct values; they areBruce Momjian2011-02-16
| | | | always zeros. Also no need to free memory before we exit.
* Cleanup ClusterInfo initialization in pg_upgradeAlvaro Herrera2011-02-16
|
* Fix bug in 9.1 pg_upgrade processing of old/new relations; adjust debugBruce Momjian2011-02-15
| | | | output.
* Make pg_upgrade compile againAlvaro Herrera2011-02-15
|
* Adjust pg_upgrade error message, array freeing, and add error check.Bruce Momjian2011-02-15
|
* Bring hstore's comment into line with style of other contrib comments.Tom Lane2011-02-15
| | | | | All the other ones that are primarily a new datatype say "data type for <purpose>", so make this one similar.
* Rethink naming of contrib/intagg extension.Tom Lane2011-02-14
| | | | | | Initially it was called int_aggregate after the old SQL file, but since the documentation just says "intagg" and that's also the directory name, let's conform to that instead.
* More fixups for "unpackaged" conversion scripts.Tom Lane2011-02-13
|
* Assorted fixups for "unpackaged" conversion scripts.Tom Lane2011-02-13
| | | | | | | 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).
* Avoid use of CREATE OR REPLACE FUNCTION in extension installation files.Tom Lane2011-02-13
| | | | | | | | | | | 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 really want a failure to occur if there are any conflicts, else it's unclear what the extension-ownership state of the conflicted object ought to be. Most of the time, CREATE EXTENSION will fail anyway because of conflicts on other object types, but an extension defining only functions can succeed, with bad results.
* Convert contrib modules to use the extension facility.Tom Lane2011-02-13
| | | | | | | | | | | 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 very nonstandard installation process. Dimitri Fontaine and Tom Lane
* Properly handle Win32 paths of 'E:abc', which can be either absolute orBruce Momjian2011-02-12
| | | | | | relative, by creating a function path_is_relative_and_below_cwd() to check for specific requirements. It is unclear if this fixes a security problem or not but the new code is more robust.
* Add support for multiple versions of an extension and ALTER EXTENSION UPDATE.Tom Lane2011-02-11
| | | | | | | | | | | This follows recent discussions, so it's quite a bit different from Dimitri's original. There will probably be more changes once we get a bit of experience with it, but let's get it in and start playing with it. This is still just core code. I'll start converting contrib modules shortly. Dimitri Fontaine and Tom Lane
* Fix pg_upgrade to handle extensions.Tom Lane2011-02-09
| | | | | | | | | | | | | | | | | | | This follows my proposal of yesterday, namely that we try to recreate the previous state of the extension exactly, instead of allowing CREATE EXTENSION to run a SQL script that might create some entirely-incompatible on-disk state. In --binary-upgrade mode, pg_dump won't issue CREATE EXTENSION at all, but instead uses a kluge function provided by pg_upgrade_support to recreate the pg_extension row (and extension-level pg_depend entries) without creating any member objects. The member objects are then restored in the same way as if they weren't members, in particular using pg_upgrade's normal hacks to preserve OIDs that need to be preserved. Then, for each member object, ALTER EXTENSION ADD is issued to recreate the pg_depend entry that marks it as an extension member. In passing, fix breakage in pg_upgrade's enum-type support: somebody didn't fix it when the noise word VALUE got added to ALTER TYPE ADD. Also, rationalize parsetree representation of COMMENT ON DOMAIN and fix get_object_address() to allow OBJECT_DOMAIN.
* Per-column collation supportPeter Eisentraut2011-02-08
| | | | | | | | This adds collation support for columns and domains, a COLLATE clause to override it per expression, and B-tree index support. Peter Eisentraut reviewed by Pavel Stehule, Itagaki Takahiro, Robert Haas, Noah Misch
* Minor sepgsql regression test fixes.Robert Haas2011-02-02
|
* Various sepgsql corrections.Robert Haas2011-02-02
| | | | KaiGai Kohei
* Repair multiple breakage in Windows-specific code for appending '.exe'.Tom Lane2011-02-02
|
* Fix wrong verb in pg_upgrade text message, per Haas.Bruce Momjian2011-02-02
|
* Simplify pg_upgrade checking of executable permissions.Bruce Momjian2011-02-02
|
* Add pg_upgrade comment for why we can't use template1 inheritance forBruce Momjian2011-02-01
| | | | the support functions.
* Support LIKE and ILIKE index searches via contrib/pg_trgm indexes.Tom Lane2011-01-31
| | | | | | | | | | Unlike Btree-based LIKE optimization, this works for non-left-anchored search patterns. The effectiveness of the search depends on how many trigrams can be extracted from the pattern. (The worst case, with no trigrams, degrades to a full-table scan, so this isn't a panacea. But it can be very useful.) Alexander Korotkov, reviewed by Jan Urbanski
* Fix pg_upgrade to create pg_authid restore functions in the 'postgres'Bruce Momjian2011-01-31
| | | | database, not in the os-user database, per report from Magnus.
* Prevent buffer overrun while parsing an integer in a "query_int" value.Tom Lane2011-01-27
| | | | | | | | | | | | | | contrib/intarray's gettoken() uses a fixed-size buffer to collect an integer's digits, and did not guard against overrunning the buffer. This is at least a backend crash risk, and in principle might allow arbitrary code execution. The code didn't check for overflow of the integer value either, which while not presenting a crash risk was still bad. Thanks to Apple Inc's security team for reporting this issue and supplying the fix. Security: CVE-2010-4015
* Per Peter E, use 'kB' for kilobyte, not 'K'.Bruce Momjian2011-01-26
|
* In pg_test_fsync, use K(1024) rather than k(1000) for write size units.Bruce Momjian2011-01-26
|
* Adjust pg_test_fsync to always do XLOG_BLCKSZ-sized writes, rather thanBruce Momjian2011-01-25
| | | | | always 8k writes, per suggestion from Tom. Also adjust open_sync output layout.
* Use consistent spacing for PGAPPICON Makefile option.Bruce Momjian2011-01-24
|
* Use XLOG_BLCKSZ in pg_test_fsync, rather than our own define, but verifyBruce Momjian2011-01-24
| | | | it is 8k as expected.
* In test_open_sync(), writes kilobytes as intended, not by bytes.Bruce Momjian2011-01-24
|
* PGXS support for contrib/hstoreRobert Haas2011-01-23
| | | | Joey Adams
* First round of cleanup of sepgsql code and documentation.Robert Haas2011-01-23
| | | | Robert Haas, with a few suggestions from Thom Brown
* sepgsql, an SE-Linux integration for PostgreSQLRobert Haas2011-01-23
| | | | | | | | This is still pretty rough - among other things, the documentation needs work, and the messages need a visit from the style police - but this gets the basic framework in place. KaiGai Kohei
* More pg_test_fsync fixups.Tom Lane2011-01-22
| | | | | | | | | | Reduce #includes to minimum actually needed; in particular include postgres_fe.h not postgres.h, so as to stop build failures on some platforms. Use get_progname() instead of hardwired program name; improve error checking for command line syntax; bring error messages into line with style guidelines; include strerror result in die() cases.
* Suppress unused-variables warning when OPEN_SYNC_FLAG isn't defined.Tom Lane2011-01-22
| | | | Per buildfarm.
* More pg_test_fsync cleanup.Tom Lane2011-01-21
| | | | | | Un-break Windows build (I hope) by making the HAVE_FSYNC_WRITETHROUGH code match the backend. Fix incorrect program help message. static-ize all functions.
* Clean up pg_test_fsync commit.Tom Lane2011-01-21
| | | | | | Actually rename the program, rather than just claiming we did. Hook it into the build system. Get rid of useless dependency on libpq. Clean up #include list and messy whitespace.
* Update C banner on new pg_test_fsync file.Bruce Momjian2011-01-21
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-04 21:35:42 +0000