1
0
mirror of https://github.com/postgres/postgres.git synced 2025-07-30 11:03:19 +03:00
Commit Graph

221 Commits

Author SHA1 Message Date
585c967720 Change resjunk to a boolean. 1999-05-17 17:03:51 +00:00
fc08814e00 Rename explain's "size" to "rows". 1999-04-23 21:23:49 +00:00
00a4196139 Add res checking to libpq examples, from Dan Merillat. 1999-04-17 17:18:41 +00:00
630ed05063 Correct documentation of CREATE OPERATOR. 1999-04-15 00:09:00 +00:00
e57c34c012 Add -E option 1999-03-30 05:14:03 +00:00
0d01fd4e19 Add EXCEPT/INTERSECT doc changes. 1999-03-19 02:41:41 +00:00
58118db39d Add new postgres -O option to allow system table structure changes. 1999-03-17 22:53:31 +00:00
a564d2bf0f geqo now at 11 tables 1999-03-07 12:00:40 +00:00
1ed5cbbfd8 Final optimizer cleanups. 1999-02-22 05:26:58 +00:00
1efa3f4228 Document postmaster's -N switch. 1999-02-21 03:17:31 +00:00
b4e7510e09 Enable bushy and right-hand queries by default. 1999-02-18 06:01:11 +00:00
65ccd1039a Enable bushy plans by default. 1999-02-18 05:26:34 +00:00
61aa825876 Optimizer rename. 1999-02-14 04:57:02 +00:00
afd57dbb3a Changed manpages for create_rule/drop_rule to the semantics
of the rule system of v6.4 and descendants.

Jan
1999-02-07 22:10:10 +00:00
f1b7823471 Make GEQO use dependent on table and index count. 1999-02-02 20:30:18 +00:00
8e958b8a38 Fix create_rule is->as. 1999-02-02 17:46:17 +00:00
4390b0bfbe Add TEMP tables/indexes. Add COPY pfree(). Other cleanups. 1999-02-02 03:45:56 +00:00
289a826dab Here is a new version of my patch for allowing pg_dump to DROP schema
elements prior to CREATEing new ones.  It is under control of the -c
command line option (with the default being status quo).

The DROP TRIGGER portion still needs implementation.  Anyone able to
help clarify what exactly the CREATE TRIGGER portion does so I can fix
this?

Again, I have tried this with tables/indexes/sequences, but do not
have other schema elements in my database.  As a result, I am not 100%
convinced that I got the syntax correct in all cases (but think I did,
nonetheless).  If anyone can check the other cases, I'd appreciate it.

Cheers,
Brook

[I added manual page and sgml additions for the new -c option.]
1999-01-21 22:53:37 +00:00
b693983004 New ecpg man page. 1998-12-13 03:53:56 +00:00
ba74ce73bb Fix from Tom Lane for pg_shadow in pg_upgrade 1998-10-25 02:47:38 +00:00
aa3a1f46df New PGQUERY_LIMIT environment variable, and doc changes. 1998-10-14 05:31:50 +00:00
8cec4cf91b New QUERY_LIMIT set command. 1998-10-14 05:10:12 +00:00
39f2ec55d7 No more pgintro. 1998-10-14 02:54:39 +00:00
103959a3df No more pgbuiltin. 1998-10-14 02:36:45 +00:00
af5d6b4ef6 I'm too short of time to make these man pages look like the
newly-updated SGML reference pages, so I just inserted a comment that they
are obsolete.  If you want to transcribe the newer info into these pages,
be my guest.
1998-10-08 01:16:18 +00:00
252568dc11 Update pg_dump sgml and manuals to remove rule restriction. 1998-10-07 02:49:10 +00:00
fe9bf46bd4 Add mention of the new "suppress double quotes" command line option "-n". 1998-10-06 05:05:48 +00:00
b7ed6f8512 Hi all
Is it too late to add a feature to pg_dump for 6.4??

I just spent most of the day learning pg_dump and modifing it so it
would
dump views also.

This is the first time I have ever contributed any code changes, so I'm
not sure of how to submit it.

The diff's and a readme as a tgz file are attached.

Thanks
Terry Mackintosh <terry@terrym.com>          http://www.terrym.com
1998-10-06 03:09:02 +00:00
2da5e598e6 Obsolete information completely superceded by the sgml sources.
These weren't really "man page"-ish anyway, and I've verified that
 all information in them has moved to the newer sources.
