| Commit message (Collapse) | Author | Age |
|
|
|
|
|
| |
a result of at most 128 chars, but that could be more than 128 bytes.
Also ensure we don't try to pfree uninitialized pointers during error
cleanup.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
"SSLv23_method(void), SSLv23_server_method(void), SSLv23_client_method(void)
A TLS/SSL connection established with these methods will understand the SSLv2,
SSLv3, and TLSv1 protocol. A client will send out SSLv2 client hello messages
and will indicate that it also understands SSLv3 and TLSv1. A server will
understand SSLv2, SSLv3, and TLSv1 client hello messages. This is the best
choice when compatibility is a concern."
This will maintain backwards compatibility for those us that don't use
TLS connections ...
|
| |
|
|
|
|
|
|
|
|
| |
disallowed by CREATE TABLE (eg, pseudo-types); also disallow these types
from being introduced by the range-function syntax. While at it, allow
CREATE TABLE to create zero-column tables, per recent pghackers discussion.
I am back-patching this into 7.3 since failure to disallow pseudo-types
is arguably a security hole.
|
|
|
|
|
|
|
|
| |
failing to find pg_hba.conf should be a fatal error anyway, so I
increased the priority of the elog() from LOG to FATAL and refactored
the code a little bit.
Neil Conway
|
|
|
|
|
|
|
| |
pqcomm.c, switched the ERROR logs to COMMERROR logs and it all works.
I've attached a patch to be-secure.c that fixes all my problems.
Nathan Mueller
|
| |
|
| |
|
| |
|
|
|
|
|
| |
simplified function call to a constant. (7.3 won't actually execute
such a plan anyway, but core dump is bad regardless.)
|
|
|
|
| |
template/sco updated.
|
|
|
|
|
|
| |
report from Oliver Elphick.
Backpatch to 7.3.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
cleaning up locale names and nothing else. Since all the locale names
are in plain ASCII I think it will be safe to use ASCII-only lower-case
conversion.
Nicolai Tufar
|
|
|
|
| |
all along; not noticed till now. It's a scan not an upper qual ...
|
| |
|
|
|
|
|
|
| |
problems that occur if sublink is referenced via a join alias variable.
Perhaps this can be improved later, but a simple and safe fix is needed
for 7.3.1.
|
|
|
|
|
|
| |
report from Terry Yapt and Hiroshi.
Backpatch to 7.3.
|
| |
|
|
|
|
|
| |
recursing to handle a join alias var, the context had better be set to
be appropriate to the join var's query level. Per report from Hristo Neshev.
|
|
|
|
| |
datconfig or useconfig field. Per report from Dustin Sallings.
|
|
|
|
| |
report from Philip Warner.
|
|
|
|
|
| |
server encoding, per report from Nicolai Tufar. This is a minimum-risk
patch for 7.3.1 --- I intend to apply a more general repair in HEAD.
|
| |
|
|
|
|
| |
solaris 2.8 as well as 2.7. Per report from Martin Renters.
|
| |
|
|
|
|
| |
--- not needed.
|
|
|
|
|
| |
as elog format strings. Hai-Chen Tu pointed out the problem in
contrib/dbmirror, but it wasn't the only such error.
|
|
|
|
| |
Christopher Kings-Lynne.
|
|
|
|
| |
(64-bit). Fix it. Per report from Permaine Cheung.
|
|
|
|
|
|
| |
results due to doing arithmetic on uninitialized values. Add some
documentation about the AT TIME ZONE construct. Update some other
date/time documentation that seemed out of date for 7.3.
|
|
|
|
|
|
| |
database access outside a transaction; revert bogus performance improvement
in SIBackendInit(); improve comments; add documentation (this part courtesy
Neil Conway).
|
|
|
|
|
| |
comparison file, instead of geometry-positive-zeros. Per report from
Patrick Welche.
|
|
|
|
| |
when a test was added to select_having.sql back in June.
|
|
|
|
|
|
| |
Modified Files:
Tag: REL7_3_STABLE
AbstractJdbc2Statement.java
|
|
|
|
|
|
|
|
|
|
| |
been reported by Marko Strukelj and Keith Wannamaker
Modified Files:
Tag: REL7_3_STABLE
jdbc/org/postgresql/jdbc1/AbstractJdbc1Statement.java
jdbc/org/postgresql/jdbc2/AbstractJdbc2Statement.java
jdbc/org/postgresql/test/jdbc2/BatchExecuteTest.java
|
|
|
|
| |
but do it correctly now.
|
|
|
|
| |
at each plan node. Per gripe from Ross Reedstrom.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
server prepared statements and an improved error message
Modified Files:
Tag: REL7_3_STABLE
jdbc/org/postgresql/errors.properties
jdbc/org/postgresql/core/Encoding.java
jdbc/org/postgresql/core/QueryExecutor.java
jdbc/org/postgresql/jdbc1/AbstractJdbc1Connection.java
jdbc/org/postgresql/jdbc1/AbstractJdbc1DatabaseMetaData.java
jdbc/org/postgresql/jdbc1/AbstractJdbc1Statement.java
|
| |
|
|
|
|
| |
meaning +1300.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
anymore given the mktime() workaround now done in DetermineLocalTimeZone.
This has now been confirmed by Robert Bruccoleri for Irix, and I'm going
to extrapolate to AIX as well.
|
|
|
|
|
|
|
| |
Modified Files:
Tag: REL7_3_STABLE
jdbc/org/postgresql/jdbc1/AbstractJdbc1DatabaseMetaData.java
jdbc/org/postgresql/test/jdbc2/DatabaseMetaDataTest.java
|
| |
|