| Commit message (Collapse) | Author | Age |
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
results to contain uninitialized, unpredictable values. While this was okay
as far as the datatypes themselves were concerned, it's a problem for the
parser because occurrences of the "same" literal might not be recognized as
equal by datumIsEqual (and hence not by equal()). It seems sufficient to fix
this in the input functions since the only critical use of equal() is in the
parser's comparisons of ORDER BY and DISTINCT expressions.
Per a trouble report from Marc Cousin.
Patch all the way back. Interestingly, array_in did not have the bug before
8.2, which may explain why the issue went unnoticed for so long.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The places that did, eg,
(statbuf.st_mode & S_IFMT) == S_IFDIR
were correct, but there is no good reason not to use S_ISDIR() instead,
especially when that's what the other 90% of our code does. The places
that did, eg,
(statbuf.st_mode & S_IFDIR)
were flat out *wrong* and would fail in various platform-specific ways,
eg a symlink could be mistaken for a regular file on most Unixen.
The actual impact of this is probably small, since the problem cases
seem to always involve symlinks or sockets, which are unlikely to be
found in the directories that PG code might be scanning. But it's
clearly trouble waiting to happen, so patch all the way back anyway.
(There seem to be no occurrences of the mistake in 7.4.)
|
|
|
|
| |
a NULL value. Per bug #4058.
|
|
|
|
|
|
|
|
|
| |
failed to cover all the ways in which a connection can be initiated in dblink.
Plug the remaining holes. Also, disallow transient connections in functions
for which that feature makes no sense (because they are only sensible as
part of a sequence of operations on the same connection). Joe Conway
Security: CVE-2007-6601
|
|
|
|
|
|
| |
test of that.
Patch by Bruce Momjian <bruce@momjian.us>
|
|
|
|
|
| |
per suggestion from Tom Lane. This fixes crash-bug reported by Stefan
Schwarzer.
|
|
|
|
|
|
|
| |
function didn't return correct result for word position greate than
limit.
Per report from Stuart Bishop <stuart@stuartbishop.net>
|
| |
|
|
|
|
|
|
|
|
| |
padded encryption scheme. Formerly it would try to access res[(unsigned) -1],
which resulted in core dumps on 64-bit machines, and was certainly trouble
waiting to happen on 32-bit machines (though in at least the known case
it was harmless because that byte would be overwritten after return).
Per report from Ken Colson; fix by Marko Kreen.
|
|
|
|
|
|
|
| |
to prevent possible escalation of privilege. Provide new SECURITY
DEFINER functions with old behavior, but initially REVOKE ALL
from public for these functions. Per list discussion and design
proposed by Tom Lane.
|
|
|
|
| |
Per report from Listmail <lists@peufeu.com>
|
|
|
|
| |
Per report from Jon Rosebaugh <jon@inklesspen.com>
|
|
|
|
|
|
|
|
| |
Call srandom() instead of srand().
pgbench calls random() later, so it should have called srandom().
On most platforms except Windows srandom() is actually identical
to srand(), so the bug only bites Windows users.
per bug report from Akio Ishida.
|
| |
|
|
|
|
| |
<mweilguni@sime.com>
|
|
|
|
|
|
| |
what was a reason to corrupt index.
Thank to Mario Weilguni <mweilguni@sime.com> to
discover a bug.
|
|
|
|
| |
Thank to Mario Weilguni <mweilguni@sime.com> to discover a bug.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Martin Pitt [2006-06-16 0:15 +0200]:
> Upstream confirmed my reply in the last mail in [1]: the complete
> escaping logic in DBMirror.pl is seriously screwew.
>
> [1] http://archives.postgresql.org/pgsql-bugs/2006-06/msg00065.php
I finally found some time to debug this, and I think I found a better
patch than the one you proposed. Mine is still hackish and is still a
workaround around a proper quoting solution, but at least it repairs
the parsing without introducing the \' quoting again.
I consider this a band-aid patch to fix the recent security update.
PostgreSQL gurus, would you consider applying this until a better
solution is found for DBMirror.pl?
Martin Pitt http://www.piware.de
|
| |
|
| |
|
|
|
|
| |
and 8.0. Later releases already patched.
|
|
|
|
| |
Minor cleanups.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
pgcrypto crypt()/md5 and hmac() leak memory when compiled against
OpenSSL as openssl.c digest ->reset will do two DigestInit calls
against a context. This happened to work with OpenSSL 0.9.6
but not with 0.9.7+.
Reason for the messy code was that I tried to avoid creating
wrapper structure to transport algorithm info and tried to use
OpenSSL context for it. The fix is to create wrapper structure.
It also uses newer digest API to avoid memory allocations
on reset with newer OpenSSLs.
Thanks to Daniel Blaisdell for reporting it.
|
|
|
|
|
|
| |
than the local query specifies (e.g. in the FROM clause),
throw an ERROR (instead of crashing). Fix for bug #2129 reported
by Akio Iwaasa.
|
|
|
|
|
|
|
| |
This makes the salt space for md5 and xdes algorithms a lot smaller than
it should be.
Marko Kreen
|
| |
|
| |
|
| |
|
|
|
|
| |
dropped. Per report from daveg (not his patch, though).
|
|
|
|
|
| |
old version doesn't available on Snowball's site and new version
of stemmers can't be compiled with old interface.
|
|
|
|
|
| |
working state, not fcinfo->context. Silly oversight on my part in last
go-round of fixes.
|
|
|
|
| |
cleanly on AIX in the 8.0 branch. Rocco Altier
|
|
|
|
|
|
|
| |
have the same name as the containing shared library --- as best I can
tell, the compiler internally creates a function of that name, and does
not warn you about the conflict. Fix buildfarm failure in back branches
by renaming tsearch() trigger function at the C level.
|
| |
|
| |
|
|
|
|
|
|
| |
instead of pg_usleep.
Backpatch to 8.0.X.
|
|
|
|
|
|
|
|
| |
that return INTERNAL without also having INTERNAL arguments. Since the
functions in question aren't meant to be called by hand anyway, I just
redeclared them to take 'internal' instead of 'text'. Also add code
to ProcedureCreate() to enforce the restriction, as I should have done
to start with :-(
|
| |
|
| |
|
|
|
|
|
| |
aren't 1-D, so give an error message instead of failing. Per report
from Ron Mayer.
|
| |
|
|
|
|
|
| |
daemonize routine, namely forcing stdin/stdout/stderr to point
to /dev/null. Per Karl Denninger.
|
| |
|
|
|
|
| |
platforms, and suggest using ~/.pgpass instead.
|
|
|
|
|
|
| |
immunte to changes in libpq's usage of pgport between major versions.
Backpatch to 8.0.X.
|
|
|
|
|
| |
fixed properly in CVS tip, but we need a band-aid for back branches.
Per report from Ron Mayer.
|
|
|
|
|
|
|
|
|
|
|
|
| |
0.9.7x have EVP_DigestFinal function which which clears all of
EVP_MD_CTX. This makes pgcrypto crash in functions which
re-use one digest context several times: hmac() and crypt()
with md5 algorithm.
Following patch fixes it by carring the digest info around
EVP_DigestFinal and re-initializing cipher.
Marko Kreen.
|