aboutsummaryrefslogtreecommitdiff
path: root/doc/src
Commit message (Collapse)AuthorAge
...
* Fix broken markup.Tom Lane2006-05-02
|
* Code review for GRANT CONNECT patch. Spell the privilege as CONNECT notTom Lane2006-04-30
| | | | | CONNECTION, fix a number of places that were missed (eg pg_dump support), avoid executing an extra search of pg_database during startup.
* Improve the representation of FOR UPDATE/FOR SHARE so that we canTom Lane2006-04-30
| | | | | | support both FOR UPDATE and FOR SHARE in one command, as well as both NOWAIT and normal WAIT behavior. The more general code is actually simpler and cleaner.
* Done:Bruce Momjian2006-04-30
| | | | > o -Allow per-database permissions to be set via GRANT
* Add GRANT CONNECTION ON DATABASE, to be used in addition to pg_hba.conf.Bruce Momjian2006-04-30
| | | | Gevik Babakhani
* Add question mark:Bruce Momjian2006-04-30
| | | | > * %Disallow changing default expression of a SERIAL column?
* Revert patch pending more discussion:Bruce Momjian2006-04-30
| | | | Disallow changing DEFAULT expression of a SERIAL column.
* Done:Bruce Momjian2006-04-29
| | | | > * -Disallow changing default expression of a SERIAL column
* Add to item log_min_error_messages item:Bruce Momjian2006-04-27
| | | | | > Another idea is to allow separate configuration files for each module, > or allow arbitrary SET commands to be passed to them.
* Add:Bruce Momjian2006-04-27
| | | | | > * Invalidate prepared queries, like INSERT, when the table definition > is altered
* Add support for SSL Certificate Revocation List (CRL) files, root.crl.Bruce Momjian2006-04-27
| | | | Libor Hoho?
* Use schema search path to find the first matching contraint name for SETBruce Momjian2006-04-27
| | | | | | | CONSTRAINT, rather than affecting all constraints in all schemas (which is what we used to do). Also allow schema specifications. Kris Jurka
* 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
* Adjust SGML spacing.Bruce Momjian2006-04-25
|
* Back out the rest of the RESET CONNECTION patch.Tom Lane2006-04-25
|
* 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
* 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
* 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.
* 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.
* 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 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
* 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.
* 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
* Fix HTML markup.Bruce Momjian2006-04-13
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-06-12 19:20:05 +0000