| Age | Commit message (Collapse) | Author |
|---|
|
|
|
as those for inherited columns; that is, it's no longer allowed for a child
table to not have a check constraint matching one that exists on a parent.
This satisfies the principle of least surprise (rows selected from the parent
will always appear to meet its check constraints) and eliminates some
longstanding bogosity in pg_dump, which formerly had to guess about whether
check constraints were really inherited or not.
The implementation involves adding conislocal and coninhcount columns to
pg_constraint (paralleling attislocal and attinhcount in pg_attribute)
and refactoring various ALTER TABLE actions to be more like those for
columns.
Alex Hunsaker, Nikhil Sontakke, Tom Lane
|
|
|
|
If this unbreaks buildfarm mastodon, apply everywhere.
|
|
began to realize that the input() function isn't used and printed warnings.
|
|
|
|
|
|
parameter. This fixes bug 4137 reported by Wojciech Strzalka, where a WAL
file is deleted too early when starting the recovery of a warm standby server.
Also add a sanity check in pg_standby so that it will refuse to delete anything
earlier than the file being restored, and improve the debug message in case
nothing is deleted.
Simon Riggs. Backpatch to 8.3, which is where %r was introduced.
|
|
something was wrong with that tab patch.
|
|
pg_wcsformat without changing pg_wcssize to match. Add some comments to
try to make that clearer, and make a couple other minor editorializations.
|
|
adjust source code to be more modular.
|
|
return 1, rather than error.
This was already the float8 behavior.
|
|
|
|
file/pipe output too if \pset columns' is set.
Bryce Nesbitt
|
|
|
|
specify the column names and types. Also simplifies the view.
Per comments from Tom.
|
|
instead of calling a bunch of individual functions.
This function can also be called directly, taking a PID as an argument, to
return only the data for a single PID.
|
|
than only 'off'.
|
|
Not clear that there's any observable bug at present from this omission,
but it seems like something to fix going forward.
|
|
to avoid the pain of manually renumbering them anytime we insert another
name in alphabetical order. An excellent idea from Alex Hunsaker and
NikhilS' inherited-constraints patch --- whether or not the rest of that
gets in, this should. Dunno why we never thought of it before.
|
|
standalone msvc build of libpq.
Hiroshi Saito
|
|
|
|
|
|
Hitoshi Harada
|
|
files were last loaded.
George Gensure
|
|
These changes assume that the varchar and xml data types are represented
the same as text. (I did not, however, accept the portions of the proposed
patch that wanted to assume bytea is the same as text --- tgl.)
Brendan Jurd
|
|
|
|
|
|
Joshua Drake.
|
|
UPDATE/DELETE forgot to teach ruleutils.c to display the alias.
Per bug #4141 from Mathias Seiler.
|
|
support multiple OUT arguments, though.)
Hannu Krosing
|
|
any hardcoding of those options. Along the way, reorder the expression used to
calculate RELSEG_SIZE to make it slightly clearer. For now wal_segsize is only
allowed to have a value of 1 on Windows - we can relax that when we get full
large file support in the backend.
|
|
Pavel Stehule
|
|
retrieved to be controlled through a GUC variable.
Robert Hell
|
|
let XLOG_BLCKSZ and XLOG_SEG_SIZE be set via configure. Per a proposal by
Mark Wong, though I thought it better to call the switches after "wal" rather
than "xlog".
|
|
|
|
Dickson S. Guedes
|
|
This has been the only documented and encouraged syntax for a long time, and
with extension facilities such as aliases being proposed, it is a good time to
clean up the legacy syntax a bit.
Author: Bernd Helmle <mailings@oopsware.de>
|
|
|
|
support for a nonsegmented mode from md.c. Per recent discussions, there
doesn't seem to be much value in a "never segment" option as opposed to
segmenting with a suitably large segment size. So instead provide a
configure-time switch to set the desired segment size in units of gigabytes.
While at it, expose a configure switch for BLCKSZ as well.
Zdenek Kotala
|
|
abbreviations. It doesn't conflict with any other abbreviation
so there seems no reason not to include it. Per a recent gripe.
|
|
it vary with BLCKSZ as before. This agrees with what the documentation says,
and avoids a regression test problem when BLCKSZ is larger than default.
Per recent discussion.
|
|
a user-supplied TID is out of range for the relation. This is needed to
preserve compatibility with our pre-8.3 behavior, and it is sensible anyway
since if the query were implemented by brute force rather than optimized
into a TidScan, the behavior for a non-existent TID would be zero rows out,
never an error. Per gripe from Gurjeet Singh.
|
|
makeFloatConst, and avoid "manual" construction of A_Const nodes in grammar
productions, in favor of using makeXXXConst subroutines.
|
|
The capability for changing language owners is new in 8.3, so that's how
far back this needs to be backpatched.
Per bug #4132 by Kirill Simonov.
|
|
Brendan Jurd, minor editorialization by me.
|
|
of functions.
|
|
test. We have seen some buildfarm failures that seem to be due to this
limit being unexpectedly exceeded when the machine is under load.
|
|
|
|
array's subscripts.
Pavel Stehule, some editorialization by me.
|
