aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* 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
* Remove from TODO ability to edit pg_hba.conf, but add GRANT connectionBruce Momjian2006-04-21
| | | | | | | | | | | | | | 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.
* Add some optional code (conditionally compiled under #ifdef LWLOCK_STATS)Tom Lane2006-04-21
| | | | | | 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.
* Eliminate some no-longer-needed workarounds for palloc's old behaviorTom Lane2006-04-20
| | | | | | | | 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.
* Add "retry another address" log message on statistics collector socketBruce Momjian2006-04-20
| | | | failure, to reduce confusion in the log file.
* Ensure that we validate the page header of the first page of a WAL fileTom Lane2006-04-20
| | | | | | | | | 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.
* Recognize __ppc64__, which seems to be Apple's spelling of the predefinedTom Lane2006-04-19
| | | | | | 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.
* Add detail:Bruce Momjian2006-04-19
| | | | | | < encoding. > encoding. This requires using mblen() to determine if the > backslash is inside or outside a multi-byte sequence.
* Add:Bruce Momjian2006-04-19
| | | | | | | | | | | | | > > o Add new version of PQescapeString() that doesn't double backslashes > that are part of a client-only multibyte sequence > > Single-quote is not a valid byte in any supported client-only > encoding. > > o Add new version of PQescapeString() that doesn't double > backslashes when standard_conforming_strings is true and > non-E strings are used
* Fix problem that sscanf(buf, "%d", &val) eats leading white space, butBruce Momjian2006-04-19
| | | | our to_* functions were not handling that.
* Remove use of lorder and tsort while building static libraries. There'sTom Lane2006-04-19
| | | | | | | | no evidence that any currently-supported platform needs this, and good reason to think that any platform that did need it couldn't use the static libraries anyway --- libpq, at least, has circular references. Removing the code shuts up tsort warnings about the circular references on some platforms.
* Fix ancient memory leak in PQprintTuples(); our code no longer uses thisTom Lane2006-04-19
| | | | | routine, but perhaps some applications do. Found by Martijn van Oosterhout using Coverity.
* Fix a couple of rather-pointless-but-easily-fixed Coverity warnings.Tom Lane2006-04-19
| | | | Per Martijn van Oosterhout.
* C code whitespace inprovement for formatting.c.Bruce Momjian2006-04-19
|
* Add:Bruce Momjian2006-04-19
| | | | | > o Add reporting of the current WAL file, perhaps as part of > partial log file archiving
* Remove kill mention in install docs, was for pre-7.0 releases.Bruce Momjian2006-04-18
|
* Mention "syntax" error as not logged by log_statement.Bruce Momjian2006-04-18
| | | | Backpatch.
* Document that errors are not output by log_statement (was they were inBruce Momjian2006-04-18
| | | | | | | | | 8.0), and add as suggestion to use log_min_error_statement for this purpose. I also fixed the code so the first EXECUTE has it's prepare, rather than the last which is what was in the current code. Also remove "protocol" prefix for SQL EXECUTE output because it is not accurate. Backpatch to 8.1.X.
* Fix the torn-page hazard for PITR base backups by forcing full page writesTom Lane2006-04-17
| | | | | | | | | to occur between pg_start_backup() and pg_stop_backup(), even if the GUC setting full_page_writes is OFF. Per discussion, doing this in combination with the already-existing checkpoint during pg_start_backup() should ensure safety against partial page updates being included in the backup. We do not have to force full page writes to occur during normal PITR operation, as I had first feared.
* Done:Bruce Momjian2006-04-17
| | | | | < o Update pg_dump and psql to use the new COPY libpq API (Christopher) > o -Update pg_dump and psql to use the new COPY libpq API (Christopher)
* Remove:Bruce Momjian2006-04-15
| | | | < o %Have pg_dump use multi-statement transactions for INSERT dumps
* Document that pg_dump -d/-D prevents invalid data from canceling theBruce Momjian2006-04-15
| | | | entire table load.
* Support the syntaxTom Lane2006-04-15
| | | | | | | | | | | | | | CREATE AGGREGATE aggname (input_type) (parameter_list) along with the old syntax where the input type was named in the parameter list. This fits more naturally with the way that the aggregate is identified in DROP AGGREGATE and other utility commands; furthermore it has a natural extension to handle multiple-input aggregates, where the basetype-parameter method would get ugly. In fact, this commit fixes the grammar and all the utility commands to support multiple-input aggregates; but DefineAggregate rejects it because the executor isn't fixed yet. I didn't do anything about treating agg(*) as a zero-input aggregate instead of artificially making it a one-input aggregate, but that should be considered in combination with supporting multi-input aggregates.
* Done:Bruce Momjian2006-04-14
| | | | > * -Re-enable the GUC full_page_writes in 8.2 when reliability issues have
* Make the world safe for full_page_writes. Allow XLOG records that try toTom Lane2006-04-14
| | | | | | | | | update no-longer-existing pages to fall through as no-ops, but make a note of each page number referenced by such records. If we don't see a later XLOG entry dropping the table or truncating away the page, complain at the end of XLOG replay. Since this fixes the known failure mode for full_page_writes = off, revert my previous band-aid patch that disabled that GUC variable.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-08 10:27:13 +0000