| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
by splitting it into three functions with better-defined behaviors.
Zdenek Kotala
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
from COMMITTED to SUBCOMMITTED during recovery. This wasn't previously
possible, but it is now due to the recent changes on clog commit protocol for
subtransactions.
Simon Riggs
|
|
|
|
|
|
|
|
| |
to dump sequence values cope with sequences outside the search path and/or
having names that need quoting. No back-patch needed because these are new
problems in 8.4.
Kris Jurka (also a little bit of code beautification by tgl)
|
|
|
|
| |
longstanding note in the source that this patch removes.
|
|
|
|
| |
Brendan Jurd
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
upon requests from backends, rather than on a fixed 500msec cycle. (There's
still throttling logic to ensure it writes no more often than once per
500msec, though.) This should result in a significant reduction in stats file
write traffic in typical scenarios where the stats are demanded only
infrequently.
This approach also means that the former difficulty with changing
stats_temp_directory on-the-fly has gone away, so remove the caution about
that as well as the thrashing we did to minimize the trouble window.
In passing, also fix pgstat_report_stat() so that we will send a stats
message if we have function call stats but not table stats to report;
this fixes a bug in the recent patch to support function-call stats.
Martin Pihlak
|
|
|
|
|
|
|
|
|
| |
allowed different processes to have different addresses for the shmem segment
in quite a long time, but there were still a few places left that used the
old coding convention. Clean them up to reduce confusion and improve the
compiler's ability to detect pointer type mismatches.
Kris Jurka
|
|
|
|
|
|
|
|
|
|
|
| |
and heap_deformtuple in favor of the newer functions heap_form_tuple et al
(which do the same things but use bool control flags instead of arbitrary
char values). Eliminate the former duplicate coding of these functions,
reducing the deprecated functions to mere wrappers around the newer ones.
We can't get rid of them entirely because add-on modules probably still
contain many instances of the old coding style.
Kris Jurka
|
| |
|