- 17 1月, 2018 1 次提交
-
-
由 Heikki Linnakangas 提交于
A long time ago, they were disabled, because the GIN code had not been modified to work with file replication. Now with WAL replication, there's no reason to not support them.
-
- 21 11月, 2017 1 次提交
-
-
由 Heikki Linnakangas 提交于
These had been added in GPDB a long time ago, presumably to make the test output repeatable. But they're not needed anymore. Remove them to match the upstream more closely, which helps when merging.
-
- 14 2月, 2017 1 次提交
-
-
由 Heikki Linnakangas 提交于
It hasn't done anything since 2010. If I'm reading the commit log correctly, it was added and deprecated only a few months apart, and probably hasn't done anything in any released version.
-
- 18 12月, 2016 1 次提交
-
-
由 Daniel Gustafsson 提交于
This ignore regex was simply hiding the fact that one expected test output was broken. Remove the ignore and fix the test.
-
- 19 7月, 2016 1 次提交
-
-
- 07 6月, 2016 1 次提交
-
-
由 Heikki Linnakangas 提交于
Merging is easier, when the upstream regression test files (create_index) are as unmodified as possible, and any GPDB added tests are added to separate files (bitmap_index). Also, the only planner vs. ORCA differences in output were in the GPDB-added parts of this, so this allows removing the ORCA alternative expected output file for the create_index test.
-
- 15 4月, 2016 1 次提交
-
-
由 Jimmy Yih 提交于
Currently, the error reporting for duplicate key value violation for unique indexes does not contain useful information for users when debugging. This commit backports two commits from PostgreSQL (shown below) and updates our multikey tuplesort to use the same. Now the error will display the first instance of a duplicate key violation. Authors: Jimmy Yih and Abhijit Subramanya commit b680ae4b Author: Tom Lane <tgl@sss.pgh.pa.us> Date: Sat Aug 1 19:59:41 2009 +0000 Improve unique-constraint-violation error messages to include the exact values being complained of. In passing, also remove the arbitrary length limitation in the similar error detail message for foreign key violations. Itagaki Takahiro Conflicts: contrib/citext/expected/citext.out contrib/citext/expected/citext_1.out src/backend/access/common/indextuple.c src/backend/access/index/genam.c src/backend/access/nbtree/nbtinsert.c src/backend/utils/adt/ri_triggers.c src/backend/utils/adt/ruleutils.c src/include/access/genam.h src/include/access/itup.h src/include/utils/builtins.h src/test/regress/expected/alter_table.out src/test/regress/expected/arrays.out src/test/regress/expected/create_index.out src/test/regress/expected/plpgsql.out src/test/regress/expected/transactions.out src/test/regress/expected/uuid.out src/test/regress/output/constraints.source src/test/regress/output/tablespace.source commit 527f0ae3 Author: Tom Lane <tgl@sss.pgh.pa.us> Date: Sat Aug 1 20:59:17 2009 +0000 Department of second thoughts: let's show the exact key during unique index build failures, too. Refactor a bit more since that error message isn't spelled the same. Conflicts: src/backend/access/nbtree/nbtinsert.c src/backend/utils/sort/tuplesort.c src/test/regress/expected/alter_table.out src/test/regress/expected/create_index.out
-
- 28 10月, 2015 1 次提交
-
-
- 12 7月, 2008 1 次提交
-
-
由 Tom Lane 提交于
-
- 11 4月, 2008 1 次提交
-
-
由 Tom Lane 提交于
indexscan always occurs in one call, and the results are returned in a TIDBitmap instead of a limited-size array of TIDs. This should improve speed a little by reducing AM entry/exit overhead, and it is necessary infrastructure if we are ever to support bitmap indexes. In an only slightly related change, add support for TIDBitmaps to preserve (somewhat lossily) the knowledge that particular TIDs reported by an index need to have their quals rechecked when the heap is visited. This facility is not really used yet; we'll need to extend the forced-recheck feature to plain indexscans before it's useful, and that hasn't been coded yet. The intent is to use it to clean up 8.3's horrid @@@ kluge for text search with weighted queries. There might be other uses in future, but that one alone is sufficient reason. Heikki Linnakangas, with some adjustments by me.
-
- 30 10月, 2007 1 次提交
-
-
由 Tom Lane 提交于
per suggestion from Rene Gollent.
-
- 21 9月, 2007 1 次提交
-
-
由 Tom Lane 提交于
columns, and the new version can be stored on the same heap page, we no longer generate extra index entries for the new version. Instead, index searches follow the HOT-chain links to ensure they find the correct tuple version. In addition, this patch introduces the ability to "prune" dead tuples on a per-page basis, without having to do a complete VACUUM pass to recover space. VACUUM is still needed to clean up dead index entries, however. Pavan Deolasee, with help from a bunch of other people.
-
- 04 6月, 2007 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 07 4月, 2007 1 次提交
-
-
由 Tom Lane 提交于
Teodor Sigaev, with some kibitzing from Tom Lane.
-
- 09 1月, 2007 1 次提交
-
-
由 Tom Lane 提交于
per-column options for btree indexes. The planner's support for this is still pretty rudimentary; it does not yet know how to plan mergejoins with nondefault ordering options. The documentation is pretty rudimentary, too. I'll work on improving that stuff later. Note incompatible change from prior behavior: ORDER BY ... USING will now be rejected if the operator is not a less-than or greater-than member of some btree opclass. This prevents less-than-sane behavior if an operator that doesn't actually define a proper sort ordering is selected.
-
- 10 9月, 2006 1 次提交
-
-
由 Tom Lane 提交于
agreed these symbols are less easily confused. I made new pg_operator entries (with new OIDs) for the old names, so as to provide backward compatibility while making it pretty easy to remove the old names in some future release cycle. This commit only touches the core datatypes, contrib will be fixed separately.
-
- 25 8月, 2006 1 次提交
-
-
由 Tom Lane 提交于
blocking concurrent writes to the table. Greg Stark, with a little help from Tom Lane.
-
- 12 7月, 2006 1 次提交
-
-
由 Teodor Sigaev 提交于
-
- 02 5月, 2006 1 次提交
-
-
由 Teodor Sigaev 提交于
text[], int4[], Tsearch2 support for GIN.
-
- 08 11月, 2005 1 次提交
-
-
由 Tom Lane 提交于
-
- 02 7月, 2005 2 次提交
-
-
由 Tom Lane 提交于
Per buildfarm results.
-
由 Tom Lane 提交于
basic regression tests for GiST to the standard regression tests. I took the opportunity to add an rtree-equivalent gist opclass for circles; the contrib version only covered boxes and polygons, but indexing circles is very handy for distance searches.
-
- 12 4月, 2005 1 次提交
-
-
由 Tom Lane 提交于
into indexscans on matching indexes. For the moment, it only handles int4 and text datatypes; next step is to add a column to pg_aggregate so that all MIN/MAX aggregates can be handled. Per my recent proposal.
-
- 22 11月, 2003 1 次提交
-
-
由 Tom Lane 提交于
large objects. Dump all these in pg_dump; also add code to pg_dump user-defined conversions. Make psql's large object code rely on the backend for inserting/deleting LOB comments, instead of trying to hack pg_description directly. Documentation and regression tests added. Christopher Kings-Lynne, code reviewed by Tom
-
- 13 11月, 2003 1 次提交
-
-
由 Tom Lane 提交于
pghackers proposal of 8-Nov. All the existing cross-type comparison operators (int2/int4/int8 and float4/float8) have appropriate support. The original proposal of storing the right-hand-side datatype as part of the primary key for pg_amop and pg_amproc got modified a bit in the event; it is easier to store zero as the 'default' case and only store a nonzero when the operator is actually cross-type. Along the way, remove the long-since-defunct bigbox_ops operator class.
-
- 25 9月, 2003 1 次提交
-
-
由 Peter Eisentraut 提交于
terms, add some clarifications, fix some untranslatable attempts at dynamic message building.
-
- 22 7月, 2003 1 次提交
-
-
由 Tom Lane 提交于
-
- 29 5月, 2003 2 次提交
-
-
由 Tom Lane 提交于
area...
-
由 Tom Lane 提交于
of an index can now be a computed expression instead of a simple variable. Restrictions on expressions are the same as for predicates (only immutable functions, no sub-selects). This fixes problems recently introduced with inlining SQL functions, because the inlining transformation is applied to both expression trees so the planner can still match them up. Along the way, improve efficiency of handling index predicates (both predicates and index expressions are now cached by the relcache) and fix 7.3 oversight that didn't record dependencies of predicate expressions.
-
- 28 8月, 2001 1 次提交
-
-
由 Tom Lane 提交于
tests.
-
- 16 7月, 2001 1 次提交
-
-
由 Tom Lane 提交于
Note: I didn't force an initdb, figuring that one today was enough. However, there is a new function in pg_proc.h, and pg_dump won't be able to dump partial indexes until you add that function.
-
- 17 2月, 2000 1 次提交
-
-
由 Tom Lane 提交于
selectivity functions and make the r-tree operators use them. The estimation functions themselves are just stubs, unfortunately, but perhaps someday someone will make them compute realistic estimates. Change pg_am so that the optimizer can reliably tell the difference between ordered and unordered indexes --- before it would think that an r-tree index can be scanned in '<<' order, which is not right AFAIK. Repair broken negator links for network_sup and related ops. Initdb forced. This might be my last initdb force for 7.0 ... hope so anyway ...
-
- 06 1月, 2000 1 次提交
-
-
由 Thomas G. Lockhart 提交于
-
- 26 4月, 1998 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 08 4月, 1998 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 31 3月, 1998 1 次提交
-
-
由 Bruce Momjian 提交于
1. Remove the char2, char4, char8 and char16 types from postgresql 2. Change references of char16 to name in the regression tests. 3. Rename the char16.sql regression test to name.sql. 4. Modify the regression test scripts and outputs to match up. Might require new regression.{SYSTEM} files... Darren King
-
- 06 4月, 1997 1 次提交
-
-
由 Marc G. Fournier 提交于
-