| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
Commit 453a5d91d49e4d35054f92785d830df4067e10c1 made it available to the
src/test/regress build of pg_regress, but all pg_regress builds need the
same treatment. Patch 9.2 through 8.4; in 9.3 and later, pg_regress
gets pqsignal() via libpgport.
|
|
|
|
|
|
|
| |
Commit 4318daecc959886d001a6e79c6ea853e8b1dfb4b broke it. The change in
sub-second precision at extreme dates is normal. The inconsistent
truncation vs. rounding is essentially a bug, albeit a longstanding one.
Back-patch to 8.4, like the causative commit.
|
|
|
|
|
|
|
|
|
| |
This was not changed in HEAD, but will be done later as part of a
pgindent run. Future pgindent runs will also do this.
Report by Tom Lane
Backpatch through all supported branches, but not HEAD
|
|
|
|
|
|
|
| |
Patches by Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>
Conflicts:
src/interfaces/ecpg/test/expected/preproc-outofscope.c
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Many server functions use the MAXDATELEN constant to size a buffer for
parsing or displaying a datetime value. It was much too small for the
longest possible interval output and slightly too small for certain
valid timestamp input, particularly input with a long timezone name.
The long input was rejected needlessly; the long output caused
interval_out() to overrun its buffer. ECPG's pgtypes library has a copy
of the vulnerable functions, which bore the same vulnerabilities along
with some of its own. In contrast to the server, certain long inputs
caused stack overflow rather than failing cleanly. Back-patch to 8.4
(all supported versions).
Reported by Daniel Schüssler, reviewed by Tom Lane.
Security: CVE-2014-0063
|
|
|
|
|
|
|
|
| |
While working on most platforms the old way sometimes created alignment
problems. This should fix it. Also the regresion tests were updated to test for
the reported case.
Report and fix by MauMau <maumau307@gmail.com>
|
| |
|
|
|
|
|
| |
There are cases where the day of year value in struct tm is used, but it never
got calculated. Problem found by Coverity scan.
|
|
|
|
| |
With a unique counter being added anyway, there is no need anymore to have the variable name listed, too.
|
| |
|
|
|
|
|
|
| |
Per recommendation from Peter. Neither choice is bulletproof, but this
is the existing style and it does help prevent unexpected environment
variable substitution.
|
|
|
|
|
|
| |
Apparently there is no buildfarm critter exercising this case after all,
because it fails in several places. With this patch, build, install,
check-world, and installcheck-world pass for me on OS X.
|
|
|
|
|
| |
Also refactor things a little bit so that the same methods for setting
test locale and encoding can be used everywhere.
|
|
|
|
| |
Backport to 9.0, we're not supporting this compiler on earlier releases.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Recent releases had a check on rel->rd_refcnt in heap_drop_with_catalog,
but failed to cover the possibility of pending trigger events at DROP time.
(Before 8.4 we didn't even check the refcnt.) When the trigger events were
eventually fired, you'd get "could not open relation with OID nnn" errors,
as in recent report from strk. Better to throw a suitable error when the
DROP is attempted.
Also add a similar check in DROP INDEX.
Back-patch to all supported branches.
|
|
|
|
| |
array dimension.
|
| |
|
|
|
|
| |
release 8.4 - earlier releases would require more changes and it's not worth the trouble.
|
| |
|
|
|
|
|
|
|
| |
The trick is to not try to build executables directly from .c files,
but to always build the intermediate .o files. For obscure reasons,
Darwin's version of gcc will leave debug cruft behind in the first
case but not the second. Per complaint from Robert Haas.
|
| |
|
|
|
|
|
| |
Fix overly-enthusiastic ignores, as identified by
git ls-files -i --exclude-standard
|
|
|
|
| |
Backpatch to 8.2 as that's how far the structure looks the same.
|
| |
|
|
|
|
| |
at end of files.
|
| |
|
|
|
|
| |
Per buildfarm, again.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
linking both executables and shared libraries, and we add on LDFLAGS_EX when
linking executables or LDFLAGS_SL when linking shared libraries. This
provides a significantly cleaner way of dealing with link-time switches than
the former behavior. Also, make sure that the various platform-specific
%.so: %.o rules incorporate LDFLAGS and LDFLAGS_SL; most of them missed that
before. (I did not add these variables for the platforms that invoke $(LD)
directly, however. It's not clear if we can do that safely, since for the
most part we assume these variables use CC command-line syntax.)
Per gripe from Aaron Swenson and subsequent investigation.
|
|
|
|
|
|
|
| |
While the values were correctly returned they were not moved into C variables
as they should be.
Closes: #5489
|
|
|
|
| |
files instead of relative ones which break vpath builds.
|
|
|
|
| |
ecpglib.
|
|
|
|
|
| |
commandline option "-i". This change fixes this and adds a test case. It also
honors #include_next, although this is probably never used for embedded SQL.
|
|
|
|
| |
these definitions unique, too. It used to use the linenumber but in the rare case of two definitions in one line this was not unique.
|
|
|
|
| |
error sqlstate. This change makes it return a correct value..
|
| |
|
|
|
|
|
| |
regession test output, and update pgindent script to avoid them in the
future.
|
| |
|
|
|
|
| |
By Zoltán Böszörményi
|
|
|
|
| |
just trying to figure out the minimal amount of defines needed.
|
|
|
|
| |
<float.h>' as well.
|
|
|
|
| |
fixing yet another incorrect log output.
|
|
|
|
|
|
| |
test failures on some architectures.
By Zoltán Böszörményi.
|
|
|
|
|
|
| |
making it OS independant.
Patch done by Zoltán Böszörményi.
|
|
|
|
|
|
|
|
| |
order
so regression testing is possible,
by Zoltan Boszormenyi
|
|
|
|
| |
of my commit.
|
|
|
|
| |
cursor support to native mode.
|
|
|
|
| |
auto-prepare mode if the connection is closed and re-opened and the previously prepared query is issued again.
|
|
|
|
| |
[OUTPUT] statement to ecpg.
|
|
|
|
|
|
| |
For non-SQL3 types ecpg used to return -Oid. This will break if there are
enough Oids to fill the namespace. Therefore we play it safe and return 0 if
there is no Oid->SQL3 tyoe mapping available.
|