| Age | Commit message (Collapse) | Author |
|---|
|
aggregate seems uniquely fragile, because it's the only one with an
agginitval that's at all likely to change in format.
|
|
|
|
specification of username (like in psql). pg_dumpall now works with
password authentication.
|
|
library extension.
|
|
there is a brace on the line above it.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(1.22) of interfaces/jdbc/org/postgresql/jdbc2/ResultSet.java. That
change removed a line that set the variable s to the value of the
stringbuffer. This fix changes the following if checks to check the
length of the stringbuffer instead of s, since s no longer contains the
string the if conditions are expecting.
The bug manifests itself in getTimestamp() loosing the timezone
information of timestamps selected from the database, thereby causing
the time to be incorrect.
Barry Lind
|
|
Here's what I came up with. The biggest difference api between JDK1.x and
later versions is the support for collections. The problem was with the
Vector class; in jdk1.x there is no method called add, so I changed the
calls to addElement. Also no addAll, so I rewrote the method slightly to not
require addAll. While reviewing this I notices some System.out.println
statements that weren't commented out. So I commented them out in both
versions.
The upshot of all of this is that I have clean compile, but no idea if the
code works ;(
Dave Cramer
|
|
|
|
2) Repair broken SQLStatistics().
|
|
library code. Tweak progress messages to include elapsed real time,
not only CPU time.
|
|
|
|
|
|
PageGetFreeSpace() was being called while not holding the buffer lock, which
not only could yield a garbage answer, but even if it's the right answer there
might be less space available after we reacquire the buffer lock.
Also repair potential deadlock introduced by my recent performance improvement
in RelationGetBufferForTuple(): it was possible for two heap_updates to try to
lock two buffers in opposite orders. The fix creates a global rule that
buffers of a single heap relation should be locked in decreasing block number
order. Currently, this only applies to heap_update; VACUUM can get away with
ignoring the rule since it holds exclusive lock on the whole relation anyway.
However, if we try to implement a VACUUM that can run in parallel with other
transactions, VACUUM will also have to obey the lock order rule.
|
|
|
|
is of type Object, and is null
Dave Cramer
|
|
David Esposito
|
|
(http://www.ideit.com/products/dbvis/) to work with Postgresql and I found
out the following bug: if database has views then getTables() gets the null
pointer exception ('order by relname' makes the listing tree in
DbVisualizer a lot useful !!)
This patch should propably be applied to the the jdbc1's
DatabaseMetaData.java, too.
Panu Outinen
|
|
return ((c == 't') || (c == 'T'));
int the getBoolean function on line 184:ish to:
return ((c == 't') || (c == 'T') (c == '1'));
Hunter Hillegas
|
|
|
|
|
|
|
|
public ResultSet getTables(String catalog, String schemaPattern, String
Jeroen van Vianen
|
|
Ola Sundell
|
|
not properly handle 8-bit unsigned data as it blindly
casts the byte to an int, which java most helpfully
promotes to a signed type. This causes problems when
you can only return -1 to indicated EOF.
The following patch fixes the bug and has been tested
locally on image data.
Chad David
|
|
|
|
type never scans a relation directly, it can't be an EPQ target.
Explicitly drop subplan's tuple table to ensure we have no buffer pin
leaks.
|
|
with many NULLs ( inserting of NULL into indexed field cause
ERROR: MemoryContextAlloc: invalid request size)
As a workaround 'vacuum analyze' could be used.
This patch resolves the problem, please upply to 7.1.1 sources and
current cvs tree.
Oleg Bartunov
|
|
|
|
|
|
|
|
dynamic linker change. #include must be before #ifdef test.
|
|
|
|
trees (mostly my fault). Repair. Also fix long-standing bug in ExecReplace:
after recomputing a concurrently updated tuple, we must recheck constraints.
Make EvalPlanQual leak memory with somewhat less enthusiasm than before,
although plugging leaks fully will require more changes than I care to risk
in a dot-release.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
forced.
|
|
for relations on the nullable side of an OUTER JOIN. For now I think
we'd better refuse such queries.
|
|
|
