Tom Lane [Fri, 9 Feb 2001 03:26:28 +0000 (03:26 +0000)]
plpgsql's private copy of xlateSqlType was out of sync. Again. This
is clearly not maintainable, so dike it out in favor of calling the real
version in the backend's gram.y.
Tom Lane [Fri, 9 Feb 2001 00:14:26 +0000 (00:14 +0000)]
EXECUTE of a SELECT ... INTO now draws a 'not implemented' error,
rather than executing the INTO clause with non-plpgsql semantics
as it was doing for the last few weeks/months. This keeps our options
open for making it do the right plpgsql-ish thing in future without
creating a backwards compatibility problem. There is no loss of
functionality since people can get the same behavior with CREATE TABLE AS.
Remove outdated contrib/linux start scripts. Beat some sense into
contrib/init.d start script. Place into more aptly named directory. Maybe
we could add scripts for other platforms here later.
Make -w the default for shut down, add -W option to specify no wait.
Add -l option to name log file. Set umask to 077.
Proper file descriptor redirection to allow postmaster to detach from
shell's process group.
Add -s option to turn off informational messages.
Tom Lane [Thu, 8 Feb 2001 00:35:10 +0000 (00:35 +0000)]
When launching a child backend, take care to close file descriptors for
any other client connections that may exist (which would only happen if
another client is currently in the authentication cycle). This avoids
wastage of open descriptors in a child. It might also explain peculiar
behaviors like not closing connections when expected, since the kernel
will probably not signal EOF as long as some other backend is randomly
holding open a reference to the connection, even if the client went away
long since ...
Tom Lane [Wed, 7 Feb 2001 21:30:12 +0000 (21:30 +0000)]
Redo pgaccess' queries about views so that they will work in both 7.1
and prior releases --- rely on pg_views view instead of direct access
to pg_class and pg_rewrite.
Tom Lane [Wed, 7 Feb 2001 20:30:20 +0000 (20:30 +0000)]
Use explicit path to libpgtcl.so, instead of relying on LD_LIBRARY_PATH
or local equivalent. Also, honor --with-pgport configure option for
default port number, and allow PGPORT environment variable to override
this.
Only pass the -L* portions of LDFLAGS to the Python build environment.
Other flags can have unpredictable effects when Python uses different
commands to build than we do.
Tom Lane [Wed, 7 Feb 2001 17:59:58 +0000 (17:59 +0000)]
Need to specify DYNAMIC_PATH flag to shl_load, else HPUX's dld will not
honor library search path that we so carefully installed into the
executable ...
Hiroshi Inoue [Tue, 6 Feb 2001 02:21:12 +0000 (02:21 +0000)]
Improved version handling introduced by Dave Page.
The driver version is 07.01.0002 now.
1) initialized pg_version by DSN's protocol info
so that we could always use pg_version info
once a connection is established (pg_version()
didn't exist before 6.4). PROTOCOL_XX() macros
are removed(except from connection.[ch]).
2) provided a few macros to encapsulate connection's
version info and replaced existent comparison
stuff by those macros.
3) change SQLTables() so that 7.1 servers could show
views.
In addtion, the following patch from Dave Page is applied.
This patch fixes a bug in SQLGetInfo for SQL_DBMS_VER which corrupted the
driver version string. The driver version number has also been incremented
to 07.01.0002.
Tom Lane [Tue, 6 Feb 2001 01:53:53 +0000 (01:53 +0000)]
Out-of-bounds memory allocation request sizes should be treated as just
elog(ERROR) not an Assert trap, since we've downgraded out-of-memory to
elog(ERROR) not a fatal error. Also, change the hard boundary from 256Mb
to 1Gb, just so that anyone who's actually got that much memory to spare
can play with TOAST objects approaching a gigabyte.
Dump/display 'timestamp' as 'timestamp with time zone', to make room for a
future 'timestamp without time zone', which SQL claims is equivalent to
plain 'timestamp'.
When making xrefs to refsects, the linkend should point to the refsect and
the endterm to the title element, not both to the title. At least
docbook2man prefers it that way.
Bruce Momjian [Thu, 1 Feb 2001 18:31:10 +0000 (18:31 +0000)]
Please replace with the one attached to this email message. The
previous version depended on the below patch, this one does not. It is
also a bit cleaner and has a few more helpful comments.
Peter Mount [Wed, 31 Jan 2001 09:23:45 +0000 (09:23 +0000)]
Wed Jan 31 08:46:00 GMT 2001 peter@retep.org.uk
- Some minor additions to Statement to make our own extensions more
portable.
- Statement.close() will now call ResultSet.close() rather than just
dissasociating with it.
Peter Mount [Wed, 31 Jan 2001 08:26:02 +0000 (08:26 +0000)]
Tue Jan 30 22:24:00 GMT 2001 peter@retep.org.uk
- Fixed bug where Statement.setMaxRows() was a global setting. Now
limited to just itself.
- Changed LargeObject.read(byte[],int,int) to return the actual number
of bytes read (used to be void).
- LargeObject now supports InputStream's!
- PreparedStatement.setBinaryStream() now works!
- ResultSet.getBinaryStream() now returns an InputStream that doesn't
copy the blob into memory first!
- Connection.isClosed() now tests to see if the connection is still alive
rather than if it thinks it's alive.
Tom Lane [Mon, 29 Jan 2001 00:39:20 +0000 (00:39 +0000)]
Clean up handling of tuple descriptors so that result-tuple descriptors
allocated by plan nodes are not leaked at end of query. This doesn't
really matter for normal queries, but it sure does for queries invoked
repetitively inside SQL functions. Clean up some other grotty code
associated with tupdescs, and fix a few other memory leaks exposed by
tests with simple SQL functions.