aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
* Allow times of 24:00:00 to match rounding behavior:Bruce Momjian2005-10-14
| | | | | | | | | | | | | | | regression=# select '23:59:59.9'::time(0); time ---------- 24:00:00 (1 row) This is bad because: regression=# select '24:00:00'::time(0); ERROR: date/time field value out of range: "24:00:00" The last example now works.
* Fix uppercase TRUE/FALSE that are WIN32 stuffl.Bruce Momjian2005-10-13
|
* Update regression output for new prepare transaction error messages.Bruce Momjian2005-10-13
|
* Make stack_base_ptr non-static, for PL/Java.Bruce Momjian2005-10-13
|
* This makes the error messages for PREPARE TRANSACTION, COMMIT PREPAREDBruce Momjian2005-10-13
| | | | | | | etc. match the docs, which talk about "transaction identifier" not "gid" or "global transaction identifier". Steve Woodcock
* Update krb_server_name to document that a missing entry defaults toBruce Momjian2005-10-13
| | | | | | 'localhost'. Improve kerberos error message.
* The patch updates the documentation to reflect the fact that higher valuesBruce Momjian2005-10-13
| | | | | | | | | | | | | | | | | | | | of client_min_messages (fatal + panic) are valid and also fixes a slight issue with how psql tried to display error messages that aren't sent to the client. We often tell people to ignore errors in response to requests for things like "drop if exists", but there's no good way to completely hide this without upping client_min_messages past ERROR. When running a file like SET client_min_messages TO 'FATAL'; DROP TABLE doesntexist; with "psql -f filename" you get an error prefix of "psql:/home/username/filename:3" even though there is no error message to prefix because it isn't sent to the client. Kris Jurka
* Go back to emitting path names with forward slashes on Windows.Tom Lane2005-10-13
| | | | | I'm not clear on what the double-backslash idea was intended to fix, but it breaks at least mingw GNU Make. Per report from Thomas Hallgren.
* Back out this because of fear of changing error strings:Bruce Momjian2005-10-13
| | | | | | | | This makes the error messages for PREPARE TRANSACTION, COMMIT PREPARED etc. match the docs, which talk about "transaction identifier" not "gid" or "global transaction identifier". Steve Woodcock
* This makes the error messages for PREPARE TRANSACTION, COMMIT PREPAREDBruce Momjian2005-10-13
| | | | | | | etc. match the docs, which talk about "transaction identifier" not "gid" or "global transaction identifier". Steve Woodcock
* Use get_progname() in backend main.c, rather than port-specific hackBruce Momjian2005-10-13
| | | | that is too fragile.
* Fix small oversight in recent patch to add more CREATE-FUNCTION-timeTom Lane2005-10-13
| | | | | | syntax checking to plpgsql: check_sql_expr() wasn't being called by make_select_stmt(), so that there was no SQL syntax check for SELECT statements.
* Remove an antiquated comment.Neil Conway2005-10-13
|
* Add a comment describing the requirement that pointers into shared memoryNeil Conway2005-10-13
| | | | that is protected by a spinlock must be volatile, per recent discussion.
* Don't try to remove duplicate OR-subclauses in create_bitmap_subplan andTom Lane2005-10-13
| | | | | | | make_restrictinfo_from_bitmapqual. The likelihood of finding duplicates seems much less than in the AND-subclause case, and the cost much higher, because OR lists with hundreds or even thousands of subclauses are not uncommon. Per discussion with Ilia Kantor and andrew@supernews.
* Fix longstanding bug found by Atsushi Ogawa: _bt_check_unique would markTom Lane2005-10-12
| | | | | | the wrong buffer dirty when trying to kill a dead index entry that's on a page after the one it started on. No risk of data corruption, just inefficiency, but still a bug.
* Fix another recently-changed place that was messing with spinlock-Tom Lane2005-10-12
| | | | protected data structures and not using a volatile pointer for same.
* Do all accesses to shared buffer headers through volatile-qualifiedTom Lane2005-10-12
| | | | | | | pointers, to ensure that compilers won't rearrange accesses to occur while we're not holding the buffer header spinlock. It's probably not necessary to mark volatile in every single place in bufmgr.c, but better safe than sorry. Per trouble report from Kevin Grittner.
* Fix typo in sample pg_hba.conf; per IRC report from Bernhard Neuhauser.Neil Conway2005-10-11
|
* Add infrastructure for making spins_per_delay variable depending onTom Lane2005-10-11
| | | | | | whether we seem to be running in a uniprocessor or multiprocessor. The adjustment rules could probably still use further tweaking, but I'm convinced this should be a win overall.
* Don't use a non-locked pre-test of the spinlock on x86_64 machines.Tom Lane2005-10-11
| | | | | The pre-test has been shown to be a big loss on Opterons and at best a wash on EM64T.
* Document that get_attstatsslot/free_attstatsslot only need to be passedTom Lane2005-10-11
| | | | | | | | valid type information if they are asked to fetch the values part of a pg_statistic slot; these arguments are unneeded if fetching only the numbers part. Use this to save a catcache lookup in btcostestimate, which is looking like a bit of a hotspot in recent profiling. Not a big savings, but since it's essentially free, might as well do it.
* Fix oversight in 8.0 modification of RestrictInfo data structures.Tom Lane2005-10-11
| | | | | | | | A RestrictInfo representing an OR clause now contains two versions of the contained expression, one with sub-RestrictInfos and one without. clause_selectivity() should descend to the version with sub-RestrictInfos so that it has a chance of caching its results for the OR's sub-clauses. Failing to do so resulted in redundant planner effort.
* Remove the DELETEs from pg_shadow and pg_group that pg_dumpall used toTom Lane2005-10-10
| | | | | | | | emit when given the --clean option, in favor of individual DROP ROLE commands. The old technique could not possibly work in 8.1, and was never a very good idea anyway IMHO. The DROP ROLE approach has the defect that the DROPs will fail for roles that own objects or have privileges, but perhaps we can improve that later.
* Use a safer order of operations in dropdb(): rollbackable operations,Tom Lane2005-10-10
| | | | | | ie removing shared-dependency entries, should happen before non-rollbackable ones. That way a failure during the rollbackable part doesn't leave us with inconsistent state.
* Document the process to update translations.Peter Eisentraut2005-10-10
|
* Translation updatePeter Eisentraut2005-10-10
|
* Fix the problem of GRANTs creating "dangling" privileges not directlyTom Lane2005-10-10
| | | | | | traceable to grant options. As per my earlier proposal, a GRANT made by a role member has to be recorded as being granted by the role that actually holds the grant option, and not the member.
* <limits.h> is now needed here, for INT_MAX. Per Michael Fuhr.Tom Lane2005-10-10
|
* Fix (hopefully for the last time) problems with datetime values displayingTom Lane2005-10-09
| | | | | | | like '23:59:60' because of fractional-second roundoff problems. Trying to control this upstream of the actual display code was hopeless; the right way is to explicitly round fractional seconds in the display code and then refigure the results if the fraction rounds up to 1. Per bug #1927.
* Fix up grammar in variable description string.Tom Lane2005-10-08
|
* Fix Kerberos authentication in wake of virtual-hosts changes --- needTom Lane2005-10-08
| | | | | | | to call krb5_sname_to_principal() always. Also, use krb_srvname rather than the hardwired string 'postgres' as the appl_version string in the krb5_sendauth/recvauth calls, to avoid breaking compatibility with PG 8.0. Magnus Hagander
* Add spacing around operators.Bruce Momjian2005-10-08
|
* Fix LWLockAssign() so that it can safely be executed after postmasterTom Lane2005-10-07
| | | | initialization. Add spinlocking, fix EXEC_BACKEND unsafeness.
* Minor parentheses cleanup.Bruce Momjian2005-10-07
|
* Add spaces around operator.Bruce Momjian2005-10-07
|
* Allocate a few extra LWLocks for possible use by add-on modules.Tom Lane2005-10-07
| | | | Per request from Marc Munro.
* Marginal performance improvement in aclmask(): don't bother withTom Lane2005-10-07
| | | | | | testing ownership if the caller isn't interested in any GOPTION bits (which is the common case). It did not matter in 8.0 where the ownership test was just a trivial equality test, but it matters now.
* Recognize ERROR_SHARING_VIOLATION (translate to EACCES), increase logTom Lane2005-10-07
| | | | | | level for unrecognized win32 error codes to LOG, and make messages conform to style guide. Per old suggestion from Qingqing Zhou, which seems to have gotten lost in the shuffle.
* Remove an unused typedef.Alvaro Herrera2005-10-07
|
* Marginal speedup in RelationIsVisible and TypeIsVisible: avoid a redundantTom Lane2005-10-06
| | | | | | | cache lookup in the success case. This won't help much for cases where the given relation is far down the search path, but it does not hurt in any cases either; and it requires only a little new code. Per gripe from Jim Nasby about slowness of \d with many tables.
* Minor API cleanup for async notifications: we can only register theNeil Conway2005-10-06
| | | | | current backend in pg_listener, so there is little point in making the PID to register part of async.c's public API. Other minor tweaks.
* When a function not returning RECORD has a single OUT parameter, useTom Lane2005-10-06
| | | | | | | | the parameter's name (if any) as the default column name for SELECT FROM the function, rather than the function name as previously. I still think this is a bad idea, but I lost the argument. Force decompilation of function RTEs to specify full aliases always, to reduce the odds of this decision breaking dumped views.
* Fix oversight in indexscan plan creation. I recently added code to useTom Lane2005-10-06
| | | | | | | | predicate_implied_by() to detect redundant filter conditions, but forgot that predicate_implied_by() assumes its first argument contains only immutable functions. Add a check to guarantee that. Also, test to see if filter conditions can be discarded because they are redundant with the predicate of a partial index.
* pg_config should print an error message to stderr and exit if anPeter Eisentraut2005-10-06
| | | | information item is not available.
* Revise pgstats stuff to fix the problems with not counting accessesTom Lane2005-10-06
| | | | | | | generated by bitmap index scans. Along the way, simplify and speed up the code for counting sequential and index scans; it was both confusing and inefficient to be taking care of that in the per-tuple loops, IMHO. initdb forced because of internal changes in pg_stat view definitions.
* Code cleanup for log_disconnections(). Patch from Qingqing Zhou,Neil Conway2005-10-05
| | | | fixes by Neil Conway.
* Make set_function_size_estimates() marginally smarter: per originalTom Lane2005-10-05
| | | | comment, it can at least test whether the expression returns set.
* Also synced the ecpg lexer with the backend lexer.Michael Meskes2005-10-05
|
* Fix pgxs for spaces in file names on Win32Bruce Momjian2005-10-05
| | | | Dave Page
generated by cgit v1.2.3 (git 2.25.1) at 2025-06-02 12:17:13 +0000