- 07 4月, 2007 1 次提交
-
-
由 Tom Lane 提交于
Teodor Sigaev, with some kibitzing from Tom Lane.
-
- 04 4月, 2007 1 次提交
-
-
由 Bruce Momjian 提交于
CONCURRENTLY. Gregory Stark
-
- 01 2月, 2007 1 次提交
-
-
由 Bruce Momjian 提交于
Standard English uses "may", "can", and "might" in different ways: may - permission, "You may borrow my rake." can - ability, "I can lift that log." might - possibility, "It might rain today." Unfortunately, in conversational English, their use is often mixed, as in, "You may use this variable to do X", when in fact, "can" is a better choice. Similarly, "It may crash" is better stated, "It might crash".
-
- 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.
-
- 16 9月, 2006 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 14 9月, 2006 1 次提交
-
-
由 Tom Lane 提交于
CONCURRENTLY. Greg Stark, some further tweaks by me.
-
- 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 次提交
-
-
由 Tom Lane 提交于
it can handle small fillfactors for ordinary-sized index entries without failing on large ones; fix nbtinsert.c to distinguish leaf and nonleaf pages; change the minimum fillfactor to 10% for all index types.
-
- 05 7月, 2006 1 次提交
-
-
由 Tom Lane 提交于
-
- 02 7月, 2006 1 次提交
-
-
由 Bruce Momjian 提交于
ITAGAKI Takahiro
-
- 08 11月, 2005 1 次提交
-
-
由 Tom Lane 提交于
-
- 04 1月, 2005 1 次提交
-
-
由 Tom Lane 提交于
-
- 06 11月, 2004 1 次提交
-
-
由 Tom Lane 提交于
clause implicitly whenever one is not given explicitly. Remove concept of a schema having an associated tablespace, and simplify the rules for selecting a default tablespace for a table or index. It's now just (a) explicit TABLESPACE clause; (b) default_tablespace if that's not an empty string; (c) database's default. This will allow pg_dump to use SET commands instead of tablespace clauses to determine object locations (but I didn't actually make it do so). All per recent discussions.
-
- 12 7月, 2004 1 次提交
-
-
由 Bruce Momjian 提交于
some other examples for CREATE DATABASE. Gavin Sherry
-
- 18 6月, 2004 1 次提交
-
-
由 Tom Lane 提交于
There are various things left to do: contrib dbsize and oid2name modules need work, and so does the documentation. Also someone should think about COMMENT ON TABLESPACE and maybe RENAME TABLESPACE. Also initlocation is dead, it just doesn't know it yet. Gavin Sherry and Tom Lane.
-
- 20 4月, 2004 3 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
> >> have to accept a full table scan when locating records. > > > > It indexes them, but "is null" is not an indexable operator, so you > > can't directly solve the above with a 3-column index. What you can do > > instead is use a partial index, for instance > > > > create index i on CUSTOMER.WCCustOrderStatusLog (WCOrderStatusID) > > where Acknowledged is null and Processing is null; > > That's a very nifty trick and exactly the sort of answer I was after! Add CREATE INDEX doc mention of using partial indexes for IS NULL indexing; idea from Tom.
-
- 30 11月, 2003 1 次提交
-
-
由 PostgreSQL Daemon 提交于
$Header: -> $PostgreSQL Changes ...
-
- 22 9月, 2003 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 12 9月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
makes a few more small improvements to runtime.sgml, and makes some SGML conventions more consistent. Neil Conway
-
- 10 9月, 2003 1 次提交
-
-
由 Tom Lane 提交于
discussion. (Still have some work to do editing the remainder.)
-
- 01 9月, 2003 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 29 5月, 2003 1 次提交
-
-
由 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.
-
- 22 4月, 2003 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 22 9月, 2002 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 14 8月, 2002 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 31 7月, 2002 1 次提交
-
-
由 Tom Lane 提交于
OPERATOR CLASS commands. Further tweaking of documentation for same.
-
- 22 6月, 2002 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 21 6月, 2002 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 18 5月, 2002 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 23 4月, 2002 1 次提交
-
-
由 Tom Lane 提交于
-
- 22 4月, 2002 1 次提交
-
-
由 Thomas G. Lockhart 提交于
capabilities of specifying time zones as intervals per SQL9x. Put refentrytitle contents on the same line as the tag. Otherwise, leading whitespace is propagated into the product, which (at least) messes up the ToC layout. Remove (some) docinfo tags containing dates. Best to omit if the dates are not accurate; maybe use CVS dates instead or leave them out.
-
- 12 4月, 2002 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 23 3月, 2002 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 21 1月, 2002 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 08 12月, 2001 1 次提交
-
-
由 Thomas G. Lockhart 提交于
between Postgres and PostgreSQL.
-
- 14 9月, 2001 1 次提交
-
-
由 Tatsuo Ishii 提交于
-
- 03 9月, 2001 1 次提交
-
-
由 Peter Eisentraut 提交于
-