- 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 提交于
-