aboutsummaryrefslogtreecommitdiff
path: root/doc/src
Commit message (Collapse)AuthorAge
...
* Provide an upgrade strategy for dump files containing functions declaredTom Lane2002-09-21
| | | | | | | | with OPAQUE. CREATE LANGUAGE, CREATE TRIGGER, and CREATE TYPE will all accept references to functions declared with OPAQUE --- but they will issue a NOTICE, and will modify the function entries in pg_proc to have the preferred type-safe argument or result types instead of OPAQUE. Per recent pghackers discussions.
* Add more appropriate markup.Peter Eisentraut2002-09-21
|
* RevisionPeter Eisentraut2002-09-20
|
* Mention that pg_get_viewdef(name) is deprecated.Bruce Momjian2002-09-20
| | | | Rod Taylor
* This patch corrects a minor mis-statement in the CREATE DOMAIN docs,Bruce Momjian2002-09-20
| | | | | | | pointed out by Chris KL on -hackers a little while ago -- NOT NULL != CHECK xxx IS NOT NULL. Neil Conway
* Extend pg_cast castimplicit column to a three-way value; this allows usTom Lane2002-09-18
| | | | | | | | | | | | | | | | | | | | | | | | to be flexible about assignment casts without introducing ambiguity in operator/function resolution. Introduce a well-defined promotion hierarchy for numeric datatypes (int2->int4->int8->numeric->float4->float8). Change make_const to initially label numeric literals as int4, int8, or numeric (never float8 anymore). Explicitly mark Func and RelabelType nodes to indicate whether they came from a function call, explicit cast, or implicit cast; use this to do reverse-listing more accurately and without so many heuristics. Explicit casts to char, varchar, bit, varbit will truncate or pad without raising an error (the pre-7.2 behavior), while assigning to a column without any explicit cast will still raise an error for wrong-length data like 7.3. This more nearly follows the SQL spec than 7.2 behavior (we should be reporting a 'completion condition' in the explicit-cast cases, but we have no mechanism for that, so just do silent truncation). Fix some problems with enforcement of typmod for array elements; it didn't work at all in 'UPDATE ... SET array[n] = foo', for example. Provide a generalized array_length_coerce() function to replace the specialized per-array-type functions that used to be needed (and were missing for NUMERIC as well as all the datetime types). Add missing conversions int8<->float4, text<->numeric, oid<->int8. initdb forced.
* Update installation instructions and put mostly everything in one place.Peter Eisentraut2002-09-18
| | | | Also, some editing in PL/Perl and PL/Python chapters.
* Remove pgeasy and odbc.Peter Eisentraut2002-09-18
|
* Point out that CREATE INDEX uses sorts and hence sort_mem GUC parameter.Bruce Momjian2002-09-17
|
* Cast functions can be immutable or stable.Peter Eisentraut2002-09-15
|
* Some PL/PgSQL documentation improvements from Neil Conway.Tom Lane2002-09-14
|
* Shrink the pg_hba.conf and pg_ident.conf default files and move most of thePeter Eisentraut2002-09-14
| | | | inline documentation to the main docs.
* Add more information about schemas. Combines some previously existingPeter Eisentraut2002-09-12
| | | | material into the new location.
* Joe Conway wrote:Bruce Momjian2002-09-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | > Hannu Krosing wrote: > >> It seems that my last mail on this did not get through to the list >> ;( >> >> Please consider renaming the new builtin function >> split(text,text,int) >> >> to something else, perhaps >> >> split_part(text,text,int) >> >> (like date_part) >> >> The reason for this request is that 3 most popular scripting >> languages (perl, python, php) all have also a function with similar >> signature, but returning an array instead of single element and the >> (optional) third argument is limit (maximum number of splits to >> perform) >> >> I think that it would be good to have similar function in (some >> future release of) postgres, but if we now let in a function with >> same name and arguments but returning a single string instead an >> array of them, then we will need to invent a new and not so easy to >> recognise name for the "real" split function. >> > > This is a good point, and I'm not opposed to changing the name, but > it is too bad your original email didn't get through before beta1 was > rolled. The change would now require an initdb, which I know we were > trying to avoid once beta started (although we could change it > without *requiring* an initdb I suppose). > > I guess if we do end up needing an initdb for other reasons, we > should make this change too. Any other opinions? Is split_part an > acceptable name? > > Also, if we add a todo to produce a "real" split function that > returns an array, similar to those languages, I'll take it for 7.4. No one commented on the choice of name, so the attached patch changes the name of split(text,text,int) to split_part(text,text,int) per Hannu's recommendation above. This can be applied without an initdb if current beta testers are advised to run: update pg_proc set proname = 'split_part' where proname = 'split'; in the case they want to use this function. Regression and doc fix is also included in the patch. Joe Conway
* Fix atan() description.Bruce Momjian2002-09-11
| | | | Bruno Wolff III
* Remove more references to pgaccess as a build target in docs.Bruce Momjian2002-09-08
|
* Changes to documentation and the regression tests for the defaultBruce Momjian2002-09-07
| | | | | | NAMEDATALEN of 64. Kris Jurka
* Remove pgaccess from docs; not shipping it anymore.Bruce Momjian2002-09-07
|
* Allow pg_dumpall to work with previous releases again. Don't pass the -cPeter Eisentraut2002-09-07
| | | | | option down to pg_dump, where it's useless, and clarify the meaning of -c in the documentation.
* Make sure the pg_dump tar archiver can handle members larger than 2 GB, butPeter Eisentraut2002-09-06
| | | | | does not create members larger than allowed by the tar format. Also, fix the generation of the tar header to conform to POSIX.
* Fix another typo.Bruce Momjian2002-09-06
|
* Fix typo.Bruce Momjian2002-09-06
|
* Missed mention of PGPASSWORDFILE.Bruce Momjian2002-09-05
|
* Remove PGPASSWORDFILE and default to always trying $HOME/.pgpass.Bruce Momjian2002-09-05
| | | | | | Cleanup up memory allocation for $HOME in related psql places. Update mention of $HOME/.pgpass in the docs; add mention in pg_dumpall.
* Fill in section on table modification.Peter Eisentraut2002-09-05
|
* Brand 7.3. Ready for beta!Bruce Momjian2002-09-04
|
* Update new HISTORY file for 7.3!Bruce Momjian2002-09-04
|
* Arrange for the default permissions on a database to allow temp tableTom Lane2002-09-03
| | | | | | | creation to world, but disallow temp table creation in template1. Per latest round of pghackers discussion. I did not force initdb, but the permissions lockdown on template1 will not take effect unless you do one (or manually REVOKE TEMP ON DATABASE template1 FROM public).
* Fix SGML build failure.Bruce Momjian2002-09-03
|
* Documentation improvements.Tom Lane2002-09-03
|
* Code review and documentation updates for indisclustered patch.Tom Lane2002-09-03
|
* pg_on_connection_loss command for libpgtcl. Patch fromTom Lane2002-09-02
| | | | | | | | Gerhard Hintermayer, revised and documented by Tom Lane. This patch also fixes a 'must fix' bug: libpgtcl's LISTEN/NOTIFY support was broken by the recent changes to the PGnotify structure. Guess that change wasn't quite so safe as we thought.
* Fix obsolete description of PGnotify struct.Tom Lane2002-09-02
|
* Department of second thoughts: make checks for replacing a view slightlyTom Lane2002-09-02
| | | | | more flexible, and improve the error reporting. Also, add documentation for REPLACE RULE/VIEW.
* Fix broken markup.Tom Lane2002-09-02
|
* This patch fixes a minor inaccuracy in the documentation: NOT NULL isBruce Momjian2002-09-02
| | | | | | | | not synonymous with CHECK (xxx IS NOT NULL) -- for example, consider ALTER TABLE ADD PRIMARY KEY, which checks for 'NOT NULL', not a check constraint. Neil Conway
* I checked all the previous string handling errors and most of them wereBruce Momjian2002-09-02
| | | | | | | | | | | | | | | already fixed by You. However there were a few left and attached patch should fix the rest of them. I used StringInfo only in 2 places and both of them are inside debug ifdefs. Only performance penalty will come from using strlen() like all the other code does. I also modified some of the already patched parts by changing snprintf(buf, 2 * BUFSIZE, ... style lines to snprintf(buf, sizeof(buf), ... where buf is an array. Jukka Holappa
* Here's a doc patch for the new string functions recently committed --Bruce Momjian2002-09-02
| | | | | | | replace, split, and to_hex. The patch also moves encode and decode into alphabetical order (since everything else in the table was). Joe Conway
* Move pg_settings doc into the right section.Bruce Momjian2002-09-02
|
* Here is a documentation patch for the pg_settings virtual table. IfBruce Momjian2002-09-02
| | | | | | there are no objections, please apply. Joe Conway
* Add GUC variable to print original query to the server logs when thereBruce Momjian2002-09-02
| | | | | | is an error, warning, etc. Gavin Sherry
* Code review for HeapTupleHeader changes. Add version number to page headersTom Lane2002-09-02
| | | | | | | | | | (overlaying low byte of page size) and add HEAP_HASOID bit to t_infomask, per earlier discussion. Simplify scheme for overlaying fields in tuple header (no need for cmax to live in more than one place). Don't try to clear infomask status bits in tqual.c --- not safe to do it there. Don't try to force output table of a SELECT INTO to have OIDs, either. Get rid of unnecessarily complex three-state scheme for TupleDesc.tdhasoids, which has already caused one recent failure. Improve documentation.
* Add log_duration to GUC/postgresql.conf.Bruce Momjian2002-09-01
| | | | | Rename debug_print_query to log_statement and rename show_query_stats to show_statement_stats.
* plpgsql functions can return RECORD, per Neil Conway.Tom Lane2002-09-01
|
* Minor copy-editing.Tom Lane2002-09-01
|
* Remove mention of wal_files in a SHOW example.Bruce Momjian2002-09-01
|
* Code review for pg_locks feature. Make shmemoffset of PROCLOCK structsTom Lane2002-08-31
| | | | | | | | available (else there's no way to interpret the list links). Change pg_locks view to show transaction ID locks separately from ordinary relation locks. Avoid showing N duplicate rows when the same lock is held multiple times (seems unlikely that users care about exact hold count). Improve documentation.
* Updates to reflect availability of autocommit option.Tom Lane2002-08-30
|
* AUTOCOMMIT mode is now an available backend GUC variable; setting itTom Lane2002-08-30
| | | | | | | | | to false provides more SQL-spec-compliant behavior than we had before. I am not sure that setting it false is actually a good idea yet; there is a lot of client-side code that will probably be broken by turning autocommit off. But it's a start. Loosely based on a patch by David Van Wie.
* Add attisinherited column to pg_attribute; use it to guard againstTom Lane2002-08-30
| | | | | | column additions, deletions, and renames that would let a child table get out of sync with its parent. Patch by Alvaro Herrera, with some kibitzing by Tom Lane.
generated by cgit v1.2.3 (git 2.25.1) at 2025-06-27 06:44:19 +0000