- 26 4月, 2006 5 次提交
-
-
由 Tom Lane 提交于
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?)
-
由 Tom Lane 提交于
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.
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
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.
-
- 25 4月, 2006 23 次提交
-
-
由 Bruce Momjian 提交于
configure.
-
由 Bruce Momjian 提交于
equals sign.
-
由 Bruce Momjian 提交于
David Wheeler
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
documentation sections. Also update SET/RESET to be consistent. Nicolas Barbier
-
由 Bruce Momjian 提交于
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.
-
由 Bruce Momjian 提交于
< * 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.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Hans-J?rgen Sch?nig
-
由 Bruce Momjian 提交于
< 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
-
由 Tatsuo Ishii 提交于
(pgsql-committers@postgresql.org).
-
由 Bruce Momjian 提交于
> * -Add transaction_timestamp(), statement_timestamp(), clock_timestamp()
-
由 Bruce Momjian 提交于
transaction_timestamp() (just like now()). Also update statement_timeout() to mention it is statement arrival time that is measured. Catalog version updated.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
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.
-
由 Bruce Momjian 提交于
o -Add support for day-time syntax, INTERVAL '1 2:03:04'DAY TO SECOND
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
o -Add support for day-time syntax, INTERVAL '1 2:03:04' DAY TO SECOND
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Report by Kris Jurka
-
由 Tom Lane 提交于
accuracy expected by the regression tests. Per suggestion from Martijn van Oosterhout.
-
由 Bruce Momjian 提交于
Report from Gevik Babakhani.
-
- 24 4月, 2006 3 次提交
-
-
由 Michael Meskes 提交于
-
由 Bruce Momjian 提交于
Mark Morgan Lloyd
-
由 Alvaro Herrera 提交于
We track the owner in pg_type instead, as that is the place where the owner is changed on ALTER TYPE ... OWNER TO.
-
- 23 4月, 2006 7 次提交
-
-
由 Bruce Momjian 提交于
< * -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. >
-
由 Bruce Momjian 提交于
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.
-
由 Tatsuo Ishii 提交于
-
由 Tatsuo Ishii 提交于
-
由 Bruce Momjian 提交于
< o Fix psql's backslash commands more consistent > o Fix psql's \d commands more consistent
-
由 Bruce Momjian 提交于
< 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
-
由 Bruce Momjian 提交于
o Fix psql's \dn for various schema combinations (Neil) http://archives.postgresql.org/pgsql-hackers/2004-11/msg00014.php
-
- 22 4月, 2006 2 次提交
-
-
由 Bruce Momjian 提交于
patch separators in COPY. Backpatch doubleing backslashes suggestion to 8.1.
-
由 Tom Lane 提交于
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.
-