| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Rearrange the documentation a bit now that array_agg and xmlagg have similar
semantics and issues.
best of Robert Haas, Jeff Davis, Peter Eisentraut
|
|
|
|
| |
I think this will fix current mingw buildfarm failures for pg_trgm.
|
|
|
|
|
|
| |
parse.[awk|pl] from the latest version of gram.y
Some small corrections to test suite.
|
|
|
|
|
| |
- FloatOnly: only used by NumericOnly, instead put the FloatOnly production into NumericOnly
- IntegerOnly: only used by NumericOnly and one ALTER TABLE rule, replacement SignedIconst is already used in several other places
|
|
|
|
|
|
|
| |
Add config parameter "sslverify" to control the verification. Default
is to do full verification.
Clean up some old SSL code that never really worked.
|
|
|
|
|
|
|
|
|
|
|
| |
operator. The result depends only on the two input operators and the proof
direction (imply or refute), so it's easy to cache. This provides a very
large savings in cases such as Sergey Konoplev's long NOT-IN-list example,
where predtest spends all its time repeatedly figuring out that the same pair
of operators cannot be used to prove anything. (But of course the O(N^2)
behavior still catches up with you eventually.) I'm not convinced it buys
a whole lot when constraint_exclusion isn't turned on, but it's not a lot
of added code so we might as well cache all the time.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
AND, OR, or equivalent clauses: if there are too many (more than 100) just
exit without proving anything. This ensures that we don't spend O(N^2) time
trying (and most likely failing) to prove anything about very long IN lists
and similar cases.
Also, install a couple of CHECK_FOR_INTERRUPTS calls to ensure that a long
proof attempt can be interrupted.
Per gripe from Sergey Konoplev.
Back-patch the whole patch to 8.2 and just the CHECK_FOR_INTERRUPTS addition
to 8.1. (The rest of the patch doesn't apply cleanly, and since 8.1 doesn't
show the complained-of behavior anyway, it doesn't seem necessary to work
hard on it.)
|
|
|
|
| |
Per note from Devrim Gunduz
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
function as a special case.
This version still has the suspicious behavior of returning null for an
empty array (rather than zero), but this may need a wholesale revision of
empty array behavior, currently under discussion.
Jim Nasby, Robert Haas, Peter Eisentraut
|
|
|
|
|
|
|
| |
autovacuum worker sending SIGUSR1 signal to wrong process, per Zou Yong's
report.
Backpatch to 8.3.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
in "postgres_verbose" intervalstyle, and the equally arbitrary decision to
show at least two fractional-seconds digits in most other datetime display
styles. This results in some minor changes in the expected regression test
outputs.
Also, coalesce a lot of repetitive code in datetime.c into subroutines,
for clarity and ease of maintenance. In particular this roughly halves
the number of #ifdef HAVE_INT64_TIMESTAMP segments.
Ron Mayer, with some additional kibitzing from Tom Lane
|
|
|
|
|
|
|
| |
translated_vars list get updated when pulling up an appendrel member. It's
not clear that this really matters at present, since relatively little gets
done with the outputs of an appendrel child relation; but it probably will
come back to bite us sometime if we leave them with the wrong values.
|
|
|
|
|
|
|
|
|
|
|
| |
we extended the appendrel mechanism to support UNION ALL optimization. The
reason nobody noticed was that we are not actually using attr_needed data for
appendrel children; hence it seems more reasonable to rip it out than fix it.
Back-patch to 8.2 because an Assert failure is possible in corner cases.
Per examination of an example from Jim Nasby.
In HEAD, also get rid of AppendRelInfo.col_mappings, which is quite inadequate
to represent UNION ALL situations; depend entirely on translated_vars instead.
|
|
|
|
|
|
|
| |
up a SSL connection, but psql is compiled without support for it.
Not a really realistic use-case, but the patch also cuts down on
the number of places with #ifdef's...
|
| |
|
|
|
|
|
|
| |
"base/11517/3767_fsm", instead of symbolic names like "1663/11517/3767/1",
per Alvaro's suggestion. I didn't change the messages in the higher-level
index, heap and FSM routines, though, where the fork is implicit.
|
|
|
|
| |
Adapted regression test files accordingly.
|
|
|
|
| |
non-null-terminated input. Per discussion with ITAGAKI Takahiro.
|
|
|
|
|
|
|
|
| |
specifically, we can input either the "format with designators" or the
"alternative format", and we can output the former when IntervalStyle is set
to iso_8601.
Ron Mayer
|
| |
|
|
|
|
|
|
| |
the length of a UTF8 character with pg_mblen (wrong if DB encoding isn't
UTF8), and the latter was blithely assuming that a static buffer would somehow
revert to all zeroes for each use.
|
| |
|
|
|
|
|
|
|
|
|
| |
different locales. This is just syntactical sweetener over --lc-collate and
--lc-ctype. Per discussion.
While at it, properly document --lc-ctype and --lc-collate in SGML docs,
which apparently were forgotten (or purposefully ommited?) when they were
created.
|
|
|
|
| |
is NULL), so remove some useless tests for the case.
|
|
|
|
| |
VACUUM reset them to false rather than trying to clean 'em up during DROP.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
("there might be triggers") rather than an exact count. This is necessary
catalog infrastructure for the upcoming patch to reduce the strength of
locking needed for trigger addition/removal. Split out and committed
separately for ease of reviewing/testing.
In passing, also get rid of the unused pg_class columns relukeys, relfkeys,
and relrefs, which haven't been maintained in many years and now have no
chance of ever being maintained (because of wishing to avoid locking).
Simon Riggs
|
|
|
|
|
|
|
| |
If the latter doesn't exist, automatically recreate it. (We don't do
this for pg_xlog, though, per discussion.)
Jonah Harris
|
|
|
|
|
|
|
|
|
|
| |
from DateStyle, and create a new interval style that produces output matching
the SQL standard (at least for interval values that fall within the standard's
restrictions). IntervalStyle is also used to resolve the conflict between the
standard and traditional Postgres rules for interpreting negative interval
input.
Ron Mayer
|
|
|
|
|
| |
it behaves correctly for a leading minus sign, zero year value, and
nonzero month value. Per discussion with Ron Mayer.
|
|
|
|
|
|
| |
as much of it as lives in its default tablespace) to a new tablespace.
Guillaume Lelarge, with some help from Bernd Helmle and Tom Lane
|
|
|
|
|
|
|
| |
(but not locked, as that would risk deadlocks). Also, make it work in a small
ring of buffers to avoid having bulk inserts trash the whole buffer arena.
Robert Haas, after an idea of Simon Riggs'.
|
|
|
|
|
| |
if their source or target types match the pattern (using the same definition
of "match" as \dT does). Per recent discussion.
|
|
|
|
|
| |
index column numbers needs to handle the case where you have more than
one scankey on the same index column. toast_fetch_datum_slice() needs it.
|
| |
|
|
|
|
| |
to only apply if present Oid is invalid, per second thought from TGL
|
|
|
|
| |
from KaiGai Kohei
|
| |
|
|
|
|
|
|
| |
Hopefully this will forestall future confusion about their roles.
Jonah Harris
|
| |
|
|
|
|
| |
Jonah Harris
|
|
|
|
|
| |
the proc->argnames array has to be initialized to zero immediately on creation,
since the error recovery path will try to free its elements.
|
|
|
|
| |
Author: Robert Haas <robertmhaas@gmail.com>
|
| |
|
|
|
|
|
| |
almost certainly represents user error. Per a gripe from Sebastian Böhm
and subsequent discussion.
|
|
|
|
| |
code beautification.
|
| |
|
|
|
|
|
|
|
| |
data type. This patch takes the approach of allowing an optional hyphen after
each group of four hex digits.
Author: Robert Haas <robertmhaas@gmail.com>
|
|
|
|
| |
stable not immutable, since it depends on system catalog contents.
|