aboutsummaryrefslogtreecommitdiff
path: root/src/backend
Commit message (Collapse)AuthorAge
...
* Fix missed message update, per Alvaro Herrera.Tom Lane2003-09-11
|
* Improve error message for cp or rm failur during create/drop database,Tom Lane2003-09-10
| | | | per recent discussions.
* Add HINT if CREATE FUNCTION specifies a valid language, but the languageBruce Momjian2003-09-10
| | | | isn't loaded into the database.
* Some "feature not supported" errors are better syntax errors, because thePeter Eisentraut2003-09-09
| | | | | feature they complain about isn't a feature or cannot be implemented without definitional changes.
* Update comments about how locale settings are handled.Tom Lane2003-09-09
|
* Avoid using s_addr as a local variable name, to work around brokenTom Lane2003-09-08
| | | | system headers on Unixware.
* Remove geqo_random_seed parameter. Having geqo reset the global random()Tom Lane2003-09-07
| | | | | | | | sequence every time it's called is bogus --- it interferes with user control over the seed, and actually decreases randomness overall (because a seed based on time(NULL) is pretty predictable). If you really want a reproducible result from geqo, do 'set seed = 0' before planning a query.
* Remove check on source address of a statistics packet. Check was brokenTom Lane2003-09-07
| | | | | by recent IPv6 changes, and since it's redundant with a kernel-level check anyway, it seems not worth trying to fix it. Per recent discussions.
* Make the default pg_hba.conf include an entry for ::1 only if configureTom Lane2003-09-07
| | | | set HAVE_IPV6. Per recent discussions.
* load_file() has to remove pre-existing shlibs that match the new fileTom Lane2003-09-07
| | | | | | | on either name or inode; otherwise load_external_function() won't do anything. At least on Linux, it appears that recompiling a shlib leads to a new file with a different inode, so the old code failed to detect a match.
* Make all valid uses of the COLLATE clause yield the same result: a syntaxPeter Eisentraut2003-09-06
| | | | | error. There is no point in providing some kind of forward compatibility now, because no one can tell what a future implementation will look like.
* Second try at IPv4-to-v6 mapping code; avoid assuming that the structTom Lane2003-09-05
| | | | returned by getaddrinfo_all will have enough room for an IPv6 address.
* Allow IPv4-format entries in pg_hba.conf to match IPv6 connectionsTom Lane2003-09-05
| | | | that have IPv4-embedded-in-IPv6 addresses. Per idea of Andreas Pflug.
* This fixes three minor typos in hba.c.Bruce Momjian2003-09-05
| | | | | -- Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
* Reimplement hash index locking algorithms, per my recent proposal toTom Lane2003-09-04
| | | | | | | | pghackers. This fixes the problem recently reported by Markus KrÌutner (hash bucket split corrupts the state of scans being done concurrently), and I believe it also fixes all the known problems with deadlocks in hash index operations. Hash indexes are still not really ready for prime time (since they aren't WAL-logged), but this is a step forward.
* Avoid consuming unreasonable amounts of memory when GRANT has manyTom Lane2003-09-04
| | | | grantees.
* Allow non-super users to set log_duration to true, then false, when theBruce Momjian2003-09-04
| | | | | administrator has not turned it on, and fix other PGC_USERLIMIT variables.
* Re-upper case CHECKPOINT_SEGMENTS.Bruce Momjian2003-09-04
|
* Lowercase CHECKPOINT_SEGMENTS.Bruce Momjian2003-09-04
|
* Pass session_authorization to the client and make psql update its promptPeter Eisentraut2003-09-03
| | | | accordingly.
* Work around ENOTEMPTY being an alias for EEXIST on some platforms.Tom Lane2003-09-03
|
* Repair problems with to_char() overrunning its input string.Tom Lane2003-09-03
| | | | From Karel Zak.
* In _bt_check_unique() loop, don't bother applying _bt_isequal() toTom Lane2003-09-02
| | | | | | | | killed items; just skip to the next item immediately. Only check for key equality when we reach a non-killed item or the end of the index page. This saves key comparisons when there are lots of killed items, as for example in a heavily-updated table that's not been vacuumed lately. Seems to be a win for pgbench anyway.
* Cause standalone backend (including bootstrap case) to read the GUCTom Lane2003-09-02
| | | | | | | | | | config file if it exists. This was already discussed as being a good idea, and now seems the cleanest way to deal with initdb-time failures on machines with small SHMMAX. (The submitted patches instead modified initdb.sh to pass the correct sizing parameters, but that would still leave standalone backends prone to failure later. An admin who needs to use a standalone backend has enough trouble already, he shouldn't have to manually configure its shmem settings...)
* Several fixes for hash indexes that involve changing the on-disk indexTom Lane2003-09-02
| | | | | | | | | layout; therefore, this change forces REINDEX of hash indexes (though not a full initdb). Widen hashm_ntuples to double so that hash space management doesn't get confused by more than 4G entries; enlarge the allowed number of free-space-bitmap pages; replace the useless bshift field with a useful bmshift field; eliminate 4 bytes of wasted space in the per-page special area.
* Fix a couple typos, add some more comments.Tom Lane2003-09-02
|
* Rewrite hashbulkdelete() to make it amenable to new bucket lockingTom Lane2003-09-02
| | | | | | | scheme. A pleasant side effect is that it is *much* faster when deleting a large fraction of the indexed tuples, because of elimination of redundant hash_step activity induced by hash_adjscans. Various other continuing code cleanup.
* Do not pass server_encoding to the client.Peter Eisentraut2003-09-01
| | | | | | libpq, talking to an old server, should assume SQL_ASCII as the default client encoding, because that is what the server will actually use (not the server encoding).
* Preliminary cleanup for hash index code (doesn't attack the locking problemTom Lane2003-09-01
| | | | | | | | | yet). Fix a couple of bugs that would only appear if multiple bitmap pages are used, including a buffer reference leak and incorrect computation of bit indexes. Get rid of 'overflow address' concept, which accomplished nothing except obfuscating the code and creating a risk of failure due to limited range of offset field. Rename some misleadingly-named fields and routines, and improve documentation.
* Add some internals documentation for hash indexes, including anTom Lane2003-09-01
| | | | | | explanation of the remarkably confusing page addressing scheme. The file also includes my planned-but-not-yet-implemented revision of the hash index locking scheme.
* Rename DoIt to changeVar, for clarity.Bruce Momjian2003-09-01
|
* Guard against pgindent changing =- to = -.Bruce Momjian2003-08-30
|
* Fix stupid typo (mine I suppose) in CopyGetData. Per report from Dave Cramer.Tom Lane2003-08-28
|
* Adjust date/time input parsing code to correctly distinguish the fourTom Lane2003-08-27
| | | | | | | SQLSTATE error codes required by SQL99 (invalid format, datetime field overflow, interval field overflow, invalid time zone displacement value). Also emit a HINT about DateStyle in cases where it seems appropriate. Per recent gripes.
* Department of second thoughts: can't reorder merge-join clauses.Tom Lane2003-08-27
|
* Share PG_DIAG_* macros between client and server and use them internally.Peter Eisentraut2003-08-27
|
* Push subplan clauses to the back in qual lists for join plans, notTom Lane2003-08-26
| | | | only scan plans. Per observation from Rod Taylor.
* Call it Linux, not GNU/Linux.Bruce Momjian2003-08-26
|
* Use separate SQLSTATE codes for file not found/file exists, rather thanTom Lane2003-08-26
| | | | | | | lumping them into ERRCODE_UNDEFINED_OBJECT/ERRCODE_DUPLICATE_OBJECT. This seems reasonable since 'object' was meant to refer to 'object in the database' and a file is outside the database. Per request from Dave Cramer.
* Attached is a (very small) patch to make analyze display someBruce Momjian2003-08-26
| | | | | | | interesting info in verbose mode about the analyzed relation (pages, rows per block and rows). Mark Kirkwood
* Mop-up for previous change to determine default shared_buffers andTom Lane2003-08-26
| | | | | | max_connections at initdb time. Get rid of DEF_NBUFFERS and DEF_MAXBACKENDS macros, which aren't doing anything useful anymore, and put more likely defaults into postgresql.conf.sample.
* Add the Brazilian time zone abbreviations BRT, BRST, FNT, FNST.Tom Lane2003-08-25
| | | | | ACT and ACST were already present. AMT and AMST conflict with the existing entries for Armenia; no change there for the moment.
* Allow parsing of time and timetz inputs to accept the documented inputTom Lane2003-08-25
| | | | | syntax '040506' for '04:05:06', as well as '0405' for '04:05:00'. This has been broken since 7.2 but was only recently complained of.
* Refactor code so that to_date() does not call to_timestamp() and thenTom Lane2003-08-25
| | | | | | | perform a timestamp-to-date coercion. Instead both routines share a subroutine that delivers the parsing result as a struct tm. This avoids problems with timezone dependency of to_date's result, and should be at least marginally faster too.
* Fix GB18030 to UTF-8 mapping tableTatsuo Ishii2003-08-25
|
* Translation updatesPeter Eisentraut2003-08-24
|
* Change warnings for non-existing or pre-existing cursors to errors.Peter Eisentraut2003-08-24
|
* Fix GB18030 to UTF-8 mapping tableTatsuo Ishii2003-08-24
|
* Fix uninstall target.Peter Eisentraut2003-08-23
|
* Tweak grammar to use FastAppend rather than lappend when constructingTom Lane2003-08-22
| | | | | expr_lists. This appears to be the only remaining O(N^2) bottleneck in processing many-way 'x IN (a,b,c,...)' conditions.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-04 14:51:01 +0000