aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
* Even though SO_PEERCRED is probably totally unportable, might as wellTom Lane2001-08-02
| | | | | declare the getsockopt parameter as ACCEPT_TYPE_ARG3 to be consistent with our other uses of getsockopt.
* Remove SO_PASSCRED step in ident_unix --- according to Helge Bahmann,Tom Lane2001-08-02
| | | | | | that call is not needed to prepare for SO_PEERCRED. Also, simplify code so that #ifdef SO_PEERCRED appears in only one place, to make it easier to support other platforms with variants of this capability.
* Digging through previous discussion of this patch, I note where Peter E.Tom Lane2001-08-01
| | | | | | points out how silly it is to use Autoconf to test for a preprocessor symbol, when one can equally easily #ifdef on the symbol itself. Accordingly, revert configure to prior state and do it that way.
* Support ident authentication on local (Unix) socket connections, if theTom Lane2001-08-01
| | | | | | system supports SO_PEERCRED requests for Unix sockets. This is an amalgamation of patches submitted by Helge Bahmann and Oliver Elphick, with some editorializing by yours truly.
* Attached is a trivial patch to add ANALYZE to the tab complete file inBruce Momjian2001-08-01
| | | | | | psql. Randy Hall
* Attached ia a patch to enable window size detection code of psql for SolarisBruce Momjian2001-08-01
| | | | | | | | | | | | | | | platform. TIOCGWINSZ is defined as follows: Linux asm/ioctls.h FreeBSD sys/ttycom.h. This file is included by sys/ioctl.h. Solaris sys/termios.h This patch tells print.c to know TIOCGWINSZ on Solaris platform. Same code is founded in src/bin/psal/common.c. Kenji Sugita
* Message typo was fixed in sources, but not in de.po.Tom Lane2001-08-01
|
* Add mention of SIGHUP for pg_ident.conf.Bruce Momjian2001-08-01
|
* Add documentation changes for new pg_hba.conf behavior.Bruce Momjian2001-08-01
|
* Cleanup code for preparsing pg_hba.conf and pg_ident.conf. Store lineTom Lane2001-07-31
| | | | | | | | | number in the data structure so that we can give at least a minimally useful idea of where the mistake is when we issue syntax error messages. Move the ClientAuthentication() call to where it should have been in the first place, so that postmaster memory releasing can happen in a reasonable place also. Update obsolete comments, correct one real bug (auth_argument was not picked up correctly).
* Further thought shows that has_distinct_on_clause() needs to take muchTom Lane2001-07-31
| | | | | | | | more care with resjunk tlist entries than it was doing. The original coding ignored resjunk entries entirely, but a resjunk entry that is in either the distinctClause or sortClause lists indicates that DISTINCT ON was used. It's important for ruleutils.c to get this right, else we may dump views using DISTINCT ON incorrectly.
* Fix optimizer to not try to push WHERE clauses down into a sub-SELECT thatTom Lane2001-07-31
| | | | | | has a DISTINCT ON clause, per bug report from Anthony Wood. While at it, improve the DISTINCT-ON-clause recognizer routine to not be fooled by out- of-order DISTINCT lists.
* Update 'translate' function description. translate does character setBruce Momjian2001-07-31
| | | | mapping, not character strings.
* Update info on pg_hba.conf comments.Bruce Momjian2001-07-31
|
* Remove WIN32_NON_BLOCKING_CONNECTIONS tests, since we don't need 'emTom Lane2001-07-31
| | | | anymore.
* Fix unportable coding for FRONTEND case.Tom Lane2001-07-31
|
* Change SQL commands embedded in the initdb script from the styleTom Lane2001-07-31
| | | | | | | | | | | | | | | echo "command" | postgres to the style postgres <<EOF command EOF This makes the script more legible (IMHO anyway) by reducing the need to escape quotes, and allows us to execute successive SQL commands in a single standalone-backend run, rather than needing to start a new standalone backend for each command. With all the CREATE VIEWs that are getting done now, this makes for a rather substantial reduction in the runtime of initdb. (Some of us do initdb often enough to care how long it runs ;-).)
* This patch merges the identical methods from the JDBC1 and JDBC2Bruce Momjian2001-07-30
| | | | | | | | | | | | connection implementations (org.postgresql.jdbc[1|2].Connection) into their superclass (org.postgresql.Connection). It also changes the close() methods of Connection and PG_Stream, so that PG_Stream no longer is responsible for sending the termination packet 'X' to the backend. I figured that protocol-level stuff like that belonged in Connection more than in PG_Stream. Anders Bengtsson
* Load pg_hba.conf and pg_ident.conf on startup and SIGHUP into List ofBruce Momjian2001-07-30
| | | | | | Lists, and use that for user validation. Bruce Momjian
* Arrange for GRANT/REVOKE on a view to be dumped at the right time,Tom Lane2001-07-29
| | | | | namely after the view definition rather than before it. Bug introduced in 7.1 by changes to dump stuff in OID ordering.
* Suppress gcc warning in USE_LOCALE case.Tom Lane2001-07-22
|
* Move EncodingTest.java file.Bruce Momjian2001-07-21
|
* DatabaseMetaData.getColumns() doesn't appear to get the defaultBruce Momjian2001-07-21
| | | | | | | value for each column. Here is a context diff of CVS which should fix it. Jason Davies
* Great, here is a context diff of CVS for implementing the get/setCatalog methodsBruce Momjian2001-07-21
| | | | | | | in Connection - note: I've updated setCatalog(String catalog) from my previous diff so it checks whether it is already connected to the specified catalog. Jason Davies
* JDBC encoding additions.Bruce Momjian2001-07-21
| | | | | | | Here's a patch against the current CVS. The changes from the previous patch are mostly related to the changed interface for PG_Stream. Anders Bengtsson
* I downloaded new source for lib (only few hours old !!!), and madeBruce Momjian2001-07-21
| | | | | | | | | | changes on this new source to make non-blocking connection work. I tested it, and PQSendQuery and PQGetResult are working fine. In win32.h I added one line: #define snprintf _snprintf Darko Prenosil
* Source formatting cleanup.Bruce Momjian2001-07-21
|
* i've spotted a following problem using DBD::Pg under win32. winsockBruce Momjian2001-07-20
| | | | | | | | | functions do not set errno, so some normal conditions are treated as fatal errors. e.g. fetching large tuples fails, as at some point recv() returns EWOULDBLOCK. here's a patch, which replaces errno with WSAGetLastError(). i've tried to to affect non-win32 code. Dmitry Yurtaev
* Minor performance improvement in MultiRecordFreeSpace.Tom Lane2001-07-19
|
* Arrange to recycle old XLOG log segment files as new segment files,Tom Lane2001-07-19
| | | | | | | | | | | | | | rather than deleting them only to have to create more. Steady state is 2*CHECKPOINT_SEGMENTS + WAL_FILES + 1 segment files, which will simply be renamed rather than constantly deleted and recreated. To make this safe, added current XLOG file/offset number to page header of XLOG pages, so that an un-overwritten page from an old incarnation of a logfile can be reliably told from a valid page. This change means that if you try to restart postmaster in a CVS-tip database after installing the change, you'll get a complaint about bad XLOG page magic number. If you don't want to initdb, run contrib/pg_resetxlog (and be sure you shut down the old postmaster cleanly).
* New-style vacuum neglected to update pg_class statistics about indexesTom Lane2001-07-18
| | | | if there were no deletions to do.
* Disallow non-cachable functions in functional indexes and in indexTom Lane2001-07-17
| | | | predicates. Per suggestion from Hiroshi.
* Avoid assuming that pg_index table entries have unique OIDs, or evenTom Lane2001-07-17
| | | | | that they have OIDs at all (the primary key for this table is indexrelid, not OID). Simplify overly complex query to get name of primary key.
* Improve documentation about reasoning behind the order of operationsTom Lane2001-07-16
| | | | | | | | in GetSnapshotData, GetNewTransactionId, CommitTransaction, AbortTransaction, etc. Correct race condition in transaction status testing in HeapTupleSatisfiesVacuum --- this wasn't important for old VACUUM with exclusive lock on its table, but it sure is important now. All per pghackers discussion 7/11/01 and 7/12/01.
* Fix fault in message.Peter Eisentraut2001-07-16
|
* Remove some unused node symbolsBruce Momjian2001-07-16
|
* More EXTEND INDEX removal.Bruce Momjian2001-07-16
| | | | Martijn van Oosterhout
* Do not push down quals into subqueries that have LIMIT/OFFSET clauses,Tom Lane2001-07-16
| | | | | since the added qual could change the set of rows that get past the LIMIT. Per discussion on pgsql-sql 7/15/01.
* Partial indexes work again, courtesy of Martijn van Oosterhout.Tom Lane2001-07-16
| | | | | | Note: I didn't force an initdb, figuring that one today was enough. However, there is a new function in pg_proc.h, and pg_dump won't be able to dump partial indexes until you add that function.
* Restructure index AM interface for index building and index tuple deletion,Tom Lane2001-07-15
| | | | | | | | | | | | | | | | | | | | | | | | | per previous discussion on pghackers. Most of the duplicate code in different AMs' ambuild routines has been moved out to a common routine in index.c; this means that all index types now do the right things about inserting recently-dead tuples, etc. (I also removed support for EXTEND INDEX in the ambuild routines, since that's about to go away anyway, and it cluttered the code a lot.) The retail indextuple deletion routines have been replaced by a "bulk delete" routine in which the indexscan is inside the access method. I haven't pushed this change as far as it should go yet, but it should allow considerable simplification of the internal bookkeeping for deletions. Also, add flag columns to pg_am to eliminate various hardcoded tests on AM OIDs, and remove unused pg_am columns. Fix rtree and gist index types to not attempt to store NULLs; before this, gist usually crashed, while rtree managed not to crash but computed wacko bounding boxes for NULL entries (which might have had something to do with the performance problems we've heard about occasionally). Add AtEOXact routines to hash, rtree, and gist, all of which have static state that needs to be reset after an error. We discovered this need long ago for btree, but missed the other guys. Oh, one more thing: concurrent VACUUM is now the default.
* Add ORDER BY to a couple of test queries whose output ordering is notTom Lane2001-07-15
| | | | | as predictable as it used to be, due to recycling of free space with new VACUUM.
* NLS for libpq. Clean up the message formats and change the documentationPeter Eisentraut2001-07-15
| | | | accordingly.
* Change xgettext rule to run in the source tree, so we don't have thePeter Eisentraut2001-07-15
| | | | | absolute paths of the source tree in the po files. Also, run msgfmt with -c option in maintainer-check.
* Make sure the build tree is before the source tree in the include path.Peter Eisentraut2001-07-15
|
* TODO item:Tatsuo Ishii2001-07-15
| | | | * Make n of CHAR(n)/VARCHAR(n) the number of letters, not bytes
* The attached patch fixes problems with the JDBC driver handling longBruce Momjian2001-07-15
| | | | | | | | | | | | | | | | | | | | | | | | null terminated strings. The FE/BE protocol sends in some cases null terminated strings to the client. The docs for the FE/BE protocol state that there is no limit on the size of a null terminated string sent to the client and a client should be coded using an expanding buffer to deal with large strings. The old code did not do this and gave an error if a null terminated string was greater than either 4 or 8K. It appears that with the advent of TOAST very long SQL statements are becoming more common, and apparently some error messages from the backend include the SQL statement thus easily exceeding the 8K limit in the old code. In fixing I also cleaned up some calls in the JDBC fastpath code that were not doing character set conversion under multibyte, and removed some methods that were no longer needed. I also removed a potential threading problem with a shared variable that was being used in Connection.java. Thanks to Steve Wampler for discovering the problem and sending the initial diffs that were the basis of this patch. thanks, --Barry
* Initial implementation of concurrent VACUUM. Ifdef'd out for the moment,Tom Lane2001-07-13
| | | | | because index locking issues are not handled correctly yet. Need to go work on the index AMs next.
* Minor code cleanup/beautification in RelationPutHeapTuple.Tom Lane2001-07-13
|
* indicies to indexes from Neil ConwayBruce Momjian2001-07-12
|
* Remove grammar restrictions on order of optional clauses in CREATE GROUP.Tom Lane2001-07-12
| | | | From Vince Vielhaber.