aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* Add comments on WSAStartup usage.Bruce Momjian2005-05-05
|
* Add WSACleanup() for Win32 socket cleanup.Bruce Momjian2005-05-05
| | | | Jason Erickson
* The issue has been raised in the past that our build system links eachNeil Conway2005-05-05
| | | | | | | | | | | | | | executable against the maximal set of libraries it might need. So for example, if one executable requires `libreadline', all executables are linked against it. The easiest fix is to make use of GNU ld's --as-needed flag, which ignores linker arguments that are not actually needed by the specified object files. The attached patch modifies configure to check for this flag (when using GNU ld), and if ld supports it, adds the flag to LDFLAGS (we need to do the check since only relatively recent versions of GNU ld support this capability). Currently only GNU ld is supported; I'm not aware of any other linkers that support this functionality.
* Adjust nodeBitmapIndexscan to keep the target index opened from planTom Lane2005-05-05
| | | | | | | | | startup to end, rather than re-opening it in each MultiExecBitmapIndexScan call. I had foolishly thought that opening/closing wouldn't be much more expensive than a rescan call, but that was sheer brain fade. This seems to fix about half of the performance lossage reported by Sergey Koposov. I'm still not sure where the other half went.
* Update "control" item.Bruce Momjian2005-05-05
| | | | Rosser Schwarz
* Typo fix, Dave HeldBruce Momjian2005-05-05
|
* Allow implicit cast from any named composite type to RECORD. At theTom Lane2005-05-05
| | | | | | | moment this has no particular use except to allow table rows to be passed to record_out(), but that case seems to be useful in itself per recent example from Elein. Further down the road we could look at letting PL functions be declared to accept RECORD parameters.
* Use postmaster_is_alive() check in pg_ctl restart as well as pg_ctl status,Tom Lane2005-05-04
| | | | so that restart doesn't fail when old postmaster died unbetimes.
* Preliminary release notes for 8.0.3, 7.4.8, 7.3.10.Tom Lane2005-05-04
|
* Spell DELIMITER correctly, per Seamus Dean.Tom Lane2005-05-04
|
* Clean up MultiXactIdExpand's API by separating out the case where weTom Lane2005-05-03
| | | | | are creating a new MultiXactId from two regular XIDs. The original coding was unnecessarily complicated and didn't save any code anyway.
* Alter the signature for encoding conversion functions to declare theTom Lane2005-05-03
| | | | | | output area as INTERNAL not CSTRING. This is to prevent people from calling the functions by hand. This is a permanent solution for the back branches but I hope it is just a stopgap for HEAD.
* Change tsearch2 to not use the unsafe practice of creating functionsTom Lane2005-05-03
| | | | | | | | that return INTERNAL without also having INTERNAL arguments. Since the functions in question aren't meant to be called by hand anyway, I just redeclared them to take 'internal' instead of 'text'. Also add code to ProcedureCreate() to enforce the restriction, as I should have done to start with :-(
* Fix typos in documentation.Neil Conway2005-05-03
|
* Add FAQ on who controls the project.Bruce Momjian2005-05-02
|
* Completed:Bruce Momjian2005-05-02
| | | | | < * Remove unreferenced table files created by transactions that were > * -Check for unreferenced table files created by transactions that were
* Check the file system on postmaster startup and report any unreferencedBruce Momjian2005-05-02
| | | | | | files in the server log. Heikki Linnakangas
* Add some missing "See Also" entries to the domain-related SQL referenceNeil Conway2005-05-02
| | | | pages. From Robert Treat.
* Change SPI functions to use a `long' when specifying the number of tuplesNeil Conway2005-05-02
| | | | | | | | to produce when running the executor. This is consistent with the internal executor APIs (such as ExecutorRun), which also use a long for this purpose. It also allows FETCH_ALL to be passed -- since FETCH_ALL is defined as LONG_MAX, this wouldn't have worked on platforms where int and long are of different sizes. Per report from Tzahi Fadida.
* Change CREATE TYPE to require datatype output and send functions to haveTom Lane2005-05-01
| | | | | | | only one argument. (Per recent discussion, the option to accept multiple arguments is pretty useless for user-defined types, and would be a likely source of security holes if it was used.) Simplify call sites of output/send functions to not bother passing more than one argument.
* Fix incorrect backslashing in regexp example, per Robert Treat.Tom Lane2005-05-01
|
* Mention the actual stored size of NUMERIC values, per David Fetter.Tom Lane2005-05-01
|
* Remove the contents of the src/corba subdirectory: this has been dead codeNeil Conway2005-05-01
| | | | for a long time.
* Change catalog entries for record_out and record_send to show only oneTom Lane2005-04-30
| | | | | | argument, since that's all they are using now. Adjust type_sanity regression test so that it will complain if anyone tries to define multiple-argument output functions in future.
* Make record_out and record_send extract type information from the passedTom Lane2005-04-30
| | | | | | | record object itself, rather than relying on a second OID argument to be correct. This patch just changes the function behavior and not the catalogs, so it's OK to back-patch to 8.0. Will remove the now-redundant second argument in pg_proc in a separate patch in HEAD only.
* Use the standard lock manager to establish priority order when thereTom Lane2005-04-30
| | | | | | is contention for a tuple-level lock. This solves the problem of a would-be exclusive locker being starved out by an indefinite succession of share-lockers. Per recent discussion with Alvaro.
* GCC 4.0 includes a new warning option, -Wformat-literal, that emitsNeil Conway2005-04-30
| | | | | | | | | | | | | | | a warning when a variable is used as a format string for printf() and similar functions (if the variable is derived from untrusted data, it could include unexpected formatting sequences). This emits too many warnings to be enabled by default, but it does flag a few dubious constructs in the Postgres tree. This patch fixes up the obvious variants: functions that are passed a variable format string but no additional arguments. Most of these are harmless (e.g. the ruleutils stuff), but there is at least one actual bug here: if you create a trigger named "%sfoo", pg_dump will read uninitialized memory and fail to dump the trigger correctly.
* Fix BCC to not define compiler location.Bruce Momjian2005-04-30
|
* Update FAQ.Bruce Momjian2005-04-30
|
* Update replication FAQ.Bruce Momjian2005-04-30
| | | | Christopher Browne
* Restructure LOCKTAG as per discussions of a couple months ago.Tom Lane2005-04-29
| | | | | | | | | | | | | | Essentially, we shoehorn in a lockable-object-type field by taking a byte away from the lockmethodid, which can surely fit in one byte instead of two. This allows less artificial definitions of all the other fields of LOCKTAG; we can get rid of the special pg_xactlock pseudo-relation, and also support locks on individual tuples and general database objects (including shared objects). None of those possibilities are actually exploited just yet, however. I removed pg_xactlock from pg_class, but did not force initdb for that change. At this point, relkind 's' (SPECIAL) is unused and could be removed entirely.
* Remove extern from optreset that was just added.Bruce Momjian2005-04-29
|
* Improve cleanup from win32 client-only build.Bruce Momjian2005-04-29
|
* Backpatch BCC compile changes to 8.0.X for psql.Bruce Momjian2005-04-29
|
* This patch fixes a bug in the error message emitted by pg_restore on anNeil Conway2005-04-29
| | | | | incorrect -F argument: write_msg() expects its first parameter to be a "module name", not the format string.
* Done:Bruce Momjian2005-04-29
| | | | > * -Implement shared row locks and use them in RI triggers
* Implement sharable row-level locks, and use them for foreign key referencesTom Lane2005-04-28
| | | | | | | | | | | | | | | to eliminate unnecessary deadlocks. This commit adds SELECT ... FOR SHARE paralleling SELECT ... FOR UPDATE. The implementation uses a new SLRU data structure (managed much like pg_subtrans) to represent multiple- transaction-ID sets. When more than one transaction is holding a shared lock on a particular row, we create a MultiXactId representing that set of transactions and store its ID in the row's XMAX. This scheme allows an effectively unlimited number of row locks, just as we did before, while not costing any extra overhead except when a shared lock actually has to be shared. Still TODO: use the regular lock manager to control the grant order when multiple backends are waiting for a row lock. Alvaro Herrera and Tom Lane.
* Fix a whitespace problem. From Alvaro Herrera.Dennis Bjorklund2005-04-28
|
* Add WAL compression item to TODO.detail.Bruce Momjian2005-04-28
|
* Add psql \set ON_ERROR_ROLLBACK to allow statements in a transaction toBruce Momjian2005-04-28
| | | | | error without affecting the entire transaction. Valid values are "on|interactive|off".
* Wording improvement.Bruce Momjian2005-04-27
|
* Update PAM documentation, per Alvaro.Bruce Momjian2005-04-27
|
* Mention that PAM requires the user already exist in the database, perBruce Momjian2005-04-26
| | | | Dick Davies.
* On further experimentation, there were still a couple of bugs inTom Lane2005-04-25
| | | | ExpandIndirectionStar() ... and in markTargetListOrigin() too.
* Fix ExpandIndirectionStar to handle cases where the expression to beTom Lane2005-04-25
| | | | | | expanded is of RECORD type, eg 'select (foo).* from (select foo(f1) from t1) ss' where foo() is a function declared with multiple OUT parameters.
* get_expr_result_type probably needs to be able to handle OpExpr as wellTom Lane2005-04-25
| | | | | as FuncExpr, to cover cases where a function returning tuple is invoked via an operator.
* Update description:Bruce Momjian2005-04-25
| | | | | | | | | | < * Allow ORDER BY ... LIMIT 1 to select high/low value without sort or > * Allow ORDER BY ... LIMIT # to select high/low value without sort or 868c868 < Right now, if no index exists, ORDER BY ... LIMIT 1 requires we sort > Right now, if no index exists, ORDER BY ... LIMIT # requires we sort 870a871 > MIN/MAX already does this, but not for LIMIT > 1.
* Re-add item with better description:Bruce Momjian2005-04-25
| | | | | | | | | | > * Allow ORDER BY ... LIMIT 1 to select high/low value without sort or > index using a sequential scan for highest/lowest values > > Right now, if no index exists, ORDER BY ... LIMIT 1 requires we sort > all values to return the high/low value. Instead The idea is to do a > sequential scan to find the high/low value, thus avoiding the sort. >
* Fix btree_gist to handle timetz zone correctly per recent changes.Tom Lane2005-04-25
|
* Avoid rechecking lossy operators twice in a bitmap scan plan.Tom Lane2005-04-25
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-05 12:04:31 +0000