- 25 4月, 2006 19 次提交
-
-
由 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 7 次提交
-
-
由 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.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Intel compiler has a bug in checking for division by NAN # (NaN == 0), -mp1 fixes it, so someday we might way to add it.
-
由 Bruce Momjian 提交于
the Intel compiler. Jeremy Drake
-
由 Bruce Momjian 提交于
permission item: < o %Allow pg_hba.conf settings to be controlled via SQL > o %Allow per-database permissions to be set via GRANT < This would add a function to load the SQL table from < pg_hba.conf, and one to writes its contents to the flat file. < The table should have a line number that is a float so rows < can be inserted between existing rows, e.g. row 2.5 goes < between row 2 and row 3. > Allow database connection checks based on GRANT rules in > addition to the existing access checks in pg_hba.conf.
-
由 Tom Lane 提交于
to track the number of LWLock acquisitions and the number of times we block waiting for an LWLock, on a per-process basis. After having needed this twice in the past few months, seems like it should go into CVS.
-
- 21 4月, 2006 1 次提交
-
-
由 Tom Lane 提交于
of rejecting palloc(0). Also, tweak like_selectivity() to avoid assuming the presented pattern is nonempty; although that assumption is valid, it doesn't really help much, and the new coding is more correct anyway since it properly handles redundant wildcards. In combination these changes should eliminate a Coverity warning noted by Martijn.
-
- 20 4月, 2006 3 次提交
-
-
由 Bruce Momjian 提交于
failure, to reduce confusion in the log file.
-
由 Tom Lane 提交于
whenever we start to read within that file. The first page carries extra identification information that really ought to be checked, but as the code stood, this was only checked when we switched sequentially into a new WAL file, or if by chance the starting checkpoint record was within the first page. This patch ensures that we will detect bogus 'long header' information before we start replaying the WAL sequence.
-
由 Tom Lane 提交于
symbol for PPC64 hardware. I hadn't known that Apple supported PPC64 at all, but darn if there aren't 64-bit variant libraries in OS X as well as support in their gcc.
-