aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* Move ltree parentsel() selectivity function into /contrib/ltree.Bruce Momjian2006-04-26
|
* In pg_resetxlog.c, uint -> uint32, for Win32 port.Bruce Momjian2006-04-26
|
* Add missing ControlFile.checkPointCopy.ThisTimeLineID line for 'guess'Bruce Momjian2006-04-26
| | | | | | pg_resetxlog. Simon
* Update catalog version for ltree changes.Bruce Momjian2006-04-26
|
* Enhanced containment selectivity function for /contrib/ltreeBruce Momjian2006-04-26
| | | | Matteo Beccati
* Allow pg_resetxlog -f to reset pg_control counters using xlogBruce Momjian2006-04-26
| | | | | | | information, and add a -r option to reset pg_control without affecting xlog. yuanjia lee
* Done:Bruce Momjian2006-04-26
| | | | * -Allow WAL information to recover corrupted pg_controldata
* Revise large-object access routines to avoid running with CurrentMemoryContextTom Lane2006-04-26
| | | | | | | | | | | | | set to the large object context ("fscxt"), as this is inevitably a source of transaction-duration memory leaks. Not sure why we'd not noticed it before; maybe people weren't touching a whole lot of LOs in the same transaction before the 8.1 pg_dump changes. Per report from Wayne Conrad. Backpatched as far as 8.1, but the problem doubtless goes all the way back. I'm disinclined to spend the time to try to verify that the older branches would still work if patched, seeing that this code was significantly modified for 8.0 and again for 8.1, and that we don't have any trouble reports before 8.1. (Maybe the leaks were smaller before?)
* Arrange to cache btree metapage data in the relcache entry for the index,Tom Lane2006-04-25
| | | | | | | thereby saving a visit to the metapage in most index searches/updates. This wouldn't actually save any I/O (since in the old regime the metapage generally stayed in cache anyway), but it does provide a useful decrease in bufmgr traffic in high-contention scenarios. Per my recent proposal.
* Adjust SGML spacing.Bruce Momjian2006-04-25
|
* Back out the rest of the RESET CONNECTION patch.Tom Lane2006-04-25
|
* The 8.1 planner removes WHERE quals from the plan when the quals areTom Lane2006-04-25
| | | | | | | implied by the predicate of a partial index being used to scan a table. However, this optimization is unsafe in an UPDATE, DELETE, or SELECT FOR UPDATE query, because the quals need to be rechecked by EvalPlanQual if there's an update conflict. Per example from Jean-Samuel Reynaud.
* Remove equals sign from environment variable with not defaults forBruce Momjian2006-04-25
| | | | configure.
* Make configure environment variable options without defaults not have anBruce Momjian2006-04-25
| | | | equals sign.
* Add documentation about configure environment variabbles used.Bruce Momjian2006-04-25
| | | | David Wheeler
* Call SET varaiables "configuration_parameter"s in the documentation.Bruce Momjian2006-04-25
|
* Change "parameter" to "varname" in the alter role and alter userBruce Momjian2006-04-25
| | | | | | documentation sections. Also update SET/RESET to be consistent. Nicolas Barbier
* I now see we support RESET SESSION AUTHORIZATION, so it seems we have toBruce Momjian2006-04-25
| | | | | | | | | | use RESET CONNECTION: < * Add RESET SESSION command to reset all session state > * Add RESET CONNECTION command to reset all session state 447c447 < notify the protocol when a RESET SESSION command is used. > notify the protocol when a RESET CONNECTION command is used.
* RESET SESSION is more precise:Bruce Momjian2006-04-25
| | | | | | | | < * Add RESET CONNECTION command to reset all session state > * Add RESET SESSION command to reset all session state 447c447 < notify the protocol when a RESET CONNECTION command is used. > notify the protocol when a RESET SESSION command is used.
* Back out RESET CONNECTION until there is more discussion.Bruce Momjian2006-04-25
|
* Add RESET CONNECTION, to reset all aspects of a session.Bruce Momjian2006-04-25
| | | | Hans-J?rgen Sch?nig
* Update inheritance constraint items:Bruce Momjian2006-04-25
| | | | | | | | | | | | | < o %Prevent child tables from altering or dropping constraints < like CHECK that were inherited from the parent table < like CHECK that are inherited by child tables < < Dropping constraints should only be possible with CASCADE. < > like CHECK that are inherited by child tables unless CASCADE > is used > o %Prevent child tables from altering or dropping constraints > like CHECK that were inherited from the parent table
* Fix bug reported by Michael Fuhr on Sun, 23 Apr 2006 09:52:31 -0600Tatsuo Ishii2006-04-25
| | | | (pgsql-committers@postgresql.org).
* Done:Bruce Momjian2006-04-25
| | | | > * -Add transaction_timestamp(), statement_timestamp(), clock_timestamp()
* Add statement_timestamp(), clock_timestamp(), andBruce Momjian2006-04-25
| | | | | | | | | transaction_timestamp() (just like now()). Also update statement_timeout() to mention it is statement arrival time that is measured. Catalog version updated.
* Word wrap entryBruce Momjian2006-04-25
|
* Update SQL-standard INTERVAL item:Bruce Momjian2006-04-25
| | | | | | | | | | | | | | | | | | | | | | | | o Support ISO INTERVAL syntax if units cannot be determined from the string, and are supplied after the string The SQL standard states that the units after the string specify the units of the string, e.g. INTERVAL '2' MINUTE should return '00:02:00'. The current behavior has the units restrict the interval value to the specified unit or unit range, INTERVAL '70' SECOND returns '00:00:10'. For syntax that isn't uniquely ISO or PG syntax, like '1' or '1:30', treat as ISO if there is a range specification clause, and as PG if there no clause is present, e.g. interpret '1:30' MINUTE TO SECOND as '1 minute 30 seconds', and interpret '1:30' as '1 hour, 30 minutes'. This makes common cases like SELECT INTERVAL '1' MONTH SQL-standard results. The SQL standard supports a limited number of unit combinations and doesn't support unit names in the string. The PostgreSQL syntax is more flexible in the range of units supported, e.g. PostgreSQL supports '1 year 1 hour', while the SQL standard does not.
* Done;Bruce Momjian2006-04-24
| | | | | o -Add support for day-time syntax, INTERVAL '1 2:03:04'DAY TO SECOND
* Back out patch, unintended.Bruce Momjian2006-04-24
|
* Done:Bruce Momjian2006-04-24
| | | | | o -Add support for day-time syntax, INTERVAL '1 2:03:04' DAY TO SECOND
* Suppress more compiler warnings caused by macro tests.Bruce Momjian2006-04-24
|
* Add one more paren to macro.Bruce Momjian2006-04-24
|
* Suprress compiler warning in gcc 4.2.Bruce Momjian2006-04-24
| | | | Report by Kris Jurka
* Improve our private implementation of cbrt() to give results of theTom Lane2006-04-24
| | | | | accuracy expected by the regression tests. Per suggestion from Martijn van Oosterhout.
* Remove compiler warning by casting SNPRINTF() call to void.Bruce Momjian2006-04-24
| | | | Report from Gevik Babakhani.
* Fixed memory leak bugs found by Martijn Oosterhout.Michael Meskes2006-04-24
|
* Fixes for BCC 5.5 compile of libpq. Backpatch to 8.1.X.Bruce Momjian2006-04-24
| | | | Mark Morgan Lloyd
* Don't add a shared dependency on the owner of a composite type in pg_class.Alvaro Herrera2006-04-24
| | | | | We track the owner in pg_type instead, as that is the place where the owner is changed on ALTER TYPE ... OWNER TO.
* Add:Bruce Momjian2006-04-23
| | | | | | | | | | | | | < * -Eventually enable escape_string_warning and standard_conforming_strings > * -Enable escape_string_warning and standard_conforming_strings > * Make standard_conforming_strings the default in 8.3? > > When this is done, backslash-quote should be prohibited in non-E'' > strings because of possible confusion over how such strings treat > backslashes. Basically, '' is always safe for a literal single > quote, while \' might or might not be based on the backslash > handling rules. >
* Removes or minimizes some documentation mentions of backwardBruce Momjian2006-04-23
| | | | | | compatibility for release 7.2 and earlier. I have not altered any mentions of release 7.3 or later. The release notes were not modified, so the changes are still documented, just not in the main docs.
* Add pgrowlocksTatsuo Ishii2006-04-23
|
* Add new contrib function pgrowlocks. See README.pgrowlocks for more details.Tatsuo Ishii2006-04-23
|
* Update:Bruce Momjian2006-04-22
| | | | | < o Fix psql's backslash commands more consistent > o Fix psql's \d commands more consistent
* Update:Bruce Momjian2006-04-22
| | | | | | | < o Fix psql's \dn for various schema combinations (Neil) > o Fix psql's backslash commands more consistent 625a626 > http://archives.postgresql.org/pgsql-hackers/2004-11/msg00014.php
* Update:Bruce Momjian2006-04-22
| | | | | | o Fix psql's \dn for various schema combinations (Neil) http://archives.postgresql.org/pgsql-hackers/2004-11/msg00014.php
* Suggest Win32 users user E'' strings and double backslashes used forBruce Momjian2006-04-22
| | | | | | patch separators in COPY. Backpatch doubleing backslashes suggestion to 8.1.
* Simplify ParamListInfo data structure to support only numbered parameters,Tom Lane2006-04-22
| | | | | | | not named ones, and replace linear searches of the list with array indexing. The named-parameter support has been dead code for many years anyway, and recent profiling suggests that the searching was costing a noticeable amount of performance for complex queries.
* Revert Intel compiler bug comment.Bruce Momjian2006-04-22
|
* Add mentioun of Intel compiler bug:Bruce Momjian2006-04-22
| | | | | Intel compiler has a bug in checking for division by NAN # (NaN == 0), -mp1 fixes it, so someday we might way to add it.
* Use special gcc -W flags only if we are using gcc, not if we are usingBruce Momjian2006-04-21
| | | | | | the Intel compiler. Jeremy Drake
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-05 16:03:07 +0000