aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* Be more realistic about plans involving Materialize nodes: take theirTom Lane2002-11-30
| | | | cost into account while planning.
* Make install and clean targets behave more normally.Tom Lane2002-11-30
|
* Upgrade planner and executor to allow multiple hash keys for a hash join,Tom Lane2002-11-30
| | | | | | instead of only one. This should speed up planning (only one hash path to consider for a given pair of relations) as well as allow more effective hashing, when there are multiple hashable joinclauses.
* Tighten selection of equality and ordering operators for groupingTom Lane2002-11-29
| | | | | | | operations: make sure we use operators that are compatible, as determined by a mergejoin link in pg_operator. Also, add code to planner to ensure we don't try to use hashed grouping when the grouping operators aren't marked hashable.
* Repair prehistoric logic error in lseg_eq and lseg_ne.Tom Lane2002-11-29
|
* Suppress compiler warning from newer gcc.Tom Lane2002-11-29
|
* This patch fixes two tiny memory leaks in pg_dump and two in pg_dumpall.Bruce Momjian2002-11-29
| | | | Neil Conway
* Add trigger emails.Bruce Momjian2002-11-28
|
* rm should be rm -f, per comment from Peter Harris.Tom Lane2002-11-27
| | | | (Checked with Peter Eisentraut.)
* Improve some comments.Tom Lane2002-11-27
|
* Add note that scaling factor should be >= # of clients.Tom Lane2002-11-27
|
* Synced parser with backendMichael Meskes2002-11-27
|
* Move to URGENT, for Justin:Bruce Momjian2002-11-26
| | | | < * Create native Win32 port [win32]
* Recreate HISTORY file to match release.sgml changes. Stamp 7.3 final inBruce Momjian2002-11-26
| | | | configure/configure.in.
* Add -cmdTuples to tcl interface.Bruce Momjian2002-11-26
|
* Update trigger discussion.Bruce Momjian2002-11-26
|
* Update build rules for /HISTORY.Bruce Momjian2002-11-26
|
* Add to trigger thread.Bruce Momjian2002-11-26
|
* Fix typo in release notes.Bruce Momjian2002-11-26
|
* Allocate proper length for sprintf string, from Tatsuo.Bruce Momjian2002-11-26
|
* Use Params, rather than run-time-modified Const nodes, to handleTom Lane2002-11-26
| | | | | | | sublink results and COPY's domain constraint checking. A Const that isn't really constant is just a Bad Idea(tm). Remove hacks in parse_coerce and other places that were needed because of the former klugery.
* Guard against 0 length string encoding conversion case.Tatsuo Ishii2002-11-26
|
* Remove check for pg_group file as part of initdb -W password assignmentBruce Momjian2002-11-25
| | | | --- not needed.
* Remove unused constisset and constiscast fields of Const nodes. CleanTom Lane2002-11-25
| | | | up code and documentation associated with Param nodes.
* Restructure outfuncs and readfuncs to use macros in the same style asTom Lane2002-11-25
| | | | | | | | just done for copyfuncs/equalfuncs. Read functions in particular get a lot shorter than before, and it's much easier to compare an out function with the corresponding read function to make sure they agree. initdb forced due to small changes in nodestring format (regularizing a few cases that were formerly idiosyncratic).
* Un-break triggers declared for INSERT OR DELETE OR UPDATE. This workedTom Lane2002-11-25
| | | | | okay in 7.3, so I think it must have been busted in the recent triggers patch.
* Restructure the code in copyfuncs and equalfuncs to put much heavierTom Lane2002-11-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | reliance on macros, in hopes of eliminating silly typos (like copying to the wrong field) and just generally making it easier to see the forest instead of the trees. As an example, here is the new code for A_Indices: static A_Indices * _copyAIndices(A_Indices *from) { A_Indices *newnode = makeNode(A_Indices); COPY_NODE_FIELD(lidx); COPY_NODE_FIELD(uidx); return newnode; } static bool _equalAIndices(A_Indices *a, A_Indices *b) { COMPARE_NODE_FIELD(lidx); COMPARE_NODE_FIELD(uidx); return true; } I plan to redo outfuncs/readfuncs in a similar style, but am committing what I've got.
* I'm sending you a small patch to pgdb.py module. ThisD'Arcy J.M. Cain2002-11-25
| | | | | | | | | | | | | | raises pgdb.DatabaseError when any of the fetch* methods was invoked but previous call to execute* did not produce any result set or no call was issued yet. Also, raises pgdb.NotSupportedError when .nextset() is invoked, instead of NameError. This behaviour complies with DB-API 2.0. Thanks for your work! Timur Irmatov.
* Change the pkey method so that the caller can optionally set the dictionaryD'Arcy J.M. Cain2002-11-25
| | | | | | | | | used for the primary key lookup. This will prevent a database lookup for each connection object that gets created. This could be a significant optimization on a busy system. Similarly, the get_attnames method allows for the attributes dictionary to be installed directly.
* Change the debug variable to allow better control by the caller over howD'Arcy J.M. Cain2002-11-25
| | | | | | | | | | | | | debug output is managed. The user can continue to use the current method of passing a formatting string to have a replacement done and output will be sent to the standard output exactly as it did before. In addition they can set it to a file object, sys.stderr for example, and the query string will be printed to it. Thay can also set it to a method (function) and the query string will be passed to that method giving them the maximum flexibility to do whatever they want with the query string. I will be working with the PyGreSQL documentation shortly and at that time will properly document this feature.
* Restructure planning of nestloop inner indexscans so that the set of usableTom Lane2002-11-24
| | | | | | | | | | | joinclauses is determined accurately for each join. Formerly, the code only considered joinclauses that used all of the rels from the outer side of the join; thus for example FROM (a CROSS JOIN b) JOIN c ON (c.f1 = a.x AND c.f2 = b.y) could not exploit a two-column index on c(f1,f2), since neither of the qual clauses would be in the joininfo list it looked in. The new code does this correctly, and also is able to eliminate redundant clauses, thus fixing the problem noted 24-Oct-02 by Hans-Jürgen Schönig.
* 7.4devel now supports SQL:1999's "enhanced trigger capability" (whichBruce Momjian2002-11-24
| | | | | | | is just FOR EACH STATEMENT triggers, AFAICS); this patch updates the SQL conformance docs to note that. Neil Conway
* Split:Bruce Momjian2002-11-24
| | | | | > * -Support statement-level triggers (Neil) > * Support triggers on columns (Neil)
* Fix inappropriate quoting in dblink. From Joe Conway.Tom Lane2002-11-23
|
* Fix regression test breakage from triggers patch.Tom Lane2002-11-23
|
* Fix compile warnings from truncate patch.Tom Lane2002-11-23
|
* Update regression for new patches. Bump up catversion.Bruce Momjian2002-11-23
|
* Heres a patch which will create the sql_help.h file on Win32 if itBruce Momjian2002-11-23
| | | | | | | doesn't already exist using an installed copy of perl. I've tested it using perl v5.6.1 from ActiveState and all appears to work. Al Sutton
* Transaction safe TruncateBruce Momjian2002-11-23
| | | | Rod Taylor
* This minor patch corrects an error in the function docs: it'sBruce Momjian2002-11-23
| | | | | | "version()", not "version". Neil Conway
* This patch implements FOR EACH STATEMENT triggers, per my email toBruce Momjian2002-11-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | -hackers a couple days ago. Notes/caveats: - added regression tests for the new functionality, all regression tests pass on my machine - added pg_dump support - updated PL/PgSQL to support per-statement triggers; didn't look at the other procedural languages. - there's (even) more code duplication in trigger.c than there was previously. Any suggestions on how to refactor the ExecXXXTriggers() functions to reuse more code would be welcome -- I took a brief look at it, but couldn't see an easy way to do it (there are several subtly-different versions of the code in question) - updated the documentation. I also took the liberty of removing a big chunk of duplicated syntax documentation in the Programmer's Guide on triggers, and moving that information to the CREATE TRIGGER reference page. - I also included some spelling fixes and similar small cleanups I noticed while making the changes. If you'd like me to split those into a separate patch, let me know. Neil Conway
* Done:Bruce Momjian2002-11-23
| | | | > * -Support statement-level triggers and triggers on columns (Neil)
* When I made the cube(text) function for 7.3, I neglected to add aBruce Momjian2002-11-23
| | | | | | | matching create cast command. The attached diff adds a create cast as assignment to cube.sql.in . Bruno Wolff III
* Update ports list from recent regression-test-database entries.Tom Lane2002-11-23
|
* This is a patch to make cube output work like double precision outputBruce Momjian2002-11-23
| | | | | | | | | with regard to the extra_float_digits setting. Since builtins.h was already included, I just deleted the extern statement (and accompaning comments). Bruno Wolff III
* Release note improvements (Neil, Tom)Tom Lane2002-11-23
|
* Remove inappropriate double-quoting in connectby() code; adjustTom Lane2002-11-23
| | | | regression test to avoid using VALUE as a name. From Joe Conway.
* Redesign internal logic of nodeLimit so that it does not need to fetchTom Lane2002-11-22
| | | | | | one more row from the subplan than the COUNT would appear to require. This costs a little more logic but a number of people have complained about the old implementation.
* Fix a dozen or so places that were passing unpredictable data stringsTom Lane2002-11-22
| | | | | as elog format strings. Hai-Chen Tu pointed out the problem in contrib/dbmirror, but it wasn't the only such error.
* Fix elog in dbmirror to use %s.Bruce Momjian2002-11-22
| | | | Hai-Chen Tu
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-07 01:35:41 +0000