aboutsummaryrefslogtreecommitdiff
path: root/src/backend
Commit message (Collapse)AuthorAge
* 1. null-safe interface to GiSTBruce Momjian2001-08-10
| | | | | | | | | | | | | | (as proposed in http://fts.postgresql.org/db/mw/msg.html?mid=1028327) 2. support for 'pass-by-value' arguments - to test this we used special opclass for int4 with values in range [0-2^15] More testing will be done after resolving problem with index_formtuple and implementation of B-tree using GiST 3. small patch to contrib modules (seg,cube,rtree_gist,intarray) - mark functions as 'isstrict' where needed. Oleg Bartunov
* Patch to LOCK multiple tables in one LOCK command.Bruce Momjian2001-08-10
| | | | Neil Padgett
* Use format_type sibling in backend error messages, so the user seesPeter Eisentraut2001-08-09
| | | | consistent type naming.
* No longer a need for -Wno-errorPeter Eisentraut2001-08-09
|
* A small patch to keep postgres working on the latest BeOS.Bruce Momjian2001-08-07
| | | | Cyril VELTER
* Fix thinko (revealed by gcc warning).Tom Lane2001-08-07
|
* Add a check for end of client connection before expecting a passwordPeter Eisentraut2001-08-07
| | | | response, to avoid noise in the server log.
* Use a fixed error message for ERANGE to avoid duplicate test result files.Peter Eisentraut2001-08-06
| | | | Add some resultmap entries for SCO OpenServer.
* Seems like a bad idea to free() a string we are about to use in anTom Lane2001-08-06
| | | | error message.
* Modify partial-index-predicate applicability tester to test whetherTom Lane2001-08-06
| | | | | | clauses are equal(), before trying to match them up using btree opclass inference rules. This allows it to recognize many simple cases involving non-btree operations, for example 'x IS NULL'. Clean up code a little.
* Evaluate LIMIT/OFFSET expressions with ExecEvalExprSwitchContext, notTom Lane2001-08-06
| | | | ExecEvalExpr, to avoid possible memory leak.
* Check that the data directory does not have group or world access; removePeter Eisentraut2001-08-06
| | | | a similar check on postgresql.conf.
* Add QueryIsRule gram.y reset.Bruce Momjian2001-08-06
|
* Endeavor to make pgstats buffer process (a) safe and (b) useful.Tom Lane2001-08-05
| | | | | | | | Make sure it exits immediately when collector process dies --- in old code, buffer process would hang around and compete with the new buffer process for packets. Make sure it doesn't block on writing the pipe when the collector falls more than a pipeload behind. Avoid leaking pgstats FDs into every backend.
* Remove no-longer-needed fcntl call (I'm not sure it *ever* did anythingTom Lane2001-08-05
| | | | useful, in fact).
* Back out LOCK A,B,C patch at Tom's suggestion.Bruce Momjian2001-08-04
|
* This patch is because Hurd does not support NOFILE. It is against currentBruce Momjian2001-08-04
| | | | | | | | | | | | cvs. The Debian bug report says, "The upstream source makes use of NOFILE unconditionalized. As the Hurd doesn't have an arbitrary limit on the number of open files, this is not defined. But _SC_OPEN_MAX works fine and returns 1024 (applications can increase this as they want), so I suggest the below diff. Please forward this upstream, too." Oliver Elphick
* Add LOCK A,B,C functionality as LOCK A;LOCK B;LOCK C; as agreed.Bruce Momjian2001-08-04
| | | | Neil Padgett
* Fix handling of SIGCHLD, per recent pghackers discussion: on someTom Lane2001-08-04
| | | | | | | platforms system(2) gets confused unless the signal handler is set to SIG_DFL, not SIG_IGN. pgstats.c now uses pqsignal() as it should, not signal(). Also, arrange for the stats collector process to show a reasonable ID in 'ps', rather than looking like a postmaster.
* For some reason, CREATE TYPE has only accepted alignment specificationsTom Lane2001-08-03
| | | | | of 'int4' and 'double'. Add 'char' and 'int2' to allow user-defined types to access the full set of supported alignments.
* Add a SPI_copytupledesc function that parallels SPI_copytuple --- ie,Tom Lane2001-08-02
| | | | | it copies the tupdesc into upper-executor memory. This is necessary for returning tuple descriptors without leaking all of lower exec memory.
* Tweak memory context sizing for saved SPI plans.Tom Lane2001-08-02
|
* Fix some poor decisions about sizing of trigger-related memory contexts.Tom Lane2001-08-02
|
* 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.
* 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 info on pg_hba.conf comments.Bruce Momjian2001-07-31
|
* Fix unportable coding for FRONTEND case.Tom Lane2001-07-31
|
* 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
* Suppress gcc warning in USE_LOCALE case.Tom Lane2001-07-22
|
* Source formatting cleanup.Bruce Momjian2001-07-21
|
* 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.
* 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.
* 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.
* TODO item:Tatsuo Ishii2001-07-15
| | | | * Make n of CHAR(n)/VARCHAR(n) the number of letters, not bytes
* 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
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-05 16:46:57 +0000