| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
[This is a repost - it supercedes the previous one. It fixes the patch so
it doesn't bread aix port, plus there's a file missing out of the
original post because difforig doesn't pick up new files. It's now
attached. peter]
This patch brings the JDBC driver up to the current protocol spec.
Basically, the backend now tells the driver what authentication scheme to
use.
The patch also fixes a performance problem with large objects. In the
buffer manager, each fastpath call was sending multiple Notifications to
the backend (sometimes more data in the form of notifications were being
sent than blob data!).
|
|
|
|
|
|
|
|
|
| |
I haven't had final confirmation from Peter yet, but the attached patch
needs to be applied for the Beta otherwise password and crypt
authentication just won't work.
It puts back the loop in libpq and also fixes a couple of problems with
maintaining compatability with pre-6.3 drivers.
|
|
|
|
|
|
|
|
|
|
|
| |
Attached is the patch to fix the warning messages from my code. I also
fixed one which wasn't my code. Apart from the usual warnings about the
bison/yacc generated code I only have one other warning message. This
is in gramm.y around line 2234. I wasn't sure of the fix.
I've also replaced all the calls to free() in gramm.y to calls to
pfree(). Without these I was getting backend crashes with GRANT. This
might already have been fixed.
|
|
|
|
|
|
|
|
|
|
| |
This has a problem when using any authentication other than trust or
ident.
Anything using libpq will hang, because the client will go into a loop
while connecting. The following patch simply comments out two lines (a do
and a while), removing the loop. Going through the new scheme, I can't see
why this do..while loop is in there.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I've completed the patch to fix the protocol and authentication issues I
was discussing a couple of weeks ago. The particular changes are:
- the protocol has a version number
- network byte order is used throughout
- the pg_hba.conf file is used to specify what method is used to
authenticate a frontend (either password, ident, trust, reject, krb4
or krb5)
- support for multiplexed backends is removed
- appropriate changes to man pages
- the -a switch to many programs to specify an authentication service
no longer has any effect
- the libpq.so version number has changed to 1.1
The new backend still supports the old protocol so old interfaces won't
break.
|
| |
|
|
|
|
|
|
| |
Hi -- a couple of small items concerning the January 23rd snapshot:
the inclusion of the Kerberos stuff in one Makefile, a "leading tab"
cleanup in another, and a fix for a typo in the configure script.
|
|
|
|
| |
Fixed pointed out by: jwieck@debis.com (Jan Wieck)
|
|
|
|
|
|
| |
This patch makes it possible to do a "real" make distclean (back to its
fresh state) on the distribution after compilation, regression testing,
etc.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The attached patches will allow postgreSQL to compile successfully on SCO
UNIXWARE 2.1.x. The patches fix the following problems:
1. Configure did not properly recognize the UNIXWARE system as needing the
univel port. It used the sys4 port.
2. Configure did not properly process the CC flag in the template file.
3. There was no working test and set locking implementation for the native
UNIXWARE compiler.
4. The test and set locking used for Intel X86 that was selected by defining
NEED_I386_TAS_ASM could fail in a multi-processor environment.
5. The makefiles for libpq and libpgtcl did not make a shared library for
the univel port.
|
|
|
|
|
| |
a) psql dumps core when using -a password and PGUSER is set but PGPASSWORD
not set.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
OK, here comes a patch, DBD::Pg (and possibly other 3rd party clients)
can connect to unix sockets.
Patch is against current source tree.
Background:
libpq set some policy for client, which it should not
IMHO. It prevent some 3rd party clients to connect with
unix domain sockets etc.
|
|
|
|
|
|
|
| |
reference to the name of the shared library, instead of dereferencing
the definition from the top of the file.
From: Tom I Helbekkmo <tih@Hamartun.Priv.NO>
|
|
|
|
| |
From: Tom I Helbekkmo <tih@Hamartun.Priv.NO>
|
| |
|
| |
|
|
|
|
| |
see README_6.3 for list of changes
|
| |
|
| |
|
|
|
|
| |
Most processors should optimize this a bit better wrt cache prefetch.
|
|
|
|
| |
failed connections.
|
|
|
|
| |
failed connections.
|
|
|
|
|
| |
An extension to the code to allow for a pg_password authentication database
that is *seperate* from the system password file
|
| |
|
|
|
|
| |
of field names uppercase code.
|
| |
|
|
|
|
| |
uninitialized variables. I _think_ the logic is preserved...
|
|
|
|
|
| |
PGCOSTHEAP, PGCOSTINDEX, PGRPLANS, PGGEQO
(PGDATESTYLE, PGTZ already defined)
|
|
|
|
|
|
|
| |
Rename PG_DATESTYLE to PGDATESTYLE environment variable.
Move environment variable code to a different place so it now works!
Note that regression tests can now run with "setenv PGTZ PST8PDT"
at the frontend rather than requiring the backend to have TZ set.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This patch fixes a few results in DatabaseMetaData, and updates the README
and TODO files (the later being a new file).
The TODO file lists the things that need to be looked into after 6.2 is
released, and describes the problem with Large Objects.
|
|
|
|
|
|
|
|
| |
I've found a problem in the Postgresql jdbc driver.
"ReceiveInteger" shifts a received byte right instead of left.
This means that only the least significant byte is read into the int.
Reviewed by: Peter T Mount <patches@maidast.demon.co.uk>
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|