| Age | Commit message (Collapse) | Author |
|---|
|
The syntax "su -c 'command' username" is not accepted by all versions of
su, for example not OpenBSD's. More portable is "su username -c
'command'". So change runtime.sgml to recommend that syntax. Also,
add a -D switch to the OpenBSD example script, for consistency with other
examples. Per Denis Lapshin and Gábor Hidvégi.
|
|
This allows easily splitting configuration into many files, deployed in a
directory.
Magnus Hagander, Greg Smith, Selena Deckelmann, reviewed by Noah Misch.
|
|
Produce a NOTICE when the label already exists, for consistency with other
CREATE IF NOT EXISTS commands. Also, fix the code so it produces something
more user-friendly than an index violation when the label already exists.
This not incidentally enables making a regression test that the previous
patch didn't make for fear of exposing an unpredictable OID in the results.
Also some wordsmithing on the documentation.
|
|
|
|
If the label is already in the enum the statement becomes a no-op.
This will reduce the pain that comes from our not allowing this
operation inside a transaction block.
Andrew Dunstan, reviewed by Tom Lane and Magnus Hagander.
|
|
|
|
Somewhere along the line, somebody decided to remove all trace of this
notation from the documentation text. It was still in the command syntax
synopses, or at least some of them, but with no indication what it meant.
This will not do, as evidenced by the confusion apparent in bug #7543;
even if the notation is now unnecessary, people will find it in legacy
SQL code and need to know what it does.
|
|
The documentation mentioned setting autovacuum_freeze_max_age to
"its maximum allowed value of a little less than two billion".
This led to a post asking about the exact maximum allowed value,
which is precisely two billion, not "a little less".
Based on question by Radovan Jablonovsky. Backpatch to 8.3.
|
|
Backpatch to 9.2.
|
|
Dan Scott
|
|
Etsuro Fujita
|
|
Shigeru Hanada
|
|
Also, set the release date to 2012-09-10, since we're pretty well
committed to that now.
|
|
with a socket directory mismatch with the new server.
Backpatch to 9.2.
|
|
|
|
When starting either an old or new postmaster, force it to place its Unix
socket in the current directory. This makes it even harder for accidental
connections to occur during pg_upgrade, and also works around some
scenarios where the default socket location isn't usable. (For example,
if the default location is something other than "/tmp", it might not exist
during "make check".)
When checking an already-running old postmaster, find out its actual socket
directory location from postmaster.pid, if possible. This dodges problems
with an old postmaster having a configured location different from the
default built into pg_upgrade's libpq. We can't find that out if the old
postmaster is pre-9.1, so also document how to cope with such scenarios
manually.
In support of this, centralize handling of the connection-related command
line options passed to pg_upgrade's subsidiary programs, such as pg_dump.
This should make future changes easier.
Bruce Momjian and Tom Lane
|
|
them.
|
|
|
|
are sometimes signed, sometimes unsigned.
|
|
Linking to other parts of the manual doesn't work when building the
standalone INSTALL document.
|
|
Jeff Janes
|
|
Extend xfunc.sgml's discussion of set-returning functions to show an
example of using LATERAL, and recommend that over putting SRFs in the
targetlist.
In passing, reword func.sgml's section on set-returning functions so
that it doesn't claim that the functions listed therein are all the
built-in set-returning functions. That hasn't been true for a long
time, and trying to make it so doesn't seem like it would be an
improvement. (Perhaps we should rename that section?)
Both per suggestions from Merlin Moncure.
|
|
Only warn when connecting to a newer server, since connecting to older
servers works pretty well nowadays. Also update the documentation a
little about current psql/server compatibility expectations.
|
|
checking an old running server.
|
|
Josh Kupershmidt
|
|
session, now that pg_terminate_backend() uses it.
Josh Kupershmidt
|
|
--enable-shared is about Plyton's configure, not ours.
|
|
|
|
queries on parent tables, per suggestion from Josh Berkus.
|
|
Jeff Janes
|
|
autovacuum activity.
Per report from Marc Mamin
|
|
The existing documentation in Linux Memory Overcommit seemed to
assume that PostgreSQL itself could never be the problem, or at
least it didn't tell you what to do about it.
Per discussion with Craig Ringer and Kevin Grittner.
|
|
As suggested by Etsuro Fujita, but with somewhat different wording.
|
|
|
|
|
|
|
|
percentage column before count column. Docs updated.
|
|
Lane's correction.
|
|
David E. Wheeler
|
|
Clarify the compatibility notes about EXTRACT() and about statistics
timing columns.
|
|
This is so that these sections will have stable HTML tags that one can
link to, rather than things like "AEN1902". Perhaps we should mount a
campaign to do this everywhere, but I've found myself pointing at
syntax.sgml subsections often enough to be sure it's useful here.
|
|
pg_restore.
|
|
Brad Davis
|
|
for CREATE TABLE LIKE ... INCLUDING INDEXES.
Per report from david.sahagian@emc.com
|
|
the same as \copy.
|
|
|
|
|
|
|
|
|
|
|
