| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
freeing all transient state of the PGconn object.
|
| |
|
|
| |
that has no terminating newline. Per report from maps.on at gmx.net.
|
| |
|
|
| |
Also, back-patch fix into back branches.
|
| | |
|
| |
|
|
|
|
|
|
| |
SELECT date_trunc('week', '2002-12-31'::date);
Backpatch to 8.0.X.
Per report from Nick Johnson.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
name matches the name of any parent-table constraint, without looking
at the constraint text. This is a not-very-bulletproof workaround for
the problem exhibited by Berend Tober last month. We really ought to
record constraint inheritance status in pg_constraint, but it's looking
like that may not get done for 8.1 --- and even if it does, we will
need this kluge for dumping from older servers.
|
| |
|
|
|
|
| |
should fix the recent reports of "index is not a btree" failures,
as well as preventing a more obscure race condition involving changes
to a template database just after copying it with CREATE DATABASE.
|
| |
|
|
|
| |
was being called twice in normal operation, leading to a leak of one set
of relcache subsidiary info. Per report from Jeff Gold.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
(1) The code doesn't initialize `sum', so the initial "does the checksum
match?" test is wrong.
(2) The loop that is intended to check for a "null block" just checks
the first byte of the tar block 512 times, rather than each of the
512 bytes one time (!), which I'm guessing was the intent.
It was only through sheer luck that this worked in the first place.
Per Coverity static analysis performed by EnterpriseDB.
|
| |
|
|
|
|
|
| |
malformed ident map file. This was introduced by the linked list
rewrite in 8.0 -- mea maxima culpa.
Per Coverity static analysis performed by EnterpriseDB.
|
| |
|
|
|
|
|
| |
It never leaked memory before PG 8.0, so none of the callers are
expecting this. Cleanest fix seems to be to make it allocate the needed
memory in estate->eval_econtext, where it will be cleaned up by
the next exec_eval_cleanup. Per report from Bill Rugolsky.
|
| |
|
|
|
|
|
| |
copying/converting the new value, which meant that it failed badly on
"var := var" if var is of pass-by-reference type. Fix this and a similar
hazard in exec_move_row(); not sure that the latter can manifest before
8.0, but patch it all the way back anyway. Per report from Dave Chapeskie.
|
| |
|
|
|
|
| |
not memcpy() to copy the offered key into the hash table during HASH_ENTER.
This avoids possible core dump if the passed key is located very near the
end of memory. Per report from Stefan Kaltenbrunner.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
if geqo_rand() returns exactly 1.0, resulting in failure due to indexing
off the end of the pool array. Also, since this is using inexact float math,
it seems wise to guard against roundoff error producing values slightly
outside the expected range. Per report from bug@zedware.org.
|
| | |
|
| |
|
|
| |
Per Volkan Yazici.
|
| |
|
|
| |
not schema-safe. Per report from Jochem van Dieten.
|
| |
|
|
| |
prepared for HAVE_INT64_TIMESTAMP. Per report from Guillaume Beaudoin.
|
| |
|
|
| |
Weiping (Laser)
|
| |
|
|
| |
Viktor Vislobokov
|
| |
|
|
|
|
|
| |
to just around the bare recv() call that gets a command from the client.
The former placement in PostgresMain was unsafe because the intermediate
processing layers (especially SSL) use facilities such as malloc that are
not necessarily re-entrant. Per report from counterstorm.com.
|
| |
|
|
| |
[One half already was committed with the last commit.]
|
| | |
|
| |
|
|
|
|
|
|
| |
and DDL statements.
Backpatch fix to 8.0.X.
Per report from Murthy Kambhampaty
|
| |
|
|
|
|
| |
expressions it constructed, causing scalarineqsel to become confused
if the underlying variable was of a domain type. Per report from
Kevin Grittner.
|
| | |
|
| |
|
|
|
| |
WAL record; this is necessary to be sure we recognize stale WAL records
when a WAL page was only partially written during a system crash.
|
| |
|
|
|
|
| |
to columns of an RTE that was a function returning RECORD with a column
definition list. Apparently no one has tried to use non-default typmod
with a function returning RECORD before.
|
| |
|
|
| |
Mahmoud Taghizadeh
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
working buffer into ParseDateTime() and reject too-long input there,
rather than checking the length of the input string before calling
ParseDateTime(). The old method was bogus because ParseDateTime() can use
a variable amount of working space, depending on the content of the
input string (e.g. how many fields need to be NUL terminated). This fixes
a minor stack overrun -- I don't _think_ it's exploitable, although I
won't claim to be an expert.
Along the way, fix a bug reported by Mark Dilger: the working buffer
allocated by interval_in() was too short, which resulted in rejecting
some perfectly valid interval input values. I added a regression test for
this fix.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
if they are two-byte multibyte characters. Same thing can be happen
if octet_length(multibyte_chars) == n where n is char(n).
Long standing bug since 7.3 days. Per report and fix from Yoshiyuki Asaba.
|
| |
|
|
|
|
|
| |
where there was also a WHERE-clause restriction that applied to the
join. The check on restrictlist == NIL is really unnecessary anyway,
because select_mergejoin_clauses already checked for and complained
about any unmergejoinable join clauses. So just take it out.
|
| |
|
|
| |
sharing of %_SHARED. From Andrew Dunstan.
|
| |
|
|
| |
Jun Kuwamura
|
| | |
|
| |
|
|
| |
Per report from Brian Hackett.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
and add an example showing assignment of a password. Per suggestion
from Jari Aalto (via Martin Pitt).
|
| | |
|
| |
|
|
| |
input. Also add a regression test for this bug. From Andrew Dunstan.
|
