| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Standard English uses "may", "can", and "might" in different ways:
may - permission, "You may borrow my rake."
can - ability, "I can lift that log."
might - possibility, "It might rain today."
Unfortunately, in conversational English, their use is often mixed, as
in, "You may use this variable to do X", when in fact, "can" is a better
choice. Similarly, "It may crash" is better stated, "It might crash".
|
| | |
|
| |
|
|
|
|
|
| |
reference pages documenting that these commands cannot be used within
a transaction block. Also make some minor improvements to the psql
reference page. Patch from Simon Riggs, minor editorialization by
myself.
|
| | |
|
| |
|
|
|
| |
blocking concurrent writes to the table. Greg Stark, with a little help
from Tom Lane.
|
| | |
|
| |
|
|
|
| |
symlink is kept for now for compatibility. To call single-user mode, use
postgres --single.
|
| |
|
|
| |
appears in the REINDEX ref page.
|
| | |
|
| |
|
|
|
|
|
| |
in the database. The old behavior (reindex system catalogs only) is now
available as REINDEX SYSTEM. I did not add the complementary REINDEX USER
case since there did not seem to be consensus for this, but it would be
trivial to add later. Per recent discussions.
|
| |
|
|
| |
8.0.X and HEAD.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
invalid (has the wrong magic number) until the build is entirely
complete. This turns out to cost no additional writes in the normal
case, since we were rewriting the metapage at the end of the process
anyway. In normal scenarios there's no real gain in security, because
a failed index build would roll back the transaction leaving an unused
index file, but for rebuilding shared system indexes this seems to add
some useful protection.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
now able to cope with assigning new relfilenode values to nailed-in-cache
indexes, so they can be reindexed using the fully crash-safe method. This
leaves only shared system indexes as special cases. Remove the 'index
deactivation' code, since it provides no useful protection in the shared-
index case. Require reindexing of shared indexes to be done in standalone
mode, but remove other restrictions on REINDEX. -P (IgnoreSystemIndexes)
now prevents using indexes for lookups, but does not disable index updates.
It is therefore safe to allow from PGOPTIONS. Upshot: reindexing system catalogs
can be done without a standalone backend for all cases except
shared catalogs.
|
| |
|
|
|
|
|
| |
makes a few more small improvements to runtime.sgml, and makes some SGML
conventions more consistent.
Neil Conway
|
| |
|
|
| |
discussion. (Still have some work to do editing the remainder.)
|
| | |
|
| | |
|
| |
|
|
| |
vague cross-references with real links.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
- more work from the SGML police
- some grammar improvements: rewriting a paragraph or two, replacing
contractions where (IMHO) appropriate
- fix missing utility commands in lock mode docs
- improve CLUSTER, REINDEX, SET SESSION AUTHORIZATION ref pages
Neil Conway
|
| |
|
|
| |
DATABASE/TABLE/INDEX is the proper order.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
capabilities of specifying time zones as intervals per SQL9x.
Put refentrytitle contents on the same line as the tag.
Otherwise, leading whitespace is propagated into the product, which
(at least) messes up the ToC layout.
Remove (some) docinfo tags containing dates. Best to omit if the dates
are not accurate; maybe use CVS dates instead or leave them out.
|
| | |
|
| |
|
|
| |
between Postgres and PostgreSQL.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Fix misspelling of disbursion to dispersion.
|
| | |
|
| |
|