aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* 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
* Enable threaded python builds on freebsd5, per report from Jim C. NasbyBruce Momjian2005-10-13
|
* Turn off list of tables, figures, and examples.Peter Eisentraut2005-10-13
|
* 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
* Rewording, use the more common multi-threaded/single-threaded.Bruce Momjian2005-10-13
|
* Clarify causes of possible mismatch between Win32 libraries andBruce Momjian2005-10-13
| | | | applications that use FILE pointers.
* Some additional doc changes based around compression of page images inBruce Momjian2005-10-13
| | | | | | | | | | | | | | | | | WAL and the interaction of the new full_page_writes parameter with PITR. The too-small WAL first sect1 has been merged with the one following sect1 for clarity. Some minor comments have been made in the WAL config section also. Passes SGML make and proofread for typos. Files changed: patching file doc/src/sgml/backup.sgml patching file doc/src/sgml/config.sgml patching file doc/src/sgml/wal.sgml Simon Riggs
* Mark xslt_process() as volatile.Bruce Momjian2005-10-13
|
* 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.
* Change xpath_table() and xslt_process() from IMMUTABLE to STABLE.Bruce Momjian2005-10-13
|
* Fix capitalization of example.Bruce Momjian2005-10-13
|
* 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.
* Update trigger demo to reflect new trigger ordering.Bruce Momjian2005-10-13
|
* Remove extra <para>Bruce Momjian2005-10-13
|
* Update:Bruce Momjian2005-10-13
| | | | | | | | > * Prevent PQfnumber() from lowercasing unquoted the column name > > PQfnumber() should never have been doing lowercasing, but historically > it has so we need a way to prevent it >
* 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 spelling error, per Michael Fuhr.Tom Lane2005-10-12
|
* Remove item:Bruce Momjian2005-10-12
| | | | | | | | < * Prevent libpq's PQfnumber() from lowercasing the column name < < One idea is to lowercase all identifiers except those that are < surrounded by quotes. <
* 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.
* Add warning about plperl nested named subroutinesBruce Momjian2005-10-12
| | | | Andrew Dunstan
* No longer needed:Bruce Momjian2005-10-12
| | | | | | | | | | | < < * Add code to detect an SMP machine and handle spinlocks accordingly < from distributted.net, http://www1.distributed.net/source, < in client/common/cpucheck.cpp < < On SMP machines, it is possible that locks might be released shortly, < while on non-SMP machines, the backend should sleep so the process < holding the lock can complete and release it.
* Rearrange:Bruce Momjian2005-10-12
| | | | | | | | | < o %Add dumping of comments on composite type columns < o %Add dumping of comments on index columns < o Stop dumping CASCADE on DROP TYPE commands in clean mode > o %Add dumping of comments on index columns and composite type columns 604a603 > o Stop dumping CASCADE on DROP TYPE commands in clean mode
* Done:Bruce Momjian2005-10-12
| | | | | | | < o %Replace crude DELETE FROM method of pg_dumpall --clean for < cleaning of roles with separate DROP commands 608a607 >
* Add:Bruce Momjian2005-10-12
| | | | | | < > o Allow pg_dump --clean to drop roles that own objects or have > privileges
* Update keywords table for 8.1.Peter Eisentraut2005-10-12
|
* Add description:Bruce Momjian2005-10-12
| | | | | | | | | < * Prevent libpq's PQfnumber() from lowercasing the column name? > * Prevent libpq's PQfnumber() from lowercasing the column name > > One idea is to lowercase all identifiers except those that are > surrounded by quotes. >
* Add:Bruce Momjian2005-10-12
| | | | > o Add options like pg_restore -l and -L to pg_dump
* Add:Bruce Momjian2005-10-11
| | | | | | | > o Allow selection of individual object(s) of all types, not just > tables > o In a selective dump, allow dumping of an object and all its > dependencies
* must commit *after* autoconf, not beforeREL8_1_0BETA3PostgreSQL Daemon2005-10-11
|
* update to beta3 before tagging ...PostgreSQL Daemon2005-10-11
|
* Fix typo in sample pg_hba.conf; per IRC report from Bernhard Neuhauser.Neil Conway2005-10-11
|
* Release notes up to date as of today.Tom Lane2005-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 a thinko in description of krb_server_hostname.Tom Lane2005-10-08
|