aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
* Awhile back I wrote that freebsd.h was probably broken in the places whereTom Lane2003-01-01
| | | | | it diverged from netbsd.h and openbsd.h. This has now been confirmed. Accordingly, make all three exactly alike.
* Adjust Tcl-related code to compile cleanly with Tcl 8.4 (add const modifiers asTom Lane2002-12-30
| | | | needed). Some desultory const-ification of SPI interface to support this.
* Attached is a patch to provide makefiles, etc. to allow the compilationBruce Momjian2002-12-30
| | | | | | | of the libpq interface static and dynamic libraries with the freely downloadable Borland C++ compiler version 5.5 and/or C++ Builder. Lester Godwin
* Code review for transaction-safe-TRUNCATE patch: minor cleanups.Tom Lane2002-12-30
|
* Code review for CLUSTER ALL patch. Fix bogus locking, incorrect transactionTom Lane2002-12-30
| | | | stop/start nesting, other infelicities.
* Make use of TCL_INCLUDE_SPEC if available (it's new in Tcl 8.4, too badTom Lane2002-12-30
| | | | it took 'em this long to realize it's needed...)
* Cause FETCH 1 to return the current cursor row, or zero if atBruce Momjian2002-12-30
| | | | | | | | | | | | beginning/end of cursor. Have MOVE return 0/1 depending on cursor position. Matches SQL spec. Pass cursor counter from parser as a long rather than int. Doc updates.
* Better solution to integer overflow problem in hash batch-numberTom Lane2002-12-30
| | | | | | | computation: reduce the bucket number mod nbatch. This changes the association between original bucket numbers and batches, but that doesn't matter. Minor other cleanups in hashjoin code to help centralize decisions.
* Add missing slash to python install path.Bruce Momjian2002-12-30
|
* Point does not return a center of lseg.Tom Lane2002-12-30
| | | | Kenji Sugita
* Adjust hash table sizing algorithm to avoid integer overflow inTom Lane2002-12-29
| | | | | ExecHashJoinGetBatch(). Fixes core dump on large hash joins, as in example from Rae Stiening.
* Deliver better error message when a relation name is used in an expression.Tom Lane2002-12-27
| | | | Per report from Ian Barwick.
* Remove overenthusiastic free'ing of comment dependencies; could lead toTom Lane2002-12-27
| | | | core dump in pg_dump when dumping views having comments. See bug #855.
* Trivial patch to increase max_fsm_pages as per earlier discussion.Bruce Momjian2002-12-27
| | | | Philip Warner
* Clamp the output of estimate_hash_bucketsize() to a sane range;Tom Lane2002-12-26
| | | | per example from Bruno Wolff in which it produced a silly result.
* Don't try to free executor state of an InitPlan early --- this breaksTom Lane2002-12-26
| | | | EXPLAIN ANALYZE. (Premature optimization is the root of all evil?)
* Update SSL error message for improper permissions. Backpatch to 7.3.X.Bruce Momjian2002-12-23
|
* case sensitive updates by Kris JurkaDave Cramer2002-12-23
|
* pg_dump should consider information_schema to be a system schema.Tom Lane2002-12-21
| | | | | | Also, tweak -C option (emit CREATE DATABASE command) to emit encoding name rather than encoding number, for consistency with pg_dumpall and better cross-version portability.
* Fix possible buffer overrun in \d command: substr(..., 128) producesTom Lane2002-12-21
| | | | | | 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.
* mike beachy's patch for statement handlingDave Cramer2002-12-20
|
* patch for null table in getPrimaryKeysDave Cramer2002-12-20
|
* Cause planner to include costs of InitPlans in startup cost of parentTom Lane2002-12-19
| | | | plan node. Not sure why this oversight has persisted so long ...
* pgindent fe-connect.c --- done to make IPv6 patch easier to apply.Bruce Momjian2002-12-19
|
* Update RELEASE checklist.Bruce Momjian2002-12-18
|
* From the SSL_CTX_new man page:PostgreSQL Daemon2002-12-18
| | | | | | | | | | | | | "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 ...
* Update EvalPlanQual() to work with new executor memory management method.Tom Lane2002-12-18
| | | | It doesn't leak memory anymore ...
* Prevent core dump when ExecMarkPos is called before any tuples have beenTom Lane2002-12-18
| | | | | retrieved. This cannot happen in ordinary execution, but it can happen under EvalPlanQual().
* Skip unnecessary plan-copying now that plan trees are read-only in theTom Lane2002-12-17
| | | | executor.
* Fix typo.Tom Lane2002-12-17
|
* To suppress memory leakage in long-lived Lists, lremove() should pfreeTom Lane2002-12-17
| | | | | the cons cell it's deleting from the list. Do this, and fix a few callers that were bogusly assuming it wouldn't free the cons cell.
* Fix GEQO to work again in CVS tip, by being more careful about memoryTom Lane2002-12-16
| | | | | | | | | | | allocation in best_inner_indexscan(). While at it, simplify GEQO's interface to the main planner --- make_join_rel() offers exactly the API it really wants, whereas calling make_rels_by_clause_joins() and make_rels_by_clauseless_joins() required jumping through hoops. Rewrite gimme_tree for clarity (sometimes iteration is much better than recursion), and approximately halve GEQO's runtime by recognizing that tours of the forms (a,b,c,d,...) and (b,a,c,d,...) are equivalent because of symmetry in make_join_rel().
* Fix ALTER TABLE ADD COLUMN to disallow the same column types that areTom Lane2002-12-16
| | | | | | | | 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.
* Code review for palloc0 patch --- avoid dangerous and unnecessaryTom Lane2002-12-16
| | | | | | | | practice of evaluating MemSet's arguments multiple times, except for the special case of newNode(), where we can assume the argument is a constant sizeof() operator. Also, add GetMemoryChunkContext() to mcxt.c's API, in preparation for fixing recent GEQO breakage.
* Tweak default memory context allocation policy so that a context is notTom Lane2002-12-15
| | | | | | | | | given any malloc block until something is first allocated in it; but thereafter, MemoryContextReset won't release that first malloc block. This preserves the quick-reset property of the original policy, without forcing 8K to be allocated to every context whether any of it is ever used or not. Also, remove some more no-longer-needed explicit freeing during ExecEndPlan.
* Revise executor APIs so that all per-query state structure is built inTom Lane2002-12-15
| | | | | | a per-query memory context created by CreateExecutorState --- and destroyed by FreeExecutorState. This provides a final solution to the longstanding problem of memory leaked by various ExecEndNode calls.
* Add major/minor release changes info to RELEASE_CHANGES file.Bruce Momjian2002-12-14
|
* The actual segfault was caused by a double pfree(), but ISTM thatBruce Momjian2002-12-14
| | | | | | | | 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
* Ok, I think I've gotten this figured out now. I saw this comment inBruce Momjian2002-12-14
| | | | | | | 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
* Initial version of the SQL information schemaPeter Eisentraut2002-12-14
|
* Clean up plantree representation of SubPlan-s --- SubLink does not appearTom Lane2002-12-14
| | | | | | | | in the planned representation of a subplan at all any more, only SubPlan. This means subselect.c doesn't scribble on its input anymore, which seems like a good thing; and there are no longer three different possible interpretations of a SubLink. Simplify node naming and improve comments in primnodes.h. No change to stored rules, though.
* Increment libpq major number for 7.3.1 and minor for 7.4.Bruce Momjian2002-12-13
|
* Admit defeat on the prospect of keeping straight exactly which platformsTom Lane2002-12-13
| | | | | | | | produce which output in the geometry test, even with the problem narrowed down to only whether they print minus zero or not. Instead, use pg_regress' locale-variant mechanism to automatically consider the test to pass if it matches either supplied comparison file. geometry_1.out replaces the former geometry-positive-zeros.out.
* Protect from null param on ecpg disconnect, verified by Roland KarchBruce Momjian2002-12-13
|
* Add a basic regression test for IS DISTINCT FROM, which has spent way tooTom Lane2002-12-13
| | | | much time in a broken state for lack of anyone noticing.
* Phase 3 of read-only-plans project: ExecInitExpr now builds expressionTom Lane2002-12-13
| | | | | | | execution state trees, and ExecEvalExpr takes an expression state tree not an expression plan tree. The plan tree is now read-only as far as the executor is concerned. Next step is to begin actually exploiting this property.
* Adjust costsize calculations to avoid introducing unnecessary roundoffTom Lane2002-12-13
| | | | | error. This seems to explain the differing choice of plan that's been causing geometry regress test to fail for the last few days.
* Remove strerror output for openssl SYSCALL error check.Bruce Momjian2002-12-13
|
* Here's the patch I mentioned on HACKERS to fix up ALTER command tabBruce Momjian2002-12-13
| | | | | | | | | | completion. Note that it's based on 7.3 tarball, not CVS HEAD, or 7.3rel branch. Damn, looking at CVS, this will patch into 7.3rel (just tested, it does) probably collide with Rod Taylor's patch adding ALTER TRIGGER stuff. O.K, second patch attached against HEAD - not tested, hand merged. Ross Reedstrom
* > There is an ugly little problem with the DB wrapper class.Bruce Momjian2002-12-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | > > In pg.py the attributes of DB are defined as being the same as > the attributes of the corresponding pgobject "db", using the following ... > The problem is that the attributes of db (which are read only) > are not static (they are actually function calls to PostgreSQL), > especially "status" and "error", but those attributes are copied > and this is done only once when initializing the DB object. > > So, in effect, only the attribute "db.error" of a DB instance > will be updated, but not the attribute "error". Same with "status". > Don't copy the (read only) attributes of the pgobject to the > DB object, but only the methods, and all of them, like this: > > --------------- change in pg.py ------------------ > # Create convience methods, in a way that is still overridable. > for e in self.db.__methods__: > setattr(self, e, getattr(self.db, e)) > ---------------------------------------------------- > > Furthermore, make an addition to the documentation of the > DB wrapper class (i.e. in pygresql-pg-db.html): > After the sentence "All pgobject methods are included in this class also." > add the following sentence "The pgobject read-only attributes can be > accessed py adding the prefix 'db.' to them." Christoph Zwerschke
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-02 01:52:36 +0000