aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* Update entry:Bruce Momjian2006-12-12
| | | | | | < * Have EXPLAIN ANALYZE highlight poor optimizer estimates > * Have EXPLAIN ANALYZE issue NOTICE messages when the estimated and > actual row counts differ by a specified percentage
* Fix planner to do the right thing when a degenerate outer join (one whoseTom Lane2006-12-12
| | | | | | | joinclause doesn't use any outer-side vars) requires a "bushy" plan to be created. The normal heuristic to avoid joins with no joinclause has to be overridden in that case. Problem is new in 8.2; before that we forced the outer join order anyway. Per example from Teodor.
* Document that log_line_prefix %t does not print timezone on Win32.Bruce Momjian2006-12-12
|
* Oops, removed:Bruce Momjian2006-12-12
| | | | < * Allow REINDEX CONCURRENTLY
* Add:Bruce Momjian2006-12-12
| | | | > * Allow REINDEX CONCURRENTLY
* Allow augmenting CPPFLAGS from the configure command line. This generallyPeter Eisentraut2006-12-12
| | | | works, but some platform templates overwrote it without asking.
* Remove blank lines in HTML FAQ.Bruce Momjian2006-12-11
|
* Add FAQ entry to mention using COALESCE() for concatenation of possibleBruce Momjian2006-12-11
| | | | NULLs.
* Add a paramtypmod field to Param nodes. This is dead weight for ParamsTom Lane2006-12-10
| | | | | | | | | | representing externally-supplied values, since the APIs that carry such values only specify type not typmod. However, for PARAM_SUBLINK Params it is handy to carry the typmod of the sublink's output column. This is a much cleaner solution for the recently reported 'could not find pathkey item to sort' and 'failed to find unique expression in subplan tlist' bugs than my original 8.2-compatible patch. Besides, someday we might want to support typmods for external parameters ...
* Make separate targets for building printable documentation in A4 andPeter Eisentraut2006-12-10
| | | | US letter paper formats.
* Reorganize XSLT stylesheet support. Put common things into a separatePeter Eisentraut2006-12-10
| | | | | file (instead of repeating), add XSL-FO stylesheet and appropriate make rules.
* Add some information about increasing JadeTeX parameters.Peter Eisentraut2006-12-10
|
* Drop indentation of verbatim environments in print output. This increasedPeter Eisentraut2006-12-10
| | | | the build time by what seemed like infinity.
* Generalize Texinfo rules. Prevent them from overriding the PostScriptPeter Eisentraut2006-12-10
| | | | build rules.
* Remove the logId/logSeg fields from pg_control, because they are not neededTom Lane2006-12-08
| | | | | | | | | | | | | | | | | | | in normal operation, and we can avoid rewriting pg_control at every log segment switch if we don't insist that these values be valid. Reducing the number of pg_control updates is a good idea for both performance and reliability. It does make pg_resetxlog's life a bit harder, but that seems a good tradeoff; and anyway the change to pg_resetxlog amounts to automating something people formerly needed to do by hand, namely look at the existing pg_xlog files to make sure the new WAL start point was past them. In passing, change the wording of xlog.c's "database system was interrupted" messages: describe the pg_control timestamp as "last known up at" rather than implying it is the exact time of service interruption. With this change the timestamp will generally be the time of the last checkpoint, which could be many minutes before the failure; and we've already seen indications that people tend to misinterpret the old wording. initdb forced due to change in pg_control layout. Simon Riggs and Tom Lane
* Fix broken markup.Tom Lane2006-12-08
|
* Fix the build for when SHOW_MEMORY_STATS is defined. The reference toNeil Conway2006-12-08
| | | | the nonexistent ShowStats variable is simply removed, per Gavin Sherry.
* Avoid double free of _SPI_current->tuptable. AtEOSubXact_SPI() now tries toTom Lane2006-12-08
| | | | | | | release it in a subtransaction abort, but this neglects possibility that someone outside SPI already did. Fix is for spi.c to forget about a tuptable as soon as it's handed it back to the caller. Per bug #2817 from Michael Andreen.
* Repair incorrect placement of WHERE clauses when there are multiple,Tom Lane2006-12-07
| | | | | | | rearrangeable outer joins and the WHERE clause is non-strict and mentions only nullable-side relations. New bug in 8.2, caused by new logic to allow rearranging outer joins. Per bug #2807 from Ross Cohen; thanks to Jeff Davis for producing a usable test case.
* Fix planning of SubLinks to ensure that Vars generated from transformation ofTom Lane2006-12-06
| | | | | | | | | | a sublink's test expression have the correct vartypmod, rather than defaulting to -1. There's at least one place where this is important because we're expecting these Vars to be exactly equal() to those appearing in the subplan itself. This is a pretty klugy solution --- it would likely be cleaner to change Param nodes to include a typmod field --- but we can't do that in the already-released 8.2 branch. Per bug report from Hubert Fongarnand.
* Add a txn_start column to pg_stat_activity. This makes it easier toNeil Conway2006-12-06
| | | | | | | | identify long-running transactions. Since we already need to record the transaction-start time (e.g. for now()), we don't need any additional system calls to report this information. Catversion bumped, initdb required.
* Various improvements to the GUC description strings. Punctuate andNeil Conway2006-12-06
| | | | | | capitalize the strings like sentences. Remove unnecessarily specific descriptions of the units used by GUC variables, since we now allow any reasonable unit to be specified.
* Change psql \\ example to use single quotes, per TOm.Bruce Momjian2006-12-06
|
* Back out mention of port success from FAQs, per Tom, added by Simon.Bruce Momjian2006-12-06
|
* Clean up psql -c documentation that uses \\.Bruce Momjian2006-12-06
|
* Make URL to docs use /current/.Bruce Momjian2006-12-05
|
* Fix documentation example of using psql \x with a SELECT command, perBruce Momjian2006-12-05
| | | | Simon Riggs. Backpatch to 8.2.X.
* Fix typos in comments and error messages in HStore. Patch from FilipNeil Conway2006-12-05
| | | | Rembialkowski, with some additional fixes by myself.
* Update of port patches, HEAD patch only.Bruce Momjian2006-12-05
| | | | Simon Riggs
* Fix pg_dump linking on Win32 with MSVS win32.mak:Bruce Momjian2006-12-04
| | | | | | | | | | | | | | The module link is insufficient.:-( ---- Sorry, japanese message change to xxx --- link.exe @C:\DOCUME~1\hi-saito\LOCALS~1\Temp\nmk03360. common.obj : error LNK2001: xxxxxx "_pg_qsort" xxxxxx pg_dump_sort.obj : error LNK2001: xxxxx "_pg_qsort" xxxxx .\Release\pg_dump.exe : fatal error LNK1120: xxxxxxx NMAKE : fatal error U1077: 'link.exe' : xxxxx '0x460' Stop. Hiroshi Saito
* Patch of Win32 Encoding problem for server messages usingBruce Momjian2006-12-04
| | | | | | | | | | | | | | | | | | | | | | | | FormatMessage() (This should have been in 8.2.0, patched to 8.2.X and HEAD): I think this problem to be complex.... http://archives.postgresql.org/pgsql-hackers/2006-11/msg00042.php FormatMessage of windows cannot consider the encoding of the database. However, I should try the solution now. It is necessary to clear the problem. Multi character-code exists together in message and log. It doesn't consider the data base encoding that the user intended.... The user in multi-byte country can try this. http://inet.winpg.jp/~saito/pg_bug/MessageCheck.c That is, it is likely to become it in this manner.(Japanese) http://inet.winpg.jp/~saito/pg_bug/FormatMessage998.png Hiroshi Saito
* Fix core dump of ispell for case of non-successfull initialization.Teodor Sigaev2006-12-04
| | | | | | | Previous versions aren't affected. Fix synonym dictionary init: string should be malloc'ed, not palloc'ed. Bug introduced recently while fixing lowerstr().
* Refactor ExecGetJunkAttribute to avoid searching for junk attributesTom Lane2006-12-04
| | | | | | by name on each and every row processed. Profiling suggests this may buy a percent or two for simple UPDATE scenarios, which isn't huge, but when it's so easy to get ...
* Fix LIMIT/OFFSET for null limit values. This worked before 8.2 but was brokenTom Lane2006-12-03
| | | | | | by the change to make limit values int8 instead of int4. (Specifically, you can do DatumGetInt32 safely on a null value, but not DatumGetInt64.) Per bug #2803 from Greg Johnson.
* Stamp HEAD as 8.3devel.Tom Lane2006-12-02
|
* Update most recent version from 8.2 to 8.2.0.Bruce Momjian2006-12-02
|
* Collect the bits of wisdom about dtrace installation in the installationPeter Eisentraut2006-12-02
| | | | chapter rather than scattering them across several incomplete fragments.
* v8.2.0 is now released ...REL8_2_0PostgreSQL Daemon2006-12-02
|
* Stamp 8.2, except configure.in.Bruce Momjian2006-12-02
|
* Update for release 8.2.Bruce Momjian2006-12-02
|
* Wording refinement for external references in man pages.Peter Eisentraut2006-12-02
|
* Don't ship spi_* man pages. (We don't do that anyway, but now it's automatic.)Peter Eisentraut2006-12-02
|
* Translation updatesPeter Eisentraut2006-12-02
|
* Put release date in release notes.Tom Lane2006-12-02
|
* Add some documentation for DTrace support. Simon RiggsTom Lane2006-12-02
|
* Make Options for Windows a second-level heading instead of first-level.Peter Eisentraut2006-12-02
|
* Editorial improvements for GIN documentation.Tom Lane2006-12-01
|
* Some more supported-platforms updates: buildfarm hare is alive again,Tom Lane2006-12-01
| | | | | and penguin reported in recently enough to justify the assumption that we haven't broken ARM support in 8.2.
* Document the recently-understood hazard that a rollback can release row-levelTom Lane2006-12-01
| | | | | | locks that logically should not be released, because when a subtransaction overwrites XMAX all knowledge of the previous lock state is lost. It seems unlikely that we will be able to fix this before 8.3...
* Make the bgwriter's error recovery path do smgrcloseall(). On Windows thisTom Lane2006-12-01
| | | | | | should allow delete-pending files to actually go away, and thereby work around the various complaints we've seen about 'permission denied' errors in such cases. Should be reasonably harmless in any case...
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-03 12:34:13 +0000