summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Insert ORDER BY into a few regression test queries that now have unstableTom Lane2007-06-096-92/+98
| | | | | | results due to syncscan patch, when shared_buffers is small enough. Per buildfarm reports and some local testing with shared_buffers set to the lowest value considered by initdb.
* Allow numeric_fac() to be interrupted, since it can take quite a while forTom Lane2007-06-091-1/+10
| | | | | | large inputs. Also cause it to error out immediately if the result will overflow, instead of grinding through a lot of calculation first. Per gripe from Jim Nasby.
* Disallow the cost balancing code from resulting in a zero cost limit, whichAlvaro Herrera2007-06-081-2/+6
| | | | | | | | causes a division-by-zero error in the vacuum code. This can happen when there are more workers than cost limit units. Per report from Galy Lee in <200705310914.l4V9E6JA094603@wwwmaster.postgresql.org>.
* Avoid passing zero as a value for vacuum_cost_limit, because it's not a validAlvaro Herrera2007-06-082-7/+13
| | | | | | | | | | value for the vacuum code. Instead, make zero signify getting the value from a higher level configuration facility, just like -1 in the original coding. We still document that -1 is the value that disables the feature, to avoid confusing the user unnecessarily. Reported by Galy Lee in <200705310914.l4V9E6JA094603@wwwmaster.postgresql.org>; per subsequent discussion.
* Add note that LIMIT without ORDER BY can produce outright nondeterministicTom Lane2007-06-081-1/+9
| | | | results. Necessary due to introduction of syncscan patch.
* Done:Bruce Momjian2007-06-082-25/+4
| | | | | | | | | | | | | | | | < * Allow sequential scans to take advantage of other concurrent > * -Allow sequential scans to take advantage of other concurrent < < One possible implementation is to start sequential scans from the lowest < numbered buffer in the shared cache, and when reaching the end wrap < around to the beginning, rather than always starting sequential scans < at the start of the table. < < http://archives.postgresql.org/pgsql-patches/2006-12/msg00076.php < http://archives.postgresql.org/pgsql-hackers/2006-12/msg00408.php < http://archives.postgresql.org/pgsql-hackers/2006-12/msg00784.php < http://archives.postgresql.org/pgsql-hackers/2007-03/msg00415.php <
* Arrange for large sequential scans to synchronize with each other, so thatTom Lane2007-06-0810-31/+485
| | | | | | | when multiple backends are scanning the same relation concurrently, each page is (ideally) read only once. Jeff Davis, with review by Heikki and Tom.
* Redefine IsTransactionState() to only return true for TRANS_INPROGRESS state,Tom Lane2007-06-073-39/+23
| | | | | | | | | which is the only state in which it's safe to initiate database queries. It turns out that all but two of the callers thought that's what it meant; and the other two were using it as a proxy for "will GetTopTransactionId() return a nonzero XID"? Since it was in fact an unreliable guide to that, make those two just invoke GetTopTransactionId() always, then deal with a zero result if they get one.
* Rework temp_tablespaces patch so that temp tablespaces are assigned separatelyTom Lane2007-06-0714-168/+283
| | | | | | | | | for each temp file, rather than once per sort or hashjoin; this allows spreading the data of a large sort or join across multiple tablespaces. (I remain dubious that this will make any difference in practice, but certain people insisted.) Arrange to cache the results of parsing the GUC variable instead of recomputing from scratch on every demand, and push usage of the cache down to the bottommost fd.c level.
* Avoid losing track of data for shared tables in pgstats. Report by MichaelAlvaro Herrera2007-06-071-2/+4
| | | | Fuhr, patch from Tom Lane after a messier suggestion by me.
* Fix array_dims() example to be consistent with the data previously shown.Tom Lane2007-06-071-2/+2
| | | | Christian Rossow
* The functions bt_metap, bt_page_stats and bt_page_items had movedMagnus Hagander2007-06-071-48/+1
| | | | | | | from contrib/pgstattuple to pageinspect. We've already fixed English documentation, but Japanese version does not catch up. ITAGAKI Takahiro
* Fix up text concatenation so that it accepts all the reasonable cases thatTom Lane2007-06-0622-109/+301
| | | | | | | | were accepted by prior Postgres releases. This takes care of the loose end left by the preceding patch to downgrade implicit casts-to-text. To avoid breaking desirable behavior for array concatenation, introduce a new polymorphic pseudo-type "anynonarray" --- the added concatenation operators are actually text || anynonarray and anynonarray || text.
* Minor editorialization: don't flush plan cache without need.Tom Lane2007-06-051-22/+17
|
* Downgrade implicit casts to text to be assignment-only, except for the onesTom Lane2007-06-0560-1610/+848
| | | | | | | | | | | | | | | | | | | | | | | | | from the other string-category types; this eliminates a lot of surprising interpretations that the parser could formerly make when there was no directly applicable operator. Create a general mechanism that supports casts to and from the standard string types (text,varchar,bpchar) for *every* datatype, by invoking the datatype's I/O functions. These new casts are assignment-only in the to-string direction, explicit-only in the other, and therefore should create no surprising behavior. Remove a bunch of thereby-obsoleted datatype-specific casting functions. The "general mechanism" is a new expression node type CoerceViaIO that can actually convert between *any* two datatypes if their external text representations are compatible. This is more general than needed for the immediate feature, but might be useful in plpgsql or other places in future. This commit does nothing about the issue that applying the concatenation operator || to non-text types will now fail, often with strange error messages due to misinterpreting the operator as array concatenation. Since it often (not always) worked before, we should either make it succeed or at least give a more user-friendly error; but details are still under debate. Peter Eisentraut and Tom Lane
* The session_replication_role actually can be changed at will duringJan Wieck2007-06-053-19/+12
| | | | | | | | a session regardless of the existence of cached plans. The plancache only needs to be invalidated so that rules affected by the new setting will be reflected in the new query plans. Jan
* Move call of MarkBufferDirty() before XLogInsert() as required.Teodor Sigaev2007-06-053-18/+25
| | | | | Many thanks to Heikki Linnakangas <heikki@enterprisedb.com> for his sharp eyes.
* Remove ill-conceived CRLF translation for Windows in syslogger.Andrew Dunstan2007-06-041-47/+3
|
* Tidy overly long configure help lines.Andrew Dunstan2007-06-042-5/+5
|
* Fix bundle bugs of GIN:Teodor Sigaev2007-06-045-54/+146
| | | | | | | | | | | | | | | | | - Fix possible deadlock between UPDATE and VACUUM queries. Bug never was observed in 8.2, but it still exist there. HEAD is more sensitive to bug after recent "ring" of buffer improvements. - Fix WAL creation: if parent page is stored as is after split then incomplete split isn't removed during replay. This happens rather rare, only on large tables with a lot of updates/inserts. - Fix WAL replay: there was wrong test of XLR_BKP_BLOCK_* for left page after deletion of page. That causes wrong rightlink field: it pointed to deleted page. - add checking of match of clearing incomplete split - cleanup incomplete split list after proceeding All of this chages doesn't change on-disk storage, so backpatch... But second point may be an issue for replaying logs from previous version.
* On win32, retry reading when WSARecv returns WSAEWOULDBLOCK. There seemMagnus Hagander2007-06-041-10/+30
| | | | | | | to be cases when at least Windows 2000 can do this even though select just indicated that the socket is readable. Per report and analysis from Cyril VELTER.
* On win32, don't use SO_REUSEADDR for TCP sockets.Magnus Hagander2007-06-041-1/+12
| | | | Per failure on buildfarm member baiji and subsequent discussion.
* Remove gratuitous response messages from utility programs.Peter Eisentraut2007-06-0414-161/+69
| | | | | | | | | | | | | | (Possibly release notes material, lest users be confused.) The --quiet option is now obsolete and without effect in createdb, createuser, dropdb, dropuser; kept for compatibility but marked for removal in 8.4. Progress messages when acting on all databases now go to stdout instead of stderr, since they are not in fact errors. Ordered options in reindexdb reference page alphabetically, like in other programs' pages.
* Update expected files for textual changesPeter Eisentraut2007-06-042-4/+4
|
* Clarify some error messages about duplicate things.Peter Eisentraut2007-06-0313-32/+32
|
* Remove description for:Bruce Momjian2007-06-032-9/+2
| | | | | | | | | o -Add a GUC variable to control the tablespace for temporary objects and sort files < < It could start with a random tablespace from a supplied list and < cycle through the list. <
* Create a GUC parameter temp_tablespaces that allows selection of theTom Lane2007-06-0326-173/+494
| | | | | | | | | | tablespace(s) in which to store temp tables and temporary files. This is a list to allow spreading the load across multiple tablespaces (a random list element is chosen each time a temp object is to be created). Temp files are not stored in per-database pgsql_tmp/ directories anymore, but per-tablespace directories. Jaime Casanova and Albert Cervera, with review by Bernd Helmle and Tom Lane.
* Minimal message corrections found by spell checker.Peter Eisentraut2007-06-023-7/+7
|
* Fix erroneous error reporting for overlength input in text_date(),Tom Lane2007-06-021-5/+8
| | | | text_time(), and text_timetz(). 7.4-vintage bug found by Greg Stark.
* Re-add TODO and clarify it is for the kernel cache:Bruce Momjian2007-06-022-3/+18
| | | | | | | < * Allow free-behind capability for large sequential scans, perhaps using < posix_fadvise() > * Allow free-behind capability for large sequential scans to avoid > kernel cache spoiling
* TODO item not needed anymore now that the buffer cache isBruce Momjian2007-06-022-18/+3
| | | | | | | | | | | | | scan-resistant: < < * Allow free-behind capability for large sequential scans, perhaps using < posix_fadvise() < < Posix_fadvise() can control both sequential/random file caching and < free-behind behavior, but it is unclear how the setting affects other < backends that also have the file open, and the feature is not supported < on all operating systems.
* Improve efficiency of LIKE/ILIKE code, especially for multi-byte charsets,Andrew Dunstan2007-06-022-439/+183
| | | | | | | | | | | and most especially for UTF8. Remove unnecessary special cases for bytea processing and single-byte charset ILIKE. a ILIKE b is now processed as lower(a) LIKE lower(b) in all cases. The code is now considerably simpler. All comparisons are now performed byte-wise, and the text and pattern are also advanced byte-wise where it is safe to do so - essentially where a wildcard is not being matched. Andrew Dunstan, from an original patch by ITAGAKI Takahiro, with ideas from Tom Lane and Mark Mielke.
* Fix aboriginal bug in BufFileDumpBuffer that would cause it to write theTom Lane2007-06-011-2/+2
| | | | | | | | wrong data when dumping a bufferload that crosses a component-file boundary. This probably has not been seen in the wild because (a) component files are normally 1GB apiece and (b) non-block-aligned buffer usage is relatively rare. But it's fairly easy to reproduce a problem if one reduces RELSEG_SIZE in a test build. Kudos to Kurt Harriman for spotting the bug.
* Allow leading and trailing whitespace in the input to the booleanNeil Conway2007-06-018-22/+110
| | | | | | | type. Also, add explicit casts between boolean and text/varchar. Both of these changes are for conformance with SQL:2003. Update the regression tests, bump the catversion.
* Make CREATE/DROP/RENAME DATABASE wait a little bit to see if other backendsTom Lane2007-06-015-108/+141
| | | | | | | will exit before failing because of conflicting DB usage. Per discussion, this seems a good idea to help mask the fact that backend exit takes nonzero time. Remove a couple of thereby-obsoleted sleeps in contrib and PL regression test sequences.
* Add URL for:Bruce Momjian2007-06-012-3/+4
| | | | | | | o Research self-referential UPDATEs that see inconsistent row versions in read-committed mode < > http://archives.postgresql.org/pgsql-hackers/2007-06/msg00016.php
* Update wording:Bruce Momjian2007-06-012-12/+12
| | | | | | | | o Research self-referential UPDATEs that see inconsistent row versions in read-committed mode http://archives.postgresql.org/pgsql-hackers/2007-05/msg00507.php
* Buy back some of the cycles spent in more-expensive hash functions byTom Lane2007-06-012-30/+30
| | | | | | | selecting power-of-2, rather than prime, numbers of buckets in hash joins. If the hash functions are doing their jobs properly by making all hash bits equally random, this is good enough, and it saves expensive integer division and modulus operations.
* Fix several hash functions that were taking chintzy shortcuts instead ofTom Lane2007-06-015-41/+67
| | | | | | | | | | | | | delivering a well-randomized hash value. I got religion on this after observing that performance of multi-batch hash join degrades terribly if the higher-order bits of hash values aren't random, as indeed was true for say hashes of small integer values. It's now expected and documented that hash functions should use hash_any or some comparable method to ensure that all bits of their output are about equally random. initdb forced because this change invalidates existing hash indexes. For the same reason, this isn't back-patchable; the hash join performance problem will get a band-aid fix in the back branches.
* Wording improvement.Bruce Momjian2007-06-012-4/+4
|
* Update FAQ_DEV URL to output for text format.Bruce Momjian2007-06-012-4/+6
|
* Add URL for code comments to developer's FAQ:Bruce Momjian2007-06-012-4/+5
| | | | http://www.ibm.com/developerworks/linux/library/l-clear-code/?ca=dgr-FClnxw01linuxcodetips
* The shortcut exit that I recently added to ExecInitIndexScan() forTom Lane2007-05-311-7/+7
| | | | | | | | | EXPLAIN-only operation was a little too short; it skipped initializing the node's result tuple type, which may be needed depending on what's above the indexscan node. Call ExecAssignResultTypeFromTL before exiting. (For good luck I moved up the ExecAssignScanProjectionInfo call as well, so that everything except indexscan-specific initialization will still be done.) Per example from Grant Finnemore.
* Change build_index_pathkeys() so that the expressions it builds to representTom Lane2007-05-313-14/+41
| | | | | | | | | | | | | index key columns always have the type expected by the index's associated operators, ie, we add RelabelType nodes when dealing with binary-compatible index opclasses. This is needed to get varchar indexes to play nicely with the new EquivalenceClass machinery, as per recent gripe from Josh Berkus that CVS HEAD was failing to match a varchar index column to a constant restriction in the query. It seems likely that this change will allow removal of a lot of ugly ad-hoc RelabelType-stripping that the planner has traditionally done while matching expressions to other expressions, but I'll worry about that some other day.
* Make some messages more consistentPeter Eisentraut2007-05-3110-26/+26
|
* Replace ReadBuffer to ReadBufferWithStrategy in all vacuum-involved placesTeodor Sigaev2007-05-312-16/+21
| | | | to implement limited-size "ring" of buffers for VACUUM for GIN & GIST
* Downgrade some low-level startup messages to DEBUG1.Peter Eisentraut2007-05-311-6/+6
|
* Fix overly-strict sanity check in BeginInternalSubTransaction that made itTom Lane2007-05-301-7/+8
| | | | | | fail when used in a deferred trigger. Bug goes back to 8.0; no doubt the reason it hadn't been noticed is that we've been discouraging use of user-defined constraint triggers. Per report from Frank van Vugt.
* Update:Bruce Momjian2007-05-302-6/+13
| | | | | | | | | | | < * Consider allowing 64-bit integers to be passed by value on 64-bit < platforms > * Consider allowing 64-bit integers and floats to be passed by value on > 64-bit platforms > > Also change 32-bit floats (float4) to be passed by value at the same > time. >
* Make large sequential scans and VACUUMs work in a limited-size "ring" ofTom Lane2007-05-3024-263/+723
| | | | | | | | | | | | | | | | | | | | | | | buffers, rather than blowing out the whole shared-buffer arena. Aside from avoiding cache spoliation, this fixes the problem that VACUUM formerly tended to cause a WAL flush for every page it modified, because we had it hacked to use only a single buffer. Those flushes will now occur only once per ring-ful. The exact ring size, and the threshold for seqscans to switch into the ring usage pattern, remain under debate; but the infrastructure seems done. The key bit of infrastructure is a new optional BufferAccessStrategy object that can be passed to ReadBuffer operations; this replaces the former StrategyHintVacuum API. This patch also changes the buffer usage-count methodology a bit: we now advance usage_count when first pinning a buffer, rather than when last unpinning it. To preserve the behavior that a buffer's lifetime starts to decrease when it's released, the clock sweep code is modified to not decrement usage_count of pinned buffers. Work not done in this commit: teach GiST and GIN indexes to use the vacuum BufferAccessStrategy for vacuum-driven fetches. Original patch by Simon, reworked by Heikki and again by Tom.
View Lorry Controller Status