aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* Defend against crash while processing Describe Statement or Describe PortalTom Lane2005-12-14
| | | | | | 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.
* Fix problem with whole-row Vars referencing sub-select outputs, perTom Lane2005-12-14
| | | | | example from Jim Dew. Add some simple regression tests, since this is an area we seem to break regularly :-(
* Use a proper enum for tri-valued variables.Bruce Momjian2005-12-12
|
* Document tri-valued variables in createdb, +1, -1, 0.Bruce Momjian2005-12-12
|
* Update wording, query -> statement:Bruce Momjian2005-12-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | < * %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
* Improve support of multibyte encoding:Teodor Sigaev2005-12-12
| | | | | | | | - tsvector_(in|out) - tsquery_(in|out) - to_tsvector - to_tsquery, plainto_tsquery - 'simple' dictionary
* Divide the lock manager's shared state into 'partitions', so as toTom Lane2005-12-11
| | | | | | | 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.
* Implement IS NOT DISTINCT FROM, update the regression tests and docs.Neil Conway2005-12-11
| | | | Patch from Pavel Stehule, minor fixups by myself.
* Remove item:Bruce Momjian2005-12-11
| | | | | < * Add GUC variable to run a command on database panic or < smart/fast/immediate shutdown
* Teach deparsing of CASE expressions to cope with the simplified formsTom Lane2005-12-10
| | | | | | 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.
* Remove incorrect increment of lineno, per David Fetter.Tom Lane2005-12-10
| | | | Sync HEAD and 8.1 branches of pgbench.
* Done:Bruce Momjian2005-12-09
| | | | | < * Allow installing to directories containing spaces > * -Allow installing to directories containing spaces
* Allow installation into directories containing spaces in the name.Peter Eisentraut2005-12-09
|
* Add release notes for back branches (7.3 and up).Tom Lane2005-12-09
| | | | Also minor improvements to 8.1.1 release notes.
* Add documentation about the behavior of BEFORE triggers and referentialBruce Momjian2005-12-09
| | | | | | integrity actions. Stephan Szabo
* Remove mention that history is _now_ automatically saved on exit. ItBruce Momjian2005-12-09
| | | | has been that way for a long time.
* Fix broken markup.Tom Lane2005-12-09
|
* Fix core dump in error path of plpgsql_parse_tripwordtype. SomebodyTom Lane2005-12-09
| | | | introduced a copy-and-pasteo while trying to simplify the code.
* Completed:Bruce Momjian2005-12-09
| | | | * -Have initdb set the input DateStyle (MDY or DMY) based on locale
* Let initdb detect the date order of the lc_time locale and initialize thePeter Eisentraut2005-12-09
| | | | datestyle parameter of the new cluster accordingly.
* I reconfirmed MS-VC6. Thank you for wonderful correspondence.Bruce Momjian2005-12-09
| | | | | | | | | However, Another problem newly occurred. This solves the problem of snprintf and vsnprintf. Patch to HEAD and 8.1.X. Hiroshi Saito
* Stamp libraries for 8.2 by updating minor library version numbers andBruce Momjian2005-12-09
| | | | Win32 library files.
* Simplify lock manager data structures by making a clear separation betweenTom Lane2005-12-09
| | | | | | | | | | | | 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.
* Release note wording improvements.Bruce Momjian2005-12-08
|
* Wrap UTF-8 paragraph.Bruce Momjian2005-12-08
|
* Update wording of translation bug item.Bruce Momjian2005-12-08
|
* Update for 8.1.1.Bruce Momjian2005-12-08
|
* Update release notes for 8.1.1.Bruce Momjian2005-12-08
|
* Add Teodor:Bruce Momjian2005-12-08
| | | | > * Teodor is Teodor Sigaev <teodor@sigaev.ru>
* Remove a few people:Bruce Momjian2005-12-08
| | | | | | < * Claudio is Claudio Natoli <claudio.natoli@memetrics.com> 1166d1164 < * Hiroshi is Hiroshi Inoue <Inoue@tpf.co.jp>
* FAQ_AIX in 8.1.0 contains outdated information about how to deal withBruce Momjian2005-12-08
| | | | | | | postgres problems due to readline. The attached patch replaces that section of it with better ways of handling the problem. Seneca Cunningham
* there's a paragraph in the ALTER TABLE reference page that reads:Bruce Momjian2005-12-08
| | | | | | | | | | | | | | | | | | | | | 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
* > 1) I'm proposing a patch to do the DROP FUNCTION argument tab completion.Bruce Momjian2005-12-08
| | | | | | | | | | | | | | | | | | | | | | | | | | > 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
* Put [] around default value for port number.Peter Eisentraut2005-12-08
|
* Remove empty heading row in error table.Bruce Momjian2005-12-08
|
* Add missing translation markerPeter Eisentraut2005-12-08
|
* Add "Constant" column to error code table.Bruce Momjian2005-12-08
| | | | | | Also, better mark section headings. kdio@uenf.br
* Documentation fix: s/event_object_name/event_object_table/gPeter Eisentraut2005-12-08
|
* Fix bgwriter's failure to release buffer pins and open files after anTom Lane2005-12-08
| | | | | error. This probably explains bug #2099 and could also account for mysterious VACUUM hangups.
* I recently received the Debian bug report below about missing iconvBruce Momjian2005-12-08
| | | | | | | | | 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
* Add documentation about the inability of plpsql to use parameter namesBruce Momjian2005-12-08
| | | | that are the same as column names used in the function.
* Disble some Win32-specific code in win32-client-only builds:Bruce Momjian2005-12-08
| | | | | | | | | | | | | | | | | | | | | | | | | | I have the problem, when building by MS-VC6. An error occurs in the 8.1.0 present source codes. nmake -f win32.mak ..\..\port\getaddrinfo.c(244) : error C2065: 'WSA_NOT_ENOUGH_MEMORY' ..\..\port\getaddrinfo.c(342) : error C2065: 'WSATYPE_NOT_FOUND' This is used by winsock2.h. However, Construction of a windows base is winsock.h. Then, Since MinGW has special environment, this is right. but, it is not found in VC6. Furthermore, in getaddrinfo.c, IPV6-API is used by LoadLibraryA("ws2_32"); Referring to of dll the external memory generates this violation by VC6 specification. I considered whether the whole should have been converted into winsock2. However, Now, DLL of MinGW creation operates wonderfully as it is. That's right, it has pliability by replacement of simple DLL. Then, I propose the system using winsock(non IPV6) in construction of VC6. Hiroshi Saito
* Fix thinko in comment.Tom Lane2005-12-08
|
* Improve tag recognizingTeodor Sigaev2005-12-08
|
* Push the responsibility for handling ignore_killed_tuples down intoTom Lane2005-12-07
| | | | | | _bt_checkkeys(), instead of checking it in the top-level nbtree.c routines as formerly. This saves a little bit of loop overhead, but more importantly it lets us skip performing the index key comparisons for dead tuples.
* A couple of tiny performance hacks in _bt_step(). Remove PageIsEmptyTom Lane2005-12-07
| | | | | | | | | checks, which were once needed because PageGetMaxOffsetNumber would fail on empty pages, but are now just redundant. Also, don't set up local variables that aren't needed in the fast path --- most of the time, we only need to advance offnum and not step across a page boundary. Motivated by noticing _bt_step at the top of OProfile profile for a pgbench run.
* Update:Bruce Momjian2005-12-07
| | | | | | < at initdb time or optionally later. > at initdb time or optionally later. Consider O_SYNC when > O_DIRECT exists.
* Fix incorrect SPI example, per Yoshihisa Nakano.Tom Lane2005-12-07
|
* Fix a couple of lingering references to POSTQUEL query syntax, per Simon.Tom Lane2005-12-07
|
* Spell "explicitly" correctly, per Simon.Tom Lane2005-12-07
|