- 15 12月, 2006 6 次提交
-
-
由 Bruce Momjian 提交于
time.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
correct, add comments about other multiple runs in the Makefile. Backpatch to 8.2.X.
-
由 Tom Lane 提交于
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
necessary.
-
- 13 12月, 2006 7 次提交
-
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
< * 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
-
由 Tom Lane 提交于
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.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
< * Allow REINDEX CONCURRENTLY
-
由 Bruce Momjian 提交于
> * Allow REINDEX CONCURRENTLY
-
由 Peter Eisentraut 提交于
works, but some platform templates overwrote it without asking.
-
- 12 12月, 2006 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
NULLs.
-
- 11 12月, 2006 3 次提交
-
-
由 Tom Lane 提交于
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 ...
-
由 Peter Eisentraut 提交于
US letter paper formats.
-
由 Peter Eisentraut 提交于
file (instead of repeating), add XSL-FO stylesheet and appropriate make rules.
-
- 10 12月, 2006 3 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
the build time by what seemed like infinity.
-
由 Peter Eisentraut 提交于
build rules.
-
- 09 12月, 2006 2 次提交
-
-
由 Tom Lane 提交于
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
-
由 Tom Lane 提交于
-
- 08 12月, 2006 3 次提交
-
-
由 Neil Conway 提交于
the nonexistent ShowStats variable is simply removed, per Gavin Sherry.
-
由 Tom Lane 提交于
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.
-
由 Tom Lane 提交于
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.
-
- 07 12月, 2006 3 次提交
-
-
由 Tom Lane 提交于
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.
-
由 Neil Conway 提交于
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.
-
由 Neil Conway 提交于
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.
-
- 06 12月, 2006 6 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Simon Riggs. Backpatch to 8.2.X.
-
由 Neil Conway 提交于
Rembialkowski, with some additional fixes by myself.
-
- 05 12月, 2006 3 次提交
-
-
由 Bruce Momjian 提交于
Simon Riggs
-
由 Bruce Momjian 提交于
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
-
由 Bruce Momjian 提交于
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
-
- 04 12月, 2006 2 次提交
-
-
由 Teodor Sigaev 提交于
Previous versions aren't affected. Fix synonym dictionary init: string should be malloc'ed, not palloc'ed. Bug introduced recently while fixing lowerstr().
-
由 Tom Lane 提交于
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 ...
-