summaryrefslogtreecommitdiff
path: root/doc
Commit message (Collapse)AuthorAgeFilesLines
* Change typreceive function API so that receive functions get the sameTom Lane2005-07-101-7/+8
| | | | | | | optional arguments as text input functions, ie, typioparam OID and atttypmod. Make all the datatypes that use typmod enforce it the same way in typreceive as they do in typinput. This fixes a problem with failure to enforce length restrictions during COPY FROM BINARY.
* Add --encoding to pg_dump.Bruce Momjian2005-07-101-1/+13
| | | | | | | | | | | | The Problem: Occassionally a DBA needs to dump a database to a new encoding. In instances where the current encoding, (or lack of an encoding, like SQL_ASCII) is poorly supported on the target database server, it can be useful to dump into a particular encoding. But, currently the only way to set the encoding of a pg_dump file is to change client_encoding in postgresql.conf and restart postmaster. This is more than a little awkward for production systems. Magnus Hagander
* Update.Bruce Momjian2005-07-102-9/+4
| | | | | | | | < computations should adjust based on the time zone rules, e.g. < adding 24 hours to a timestamp would yield a different result from < adding one day. < > computations should adjust based on the time zone rules.
* I made the patch that implements regexp_replace again.Bruce Momjian2005-07-101-1/+21
| | | | | | | | | | | | | | | | | | | | | | | The specification of this function is as follows. regexp_replace(source text, pattern text, replacement text, [flags text]) returns text Replace string that matches to regular expression in source text to replacement text. - pattern is regular expression pattern. - replacement is replace string that can use '\1'-'\9', and '\&'. '\1'-'\9': back reference to the n'th subexpression. '\&' : entire matched string. - flags can use the following values: g: global (replace all) i: ignore case When the flags is not specified, case sensitive, replace the first instance only. Atsushi Ogawa
* Add psql \pset numericsep to allow output numbers like 100,000.0 orBruce Momjian2005-07-101-1/+13
| | | | | | 100.000,0. Eugen Nedelcu
* Done:Bruce Momjian2005-07-082-4/+4
| | | | > * -Prevent dropping user that still owns objects, or auto-drop the objects
* Track dependencies on shared objects (which is to say, roles; we alreadyTom Lane2005-07-071-3/+157
| | | | | | | have adequate mechanisms for tracking the contents of databases and tablespaces). This solves the longstanding problem that you can drop a user who still owns objects and/or has access permissions. Alvaro Herrera, with some kibitzing from Tom Lane.
* Update:Bruce Momjian2005-07-072-4/+8
| | | | | | | < writer. > writer. It might cause problems for applying WAL on recovery > into a partially-written page, but later the full page will be > replaced from WAL.
* Update:Bruce Momjian2005-07-072-2/+21
| | | | | | | | | | | | > > o -Add ability to turn off full page writes > o When off, write CRC to WAL and check file system blocks > on recovery > o Write full pages during file system write and not when > the page is modified in the buffer cache > > This allows most full page writes to happen in the background > writer.
* Reverse out because the lack of using pgport in timezone/ is causingBruce Momjian2005-07-061-18/+1
| | | | | | | | | | problems: --------------------------------------------------------------------------- Support cross compilation by compiling "zic" with a native compiler. This relies on the output of zic being platform independent, but that is currently the case.
* Add pg_column_size() to return storage size of a column, includingBruce Momjian2005-07-061-1/+9
| | | | | | possible compression. Mark Kirkwood
* Update description of GUC full_page_writes.Bruce Momjian2005-07-061-6/+7
| | | | Michael Paesold
* Done:Bruce Momjian2005-07-062-4/+4
| | | | > * -Add function to return compressed length of TOAST data values
* Add GUC full_page_writes to control writing full pages to WAL.Bruce Momjian2005-07-051-2/+35
|
* Remove, now have GUC:Bruce Momjian2005-07-052-9/+2
| | | | | | | < * Turn off full page writes if fsync is disabled < < If fsync is off, there is no purpose in writing full pages to WAL <
* Add:Bruce Momjian2005-07-052-3/+6
| | | | | | | < 881a881,882 > o Improve xid wraparound detection by recording per-table rather > than per-database
* More TODO list section restructuring.Bruce Momjian2005-07-042-165/+221
|
* Restructure TODO sections.Bruce Momjian2005-07-042-455/+500
|
* UpdateBruce Momjian2005-07-042-2/+8
| | | | | | | | > * Allow GIST indexes to create certain complex index types, like digital > trees (see Aoki) > 783a787 >
* Update wording:Bruce Momjian2005-07-042-6/+6
| | | | | | | | < Currently, to protect against partial disk page writes, we write the > Currently, to protect against partial disk page writes, we write 877c877 < * Turn off after-change writes if fsync is disabled > * Turn off full page writes if fsync is disabled
* Support cross compilation by compiling "zic" with a native compiler. ThisPeter Eisentraut2005-07-031-1/+18
| | | | | relies on the output of zic being platform independent, but that is currently the case.
* Remove GIST concurrency limitations section.Bruce Momjian2005-07-021-20/+1
| | | | Christopher Kings-Lynne
* Add SGML markup for on/off values in run-time section.Bruce Momjian2005-07-021-50/+54
|
* Use on/off consistently for GUC variables in postgresql.conf and theBruce Momjian2005-07-021-16/+16
| | | | documentation, to match SHOW.
* Update:Bruce Momjian2005-07-022-4/+4
| | | | | < * Add rtree index support for line, lseg, path, point > * Add more gist index support for geometric data types
* In PL/PgSQL, allow a block's label to be optionally specified at theNeil Conway2005-07-021-17/+18
| | | | | | | | | | | | | end of the block: <<label>> begin ... end label; Similarly for loops. This is per PL/SQL. Update the documentation and add regression tests. Patch from Pavel Stehule, code review by Neil Conway.
* Clarify:Bruce Momjian2005-07-012-6/+6
| | | | | | | < o Replace crude DELETE FROM method of pg_dumpall for cleaning of < roles with separate DROP commands > o Replace crude DELETE FROM method of pg_dumpall --clean for > cleaning of roles with separate DROP commands
* Update for roles:Bruce Momjian2005-07-012-19/+8
| | | | | | | | | | | | | | | | | < * Allow limits on per-db/user connections > * Allow limits on per-db/role connections < * Prevent default re-use of sysids for dropped users and roles < < Currently, if a user is removed while he still owns objects, a new < user given might be given their user id and inherit the < previous users objects. < 450c444 < * Add COMMENT ON for all cluster global objects (users, roles, databases > * Add COMMENT ON for all cluster global objects (roles, databases 609c603 < users and roles with separate DROP commands > roles with separate DROP commands
* Update for roles:Bruce Momjian2005-07-012-8/+8
| | | | | | | | | | | < * Prevent default re-use of sysids for dropped users and groups > * Prevent default re-use of sysids for dropped users and roles 450c450 < * Add COMMENT ON for all cluster global objects (users, groups, databases > * Add COMMENT ON for all cluster global objects (users, roles, databases 609c609 < users and groups with separate DROP commands > users and roles with separate DROP commands
* Item superceeded now that groups exist:Bruce Momjian2005-07-012-6/+2
| | | | | < * Add group object ownership, so groups can rename/drop/grant on objects, < so we can implement roles
* Done:Bruce Momjian2005-07-012-6/+4
| | | | > o -Add dumping and restoring of LOB comments
* Clarify documentation about log_min_duration_statement.Bruce Momjian2005-07-011-11/+12
|
* Improve gettimeofday() documentation.Bruce Momjian2005-06-291-12/+14
| | | | Karl O. Pinc
* Improved words spacing.Bruce Momjian2005-06-291-7/+7
| | | | Victor Y. Yegorov
* Replace pg_shadow and pg_group by new role-capable catalogs pg_authidTom Lane2005-06-282-211/+511
| | | | | | | | and pg_auth_members. There are still many loose ends to finish in this patch (no documentation, no regression tests, no pg_dump support for instance). But I'm going to commit it now anyway so that Alvaro can make some progress on shared dependencies. The catalog changes should be pretty much done.
* Done:Bruce Momjian2005-06-272-4/+4
| | | | > * -Add concurrency to GIST
* Done:Bruce Momjian2005-06-272-4/+4
| | | | > * -Remove kerberos4 from source tree
* Remove support for Kerberos V4. It seems no one is using this, it hasNeil Conway2005-06-274-86/+11
| | | | | some security issues, and upstream has declared it "dead". Patch from Magnus Hagander, minor editorialization from Neil Conway.
* Done:Bruce Momjian2005-06-272-4/+4
| | | | > o -Allow PL/pgSQL EXECUTE query_var INTO record_var;
* Add Oracle-compatible GREATEST and LEAST functions. Pavel StehuleTom Lane2005-06-262-8/+53
|
* Code review for escape-strings patch. Sync psql and plpgsql lexersTom Lane2005-06-265-40/+48
| | | | | | | with main, avoid using a SQL-defined SQLSTATE for what is most definitely not a SQL-compatible error condition, fix documentation omissions, adhere to message style guidelines, don't use two GUC_REPORT variables when one is sufficient. Nothing done about pg_dump issues.
* Add E'' syntax so eventually normal strings can treat backslashesBruce Momjian2005-06-262-5/+75
| | | | | | | | | | | | literally. Add GUC variables: "escape_string_warning" - warn about backslashes in non-E strings "escape_string_syntax" - supports E'' syntax? "standard_compliant_strings" - treats backslashes literally in '' Update code to use E'' when escapes are used.
* Force a checkpoint before committing a CREATE DATABASE command. ThisTom Lane2005-06-251-1/+13
| | | | | | should fix the recent reports of "index is not a btree" failures, as well as preventing a more obscure race condition involving changes to a template database just after copying it with CREATE DATABASE.
* Add:Bruce Momjian2005-06-252-2/+6
| | | | | > o Pass arrays natively instead of as text between plperl and postgres > o Add support for polymorphic arguments and return types to plperl
* Update:Bruce Momjian2005-06-252-4/+4
| | | | | < * Allow per-user, per-group quotas per-tablespace > * Allow per-tablespace quotas
* Update:Bruce Momjian2005-06-252-4/+4
| | | | | < * Allow per-user and per-tablespaces quotas > * Allow per-user, per-group quotas per-tablespace
* Add:Bruce Momjian2005-06-252-2/+4
| | | | > * Allow per-user and per-tablespaces quotas
* Add item:Bruce Momjian2005-06-252-3/+26
| | | | | | | | | | | | | | > * Add NUMERIC division operator that doesn't round? > > Currently NUMERIC _rounds_ the result to the specified precision. > This means division can return a result that multiplied by the > divisor is greater than the dividend, e.g. this returns a value > 10: > > SELECT (10::numeric(2,0) / 6::numeric(2,0))::numeric(2,0) * 6; > > The positive modulus result returned by NUMERICs might be considered > inaccurate, in one sense. >
* Add desciption for terminate:Bruce Momjian2005-06-242-2/+7
| | | | | | > > Currently SIGTERM of a backend can lead to lock table corruption. >
* Extend r-tree operator classes to handle Y-direction tests equivalentTom Lane2005-06-243-19/+75
| | | | | | | | | | | | | | | to the existing X-direction tests. An rtree class now includes 4 actual 2-D tests, 4 1-D X-direction tests, and 4 1-D Y-direction tests. This involved adding four new Y-direction test operators for each of box and polygon; I followed the PostGIS project's lead as to the names of these operators. NON BACKWARDS COMPATIBLE CHANGE: the poly_overleft (&<) and poly_overright (&>) operators now have semantics comparable to box_overleft and box_overright. This is necessary to make r-tree indexes work correctly on polygons. Also, I changed circle_left and circle_right to agree with box_left and box_right --- formerly they allowed the boundaries to touch. This isn't actually essential given the lack of any r-tree opclass for circles, but it seems best to sync all the definitions while we are at it.
View Lorry Controller Status