1
0
mirror of https://github.com/postgres/postgres.git synced 2025-06-10 09:21:54 +03:00
Commit Graph

8677 Commits

Author SHA1 Message Date
2ce4b4cda1 Update obsolete statement that indexes can have only 7 columns.
Reorganize description of index features for more clarity.
2000-03-26 19:47:17 +00:00
ee4dcf1478 Update/improve documentation about creating aggregate functions. 2000-03-26 19:45:21 +00:00
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
3871b69ba1 Improve descriptions of postmaster switches. 2000-03-26 07:04:54 +00:00
a7b8de40db Rearrange steps in recommended install procedure to something more
reasonable, ie configure and build first, then optionally run regress
tests using new parallel (non-installed) test method, and only then
backup and kill old installation.
2000-03-26 07:03:38 +00:00
5521658e30 Add description of new parallel regression testing method; update
procedure to cover running either test script; other minor improvements.
2000-03-26 07:01:19 +00:00
4e9c534766 Update descriptions of configure's options, and document how to specify
multiple directories for --with-includes or --with-libraries.
2000-03-26 06:59:31 +00:00
7c81a130a4 Fix erroneous claim that 'postmaster -S' leaves the postmaster running
in the foreground --- in fact, it auto-detaches.
2000-03-26 06:58:17 +00:00
ba834d6425 Update initdb flags. 2000-03-26 03:40:37 +00:00
cb3b3eda9a In PQnotifies discussion, reference PQsocket as function needed to get
file descriptor number for select().  (Suggestion from Ken Wright.)
2000-03-26 01:00:17 +00:00
be0204133c Move LOCK terms down. 2000-03-24 03:57:06 +00:00
0edcee3459 Fold PQsetenv working state into PGconn, rather than trying to maintain
it in a separate object.  There's no value in keeping the state separate,
and it creates dangling-pointer problems.  Also, remove PQsetenv routines
from public API, until and unless they are redesigned to have a safer
interface.  Since they were never part of the documented API before 7.0,
it's unlikely that anyone is calling them.
2000-03-24 01:39:55 +00:00
853cf66176 Update HISTORY 2000-03-24 01:20:09 +00:00
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
f8645018bc Back out // compiler flag. 2000-03-23 22:25:36 +00:00
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
90cb4c89df Update history/sgml. 2000-03-23 15:09:56 +00:00
b508136d81 Update HISTORY file for 7.0. 2000-03-23 06:30:58 +00:00
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
8fc97e8276 Sorry, I have read the misspelling 'coersion' one time too many. 2000-03-20 04:22:11 +00:00
b9a990d8a8 Add exp(), ln(), and some other functions to numeric-functions table. 2000-03-20 04:20:52 +00:00
339fe3c4cb Add note that ':' and ';' operators are deprecated. 2000-03-20 04:19:47 +00:00
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
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
1f3122e26d Fix typo (introduced by xemacs markup normalization) in the syntax summary. 2000-03-16 14:39:30 +00:00
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
795878d2dd Fix " to ' on lobj docs. 2000-03-15 17:07:41 +00:00
ce543b2121 Write up new TIME WITH TIME ZONE type. 2000-03-14 22:52:53 +00:00
1d75298176 Karel Zakr's revised patch to fix psql prompt for local host connections. 2000-03-11 13:56:24 +00:00
370186e807 Update libpq documentation for PQconndefaults() change. Add section
about thread-safeness of the library.
2000-03-11 03:09:28 +00:00
0f17e3faab Okay, this time I *really* added the bug reporting guidelines. 2000-03-10 22:32:59 +00:00
16ace63c6b Added bug reporting guidelines
Some corrections in installation procedure
2000-03-09 12:00:08 +00:00
3a81a1a462 *** empty log message *** 2000-03-03 09:56:03 +00:00
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
80b7955d60 Correct bogus syntax in SET example. 2000-02-27 21:07:03 +00:00
020be62dea Well, here's the first pass on regression
tests for the Foreign Key support in 7.0 which
was made against a CVS copy from this
afternoon.

This modifies
 src/test/regress/sql/run_check.tests
 src/test/regress/sql/alter_table.sql
 src/test/regress/expected/alter_table.out
 src/test/regress/sql/foreign_key.sql
 src/test/regress/expected/foreign_key.out

sszabo@bigpanda.co
2000-02-22 20:58:31 +00:00
f72aad5678 Update discussion of aggregate syntax to mention ALL. 2000-02-21 01:20:41 +00:00
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
bd8e071482 Forgot to include the documentation for \encoding ... 2000-02-20 14:29:21 +00:00
58a9ea9d80 Clean up markup so docs will compile. 2000-02-19 08:14:54 +00:00
ac324075de Update for new Irix info. 2000-02-19 08:14:33 +00:00
598ea2c359 Finish repairing 6.5's problems with r-tree indexes: create appropriate
selectivity functions and make the r-tree operators use them.  The
estimation functions themselves are just stubs, unfortunately, but
perhaps someday someone will make them compute realistic estimates.
Change pg_am so that the optimizer can reliably tell the difference
between ordered and unordered indexes --- before it would think that
an r-tree index can be scanned in '<<' order, which is not right AFAIK.
Repair broken negator links for network_sup and related ops.
Initdb forced.  This might be my last initdb force for 7.0 ... hope so
anyway ...
2000-02-17 03:40:02 +00:00
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
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
f0c66e539b Fix extraneous ending tag on libpq.sgml.
Renormalize query.sgml and fix indenting.
2000-02-15 03:57:02 +00:00
9672d38f91 Adjusted psql echoing options (-a and -e) 2000-02-13 21:45:15 +00:00
2fb0ff0c5b Default argument for createdb
Changed EXIT_ON_ERROR to ON_ERROR_STOP in psql
2000-02-10 20:08:58 +00:00
5d93742b8d You will need to copy "config.h.win32" to "config.h" in the include
directory.

I think this patch to the docs should be what is needed.

 Magnus Hagander
2000-02-10 15:47:58 +00:00
b1b8fc813f Update length to 31. 2000-02-10 04:08:25 +00:00
394af52795 I'm sending patch with new version of to_char numbers formatting.
The PostgreSQL's to_char() is very compatible with Oracle's to_char
 now. I hope that to_char's 3000 rows of source is without bugs, but
 will good if anyone test it, for me it works very well :-)


                                                        Karel

----------------------------------------------------------------------
Karel Zak <zakkr@zf.jcu.cz>              http://home.zf.jcu.cz/~zakkr/
2000-02-08 15:57:01 +00:00