1998-10-02 16:46:34 +00:00
2913d6557e Preserver pg_log and pg_variable in upgrade. Cleanups. 1998-08-31 04:32:18 +00:00
6c4982851a From: Massimo Dal Zotto <dz@cs.unitn.it> 1998-08-30 21:05:27 +00:00
3b7d13a6b0 Make old db directory configurable. 1998-08-30 13:14:00 +00:00
2739315a80 Update man pages. 1998-08-30 05:25:47 +00:00
c870be6590 New pg_upgrade command. 1998-08-30 05:06:54 +00:00
0a15090dba man pages cleanup 1998-08-24 01:51:20 +00:00
212f7bdfe3 Patch to allow createuser options from the command line. 1998-08-22 05:19:35 +00:00
7971539020 heap_fetch requires buffer pointer, must be released; heap_getnext
no longer returns buffer pointer, can be gotten from scan;
	descriptor; bootstrap can create multi-key indexes;
pg_procname index now is multi-key index; oidint2, oidint4, oidname
are gone (must be removed from regression tests); use System Cache
rather than sequential scan in many places; heap_modifytuple no
longer takes buffer parameter; remove unused buffer parameter in
a few other functions; oid8 is not index-able; remove some use of
single-character variable names; cleanup Buffer variables usage
and scan descriptor looping; cleaned up allocation and freeing of
tuples; 18k lines of diff;
1998-08-19 02:04:17 +00:00
9e1d532027 This README only mentions nroff problems with page.5, which has been
removed from the man pages and put into the new sgml docs.
1998-08-15 16:39:21 +00:00
4ab9ac79ba Include a sentence in the top pointing to the new docs.
pgbuiltin.3 is obsolete for sure, and libpq.3 can become so since the
 size and scope of this man page is not appropriate in a man page format.
1998-08-15 16:36:22 +00:00
b55a020aca Converted to page.sgml. Not needed in a man page. 1998-08-15 13:01:26 +00:00
223fa7ff4a Information moved to sgml source files.
The "Oracle compatibility" page should have always been in with functions
 anyway. The BKI information is not really appropriate for a man page.
1998-08-15 07:03:59 +00:00
ffb120ecc6 Add new \w write command to psql. 1998-08-10 20:31:42 +00:00
e6311b4ad0 The attached patch implements some changes that were discussed a
couple weeks ago on the hackers and interfaces lists:

1. When the backend sends a NOTICE message and closes the connection
   (typically, because it was told to by the postmaster after
   another backend coredumped), libpq will now print the notice
   and close the connection cleanly.  Formerly, the frontend app
   would usually terminate ungracefully due to a SIGPIPE.  (I am
   not sure if 6.3.2 behaved that way, but the current cvs sources
   do...)

2. libpq's various printouts to stderr are now fed through a single
   "notice processor" routine, which can be overridden by the
   application to direct notices someplace else.  This should ease
   porting libpq to Windows.

I also noticed and fixed a problem in PQprint: when sending output
to a pager subprocess, it would disable SIGPIPE in case the pager
terminates early (this is good) --- but afterwards it reset SIGPIPE
to SIG_DFL, rather than restoring the application's prior setting
(bad).

			regards, tom lane
1998-08-09 02:59:33 +00:00
7db9ea5c1e EXPLAIN VERBOSE prints the plan, and now pretty-prints the plan to
the postmaster log file.
1998-08-04 15:00:28 +00:00
21ad8695ca Fix typo in man pages. 1998-08-03 05:54:30 +00:00
d8d0aa019b Update psql help syntax to remove <> and uppercaese keywords. 1998-07-25 00:17:30 +00:00
8e2647a145 Add mention of actual SQL command to create*/destroy* commands. 1998-07-24 16:44:04 +00:00
22616fdc5d Add mention of SQL commands to create/destroy man pages. 1998-07-24 16:36:56 +00:00
253a294e9f Add mention of psql and template1 to create*, destroy* command
manual pages.
1998-07-24 16:10:19 +00:00
916710fc91 pg_dump -z has gotten rather thoroughly broken in the last couple
of days --- it was emitting stuff like
	REVOKE ALL on 'table' from PUBLIC; GRANT ALL on "table" to
	"Public"; neither of which work.  While I was at it I
cleaned up a few other things:

* \connect commands are issued only in -z mode.  In this way,
reloading a pg_dump script made without -z will generate a simple
database wholly owned by the invoking user, rather than a mishmash
of tables owned by various people but lacking in access rights.
(Analogy: cp versus cp -p.)

* \connect commands are issued just before COPY FROM stdin commands;
without this, reloading a database containing non-world-writable
tables tended to fail because the COPY was not necessarily attempted
as the table owner.

* Redundant \connect commands are suppressed (each one costs a
backend launch, so...).

* Man page updated (-z wasn't ever documented).

The first two items were discussed in a pgsql-hackers thread around
6 May 98 ("An item for the TODO list: pg_dump and multiple table
owners") but no one had bothered to deal with 'em yet.

			regards, tom lane
1998-07-19 05:24:51 +00:00