- 15 12月, 2005 2 次提交
-
-
由 Tom Lane 提交于
messages, when client attempts to execute these outside a transaction (start one) or in a failed transaction (reject message, except for COMMIT/ROLLBACK statements which we can handle). Per report from Francisco Figueiredo Jr.
-
由 Tom Lane 提交于
example from Jim Dew. Add some simple regression tests, since this is an area we seem to break regularly :-(
-
- 12 12月, 2005 5 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
< * %Allow pooled connections to list all prepared queries > * %Allow pooled connections to list all prepared statements 28c28 < the queries prepared in the current session. > the statements prepared in the current session. 143c143 < o Allow a warm standby system to also allow read-only queries > o Allow a warm standby system to also allow read-only statements 404c404 < * Add GUC to issue notice about queries that use unjoined tables > * Add GUC to issue notice about statements that use unjoined tables 490c490 < Another idea would be to allow actual SELECT queries in a COPY. > Another idea would be to allow actual SELECT statements in a COPY. 554c554 < o Allow function argument names to be queries from PL/PgSQL > o Allow function argument names to be statements from PL/PgSQL 591c591 < o Improve psql's handling of multi-line queries > o Improve psql's handling of multi-line statements < Currently, while \e saves a single query as one entry, interactive < queries are saved one line at a time. Ideally all queries > Currently, while \e saves a single statement as one entry, interactive > statements are saved one line at a time. Ideally all statements 665c665 < o Allow query results to be automatically batched to the client > o Allow statement results to be automatically batched to the client 667c667 < Currently, all query results are transfered to the libpq > Currently, all statement results are transfered to the libpq 672c672 < One complexity is that a query like SELECT 1/col could error > One complexity is that a statement like SELECT 1/col could error 739c739 < * Allow queries across databases or servers with transaction > * Allow statements across databases or servers with transaction < inheritance, allow it to work for UPDATE and DELETE queries, and allow < it to be used for all queries with little performance impact > inheritance, allow it to work for UPDATE and DELETE statements, and allow > it to be used for all statements with little performance impact 876c876 < * Consider automatic caching of queries at various levels: > * Consider automatic caching of statements at various levels: 947c947 < a single session using multiple threads to execute a query faster. > a single session using multiple threads to execute a statement faster. 1025c1025 < * Log queries where the optimizer row estimates were dramatically > * Log statements where the optimizer row estimates were dramatically 1146c1146 < of result sets using new query protocol > of result sets using new statement protocol
-
由 Teodor Sigaev 提交于
- tsvector_(in|out) - tsquery_(in|out) - to_tsvector - to_tsquery, plainto_tsquery - 'simple' dictionary
-
由 Tom Lane 提交于
reduce contention for the former single LockMgrLock. Per my recent proposal. I set it up for 16 partitions, but on a pgbench test this gives only a marginal further improvement over 4 partitions --- we need to test more scenarios to choose the number of partitions.
-
- 11 12月, 2005 3 次提交
-
-
由 Neil Conway 提交于
Patch from Pavel Stehule, minor fixups by myself.
-
由 Bruce Momjian 提交于
< * Add GUC variable to run a command on database panic or < smart/fast/immediate shutdown
-
由 Tom Lane 提交于
that simplify_boolean_equality() may leave behind. This is only relevant if the user writes something a bit silly, like CASE x=y WHEN TRUE THEN. Per example from Michael Fuhr; may or may not explain bug #2106.
-
- 10 12月, 2005 9 次提交
-
-
由 Tom Lane 提交于
Sync HEAD and 8.1 branches of pgbench.
-
由 Bruce Momjian 提交于
< * Allow installing to directories containing spaces > * -Allow installing to directories containing spaces
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
Also minor improvements to 8.1.1 release notes.
-
由 Bruce Momjian 提交于
integrity actions. Stephan Szabo
-
由 Bruce Momjian 提交于
has been that way for a long time.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
introduced a copy-and-pasteo while trying to simplify the code.
-
由 Bruce Momjian 提交于
* -Have initdb set the input DateStyle (MDY or DMY) based on locale
-
- 09 12月, 2005 21 次提交
-
-
由 Peter Eisentraut 提交于
datestyle parameter of the new cluster accordingly.
-
由 Bruce Momjian 提交于
However, Another problem newly occurred. This solves the problem of snprintf and vsnprintf. Patch to HEAD and 8.1.X. Hiroshi Saito
-
由 Bruce Momjian 提交于
Win32 library files.
-
由 Tom Lane 提交于
the data defining the semantics of a lock method (ie, conflict resolution table and ancillary data, which is all constant) and the hash tables storing the current state. The only thing we give up by this is the ability to use separate hashtables for different lock methods, but there is no need for that anyway. Put some extra fields into the LockMethod definition structs to clean up some other uglinesses, like hard-wired tests for DEFAULT_LOCKMETHOD and USER_LOCKMETHOD. This commit doesn't do anything about the performance issues we were discussing, but it clears away some of the underbrush that's in the way of fixing that.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
> * Teodor is Teodor Sigaev <teodor@sigaev.ru>
-
由 Bruce Momjian 提交于
< * Claudio is Claudio Natoli <claudio.natoli@memetrics.com> 1166d1164 < * Hiroshi is Hiroshi Inoue <Inoue@tpf.co.jp>
-
由 Bruce Momjian 提交于
postgres problems due to readline. The attached patch replaces that section of it with better ways of handling the problem. Seneca Cunningham
-
由 Bruce Momjian 提交于
DROP CONSTRAINT This form drops constraints on a table. Currently, constraints on tables are not required to have unique names, so there may be more than one constraint matching the specified name. All matching constraints will be dropped. To my knowledge, it is no longer possible to create constraints with the same name for the same relation. When you create a constraint and specify the same name explictly, an error is raised. Implicit constraint creation won't choose an existing name either and up to now you could not rename a constraint. Renaming works with the patch I sent in a few hours ago but this patch as well won't allow constraints with identical names on the same relation. The attached patch thus removes the note in the docs. Joachim Wieland
-
由 Bruce Momjian 提交于
> Now, the arguments of the drop function can be tab completed. for example > > drop function strpos ( > <press tab> > drop FUNCTION strpos (text, text) > > or: > > wsdb=# drop FUNCTION length ( > bit) bytea) character) lseg) path) text) > <press c> > wsdb# DROP FUNCTION length ( character) > > I think that this patch should be rather useful. At it least I hate > always to type all the arguments of the dropped functions. > > 2) Also some fixes applied for the > CREATE INDEX syntax > > now the parenthesises are inserted by tab pressing. > suppose I have the table q3c: Sergey E. Koposov
-
由 Peter Eisentraut 提交于
-
由 Bruce Momjian 提交于
-
由 Peter Eisentraut 提交于
-
由 Bruce Momjian 提交于
Also, better mark section headings. kdio@uenf.br
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
error. This probably explains bug #2099 and could also account for mysterious VACUUM hangups.
-
由 Bruce Momjian 提交于
support for the dbf2pg contrib module. The submitter created a patch which replaces the silent ignoring of -F (when iconv support is disabled) with a meaningful warning. Martin Pitt
-