Bruce Momjian
5b795bec59
No revoke on indexes any more
2000-04-10 01:35:44 +00:00
Bruce Momjian
f49cbb54f1
No more need to create groups manually.
2000-04-09 12:14:25 +00:00
Bruce Momjian
d888ca7c08
No grant on indexes.
2000-04-09 12:08:33 +00:00
Bruce Momjian
321eedd0bf
Document FSYNC in pg_options sgml file.
2000-04-08 23:12:01 +00:00
Tom Lane
607c6d25d7
Link already-existing COMMENT and REINDEX command docs into documentation.
2000-04-08 05:11:03 +00:00
Bruce Momjian
75b5915b43
update
2000-04-08 02:44:55 +00:00
Tom Lane
b99cdde0d7
Fix cross-references, update examples, copy-edit.
2000-04-08 02:39:02 +00:00
Thomas G. Lockhart
c264c4daeb
Add reference page for pg_ctl.
2000-04-08 02:16:26 +00:00
Bruce Momjian
124875e879
More man updates to fix bad tags
2000-04-07 19:20:48 +00:00
Bruce Momjian
28fb1c196b
Update create_rule manual page.
2000-04-07 19:17:51 +00:00
Bruce Momjian
0df916e096
Again update of rule manual page.
2000-04-07 17:37:24 +00:00
Bruce Momjian
592b69056d
Update rule examples
2000-04-07 17:35:08 +00:00
Bruce Momjian
d27a566583
Remove mention of INSTANCE rule system, because it is gone.
2000-04-07 17:23:11 +00:00
Thomas G. Lockhart
1b992b468b
Document new SET SEED command.
2000-04-07 13:31:18 +00:00
Bruce Momjian
7c6bac0071
Update vacuum to mention analyze
2000-04-05 21:51:11 +00:00
Bruce Momjian
30d4f58256
Remove FETCH syntax heading from MOVE manual page.
2000-04-04 19:42:36 +00:00
Bruce Momjian
ca6c98dbe1
Remove from FETCH manual page:
...
Once all rows are fetched, every other fetch access
returns no rows.
2000-04-04 19:29:18 +00:00
Tom Lane
c84ba6638e
Add a check to pg_dump to see whether backend is same version as pg_dump.
...
If not, abort by default. Abort can be prevented by using -i or
--ignore-version switch.
2000-04-04 05:22:46 +00:00
Tom Lane
dbc9346f75
Correct typo.
2000-03-31 17:45:32 +00:00
Tom Lane
58b4886004
CREATE AGGREGATE ref page claimed that a noise-word AS was allowed in
...
the syntax ... but gram.y doesn't think so.
2000-03-31 14:57:05 +00:00
Hiroshi Inoue
e854d3da54
*** empty log message ***
2000-03-31 08:16:33 +00:00
Thomas G. Lockhart
f43974f6f1
Include all information from the old man pages.
2000-03-31 06:17:52 +00:00
Thomas G. Lockhart
f38d2afa16
Document recent changes in syntax, including examples.
2000-03-31 03:20:17 +00:00
Thomas G. Lockhart
f05ac972c6
Fix markup for terminology.
2000-03-28 14:35:27 +00:00
Thomas G. Lockhart
39f69bc38f
Start updating for the v7.0 release.
...
Use "generic functions" for math and other routines.
Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".
2000-03-27 17:14:43 +00:00
Tom Lane
ee4dcf1478
Update/improve documentation about creating aggregate functions.
2000-03-26 19:45:21 +00:00
Peter Eisentraut
4579e68db2
Updated user's guide to match new psql's output format
...
Fixed bug in createdb/alternative location
2000-03-26 18:32:30 +00:00
Tom Lane
3871b69ba1
Improve descriptions of postmaster switches.
2000-03-26 07:04:54 +00:00
Bruce Momjian
be0204133c
Move LOCK terms down.
2000-03-24 03:57:06 +00:00
Bruce Momjian
853cf66176
Update HISTORY
2000-03-24 01:20:09 +00:00
Bruce Momjian
6d79d6027c
>> 5. empty define that results in an empty but terminated line ( ; )
...
easy (maybe dumb) fix for 5 in attachment define.patch
greetings, Andreas
2000-03-23 23:16:49 +00:00
Bruce Momjian
f8645018bc
Back out // compiler flag.
2000-03-23 22:25:36 +00:00
Bruce Momjian
4ddc50dffa
Hmm, absolute pathnames for the copy makes sense. I'll whip up that
...
patch in a second. Should be sufficent to just make sure the first
character is a '/', right?
Ross J. Reedstrom
2000-03-23 21:38:58 +00:00
Bruce Momjian
1d5df1547a
This patch corrects spelling, grammar and euphony for the psql reference
...
page for 7.0:
Oliver Elphick
2000-03-21 01:52:12 +00:00
Tom Lane
f945f46193
Modify lexing of multi-char operators per pghackers discussion around
...
16-Mar-00: trailing + or - is not part of the operator unless the operator
also contains characters not present in SQL92-defined operators. This
solves the 'X=-Y' problem without unduly constraining users' choice of
operator names --- in particular, no existing Postgres operator names
become invalid.
Also, remove processing of // comments, as agreed in the same thread.
2000-03-18 18:03:12 +00:00
Tom Lane
0e314d747e
Add safety check on expression nesting depth. Default value is set by
...
a config.h #define, and the runtime value can be controlled via SET.
2000-03-17 05:29:07 +00:00
Thomas G. Lockhart
1f3122e26d
Fix typo (introduced by xemacs markup normalization) in the syntax summary.
2000-03-16 14:39:30 +00:00
Tom Lane
1763a7c1ea
Tweak GROUP BY so that it will still accept result-column names, but only
...
after trying to resolve the item as an input-column name. This allows us
to be compliant with the SQL92 spec for queries that fall within the spec,
while still accepting the same out-of-spec queries as 6.5 did. You'll only
lose if there is an output column name that is the same as an input
column name, but doesn't refer to the same value. 7.0 will interpret
such a GROUP BY spec differently than 6.5 did. No way around that, because
6.5 was clearly not spec compliant.
2000-03-15 23:31:19 +00:00
Peter Eisentraut
1d75298176
Karel Zakr's revised patch to fix psql prompt for local host connections.
2000-03-11 13:56:24 +00:00
Peter Eisentraut
c75adac757
More fixes for psql ^C handling, especially during copy. Still doesn't
...
cope so well with copy to but that will have to wait for the next release.
Also added -X option to prevent reading .psqlrc startup file.
2000-03-01 21:10:05 +00:00
Tom Lane
80b7955d60
Correct bogus syntax in SET example.
2000-02-27 21:07:03 +00:00
Tom Lane
a7f85783fb
Update SELECT documentation to have a more thorough discussion
...
of LIMIT, and fix a few other glitches too.
2000-02-21 01:13:52 +00:00
Peter Eisentraut
bd8e071482
Forgot to include the documentation for \encoding ...
2000-02-20 14:29:21 +00:00
Thomas G. Lockhart
58a9ea9d80
Clean up markup so docs will compile.
2000-02-19 08:14:54 +00:00
Tom Lane
9c80cceb02
Update EXPLAIN documentation to reflect the fact that the
...
planner now produces two cost numbers instead of one.
2000-02-15 23:37:49 +00:00
Tom Lane
b1577a7c78
New cost model for planning, incorporating a penalty for random page
...
accesses versus sequential accesses, a (very crude) estimate of the
effects of caching on random page accesses, and cost to evaluate WHERE-
clause expressions. Export critical parameters for this model as SET
variables. Also, create SET variables for the planner's enable flags
(enable_seqscan, enable_indexscan, etc) so that these can be controlled
more conveniently than via PGOPTIONS.
Planner now estimates both startup cost (cost before retrieving
first tuple) and total cost of each path, so it can optimize queries
with LIMIT on a reasonable basis by interpolating between these costs.
Same facility is a win for EXISTS(...) subqueries and some other cases.
Redesign pathkey representation to achieve a major speedup in planning
(I saw as much as 5X on a 10-way join); also minor changes in planner
to reduce memory consumption by recycling discarded Path nodes and
not constructing unnecessary lists.
Minor cleanups to display more-plausible costs in some cases in
EXPLAIN output.
Initdb forced by change in interface to index cost estimation
functions.
2000-02-15 20:49:31 +00:00
Peter Eisentraut
9672d38f91
Adjusted psql echoing options (-a and -e)
2000-02-13 21:45:15 +00:00
Peter Eisentraut
2fb0ff0c5b
Default argument for createdb
...
Changed EXIT_ON_ERROR to ON_ERROR_STOP in psql
2000-02-10 20:08:58 +00:00
Peter Eisentraut
9ceb5d8a7b
Fixed psql double quoting of SQL ids
...
Fixed libpq printing functions
2000-02-07 23:10:11 +00:00
Thomas G. Lockhart
911fc20c41
Update with current summary information on pgadmin.
...
From pgadmin author on 99-12-24.
2000-02-02 16:19:54 +00:00