- 29 5月, 2003 2 次提交
-
-
由 Tom Lane 提交于
of order; the 'server log' output is actually client output in these scenarios and we ought to treat elevels the same way as in the client case. This allows initdb to not send backend stderr to /dev/null anymore, which makes it much more likely that people will notice problems during initdb.
-
由 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 5月, 2003 6 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Peter Eisentraut 提交于
-
由 Bruce Momjian 提交于
users can't turn it off.
-
由 Bruce Momjian 提交于
docs that CLIENT/LOG_MIN_MESSAGES now controls debug_* output location. Doc changes included.
-
由 Bruce Momjian 提交于
-
- 27 5月, 2003 8 次提交
-
-
由 Michael Meskes 提交于
-
由 Michael Meskes 提交于
-
由 Tom Lane 提交于
sanely with running out of memory for a query result.
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
< * Add now("transaction|statement|clock") functionality > * Add transaction_timestamp(), statement_timestamp(), clock_timestamp() functionality
-
由 Tom Lane 提交于
advertised in RowDescription message. Depending on the physical tuple's column count is not really correct, since according to heap_getattr() conventions the tuple may be short some columns, which will automatically get read as nulls. Problem has been latent since forever, but was only exposed by recent change to skip a projection step in SELECT * FROM...
-
由 Bruce Momjian 提交于
modify passwords, per user confusion report. Also clean up wording that command line utils need database access.
-
- 26 5月, 2003 3 次提交
-
-
由 Bruce Momjian 提交于
> * Allow UPDATE to use SET col = DEFAULT
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
blanks, in hopes of reducing the surprise factor for newbies. Remove redundant operators for VARCHAR (it depends wholly on TEXT operations now). Clean up resolution of ambiguous operators/functions to avoid surprising choices for domains: domains are treated as equivalent to their base types and binary-coercibility is no longer considered a preference item when choosing among multiple operators/functions. IsBinaryCoercible now correctly reflects the notion that you need *only* relabel the type to get from type A to type B: that is, a domain is binary-coercible to its base type, but not vice versa. Various marginal cleanup, including merging the essentially duplicate resolution code in parse_func.c and parse_oper.c. Improve opr_sanity regression test to understand about binary compatibility (using pg_cast), and fix a couple of small errors in the catalogs revealed thereby. Restructure "special operator" handling to fetch operators via index opclasses rather than hardwiring assumptions about names (cleans up the pattern_ops stuff a little).
-
- 25 5月, 2003 6 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
< * Update clients to use data types, typmod, schema.table.column names of < result sets using new query protocol 453a452,453 > o Update clients to use data types, typmod, schema.table.column names of > result sets using new query protocol
-
由 Bruce Momjian 提交于
< * Allow clients to get data types, typmod, schema.table.column names from < result sets, either via the backend protocol or a new QUERYINFO command to: > * Update clients to use data types, typmod, schema.table.column names of > result sets using new query protocol
-
由 Bruce Momjian 提交于
> * Allow clients to get data types, typmod, schema.table.column names from > result sets, either via the backend protocol or a new QUERYINFO command
-
由 Bruce Momjian 提交于
> * Allow backend to output result sets in XML > * Add XML capability to pg_dump and COPY, when backend XML capability
-
- 24 5月, 2003 7 次提交
-
-
由 Bruce Momjian 提交于
> * Find a way to reduce rotational delay when repeatedly writing > last WAL page
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
* With disabled triggers, allow pg_dump to use ALTER TABLE ADD FOREIGN KEY Add to trigger TODO.detail.
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
single-byte encodings, and a direct C implementation of the single-argument forms (where spaces are always what gets trimmed). This is in preparation for using rtrim1() as the bpchar-to-text cast operator, but is a useful performance improvement even if we decide not to do that.
-
由 Michael Meskes 提交于
-
由 Bruce Momjian 提交于
-
- 23 5月, 2003 8 次提交
-
-
由 Michael Meskes 提交于
-
由 Michael Meskes 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
-