- 27 10月, 2007 4 次提交
-
-
由 Alvaro Herrera 提交于
to be locking another process (except when it's working to prevent Xid wraparound problems).
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
cases.
-
由 Tom Lane 提交于
if either of the input relations can legally be joined to any other rels using join clauses. This avoids uselessly (and expensively) considering a lot of really stupid join paths when there is a join restriction with a large footprint, that is, lots of relations inside its LHS or RHS. My patch of 15-Feb-2007 had been causing the code to consider joining *every* combination of rels inside such a group, which is exponentially bad :-(. With this behavior, clauseless bushy joins will be done if necessary, but they'll be put off as long as possible. Per report from Jakub Ouhrabka. Backpatch to 8.2. We might someday want to backpatch to 8.1 as well, but 8.1 does not have the problem for OUTER JOIN nests, only for IN-clauses, so it's not clear anyone's very likely to hit it in practice; and the current patch doesn't apply cleanly to 8.1.
-
- 26 10月, 2007 7 次提交
-
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
Per gripe from Zdenek Kotala, though not exactly his patch.
-
由 Bruce Momjian 提交于
Jun Kuwamura
-
由 Bruce Momjian 提交于
Ulrich Kroener
-
由 Tom Lane 提交于
only on the 'language' part of the locale name, ignoring the country code. We may need to be smarter later when there are more built-in configurations, but for now this is good enough and avoids having to bloat the table.
-
由 Alvaro Herrera 提交于
transaction end, in case we decide to do a vacuum analyze (which is done in two xacts).
-
由 Tom Lane 提交于
the sequence. Also, make setval() with is_called = false not affect the currval state, either. Per report from Kris Jurka that an implicit ALTER SEQUENCE OWNED BY unexpectedly caused currval() to become valid. Since this isn't 100% backwards compatible, it will go into HEAD only; I'll put a more limited patch into 8.2.
-
- 25 10月, 2007 12 次提交
-
-
由 Alvaro Herrera 提交于
Also, remove redundant reset of for-wraparound PGPROC flag. Thanks to Tom Lane for noticing both bogosities.
-
由 Tom Lane 提交于
(Last night I copied-and-pasted from the WITH HOLD case, but that's wrong because of the bizarrely irregular syntax specified by the standard.)
-
由 Alvaro Herrera 提交于
-
由 Alvaro Herrera 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
in corner cases such as re-fetching a just-deleted row. We may be able to relax this someday, but let's find out how many people really care before we invest a lot of work in it. Per report from Heikki and subsequent discussion. While in the neighborhood, make the combination of INSENSITIVE and FOR UPDATE throw an error, since they are semantically incompatible. (Up to now we've accepted but just ignored the INSENSITIVE option of DECLARE CURSOR.)
-
由 Tom Lane 提交于
-
由 Alvaro Herrera 提交于
having several of them. Add two more flags: whether the process is executing an ANALYZE, and whether a vacuum is for Xid wraparound (which is obviously only set by autovacuum). Sneakily move the worker's recently-acquired PostAuthDelay to a more useful place.
-
由 Tom Lane 提交于
neglected to test whether an outer join's join-condition actually refers to the lower outer join it is looking at. (The comment correctly described what was supposed to happen, but the code didn't do it...) This often resulted in adding an unnecessary constraint on the join order of the two outer joins, which was bad enough. However, it also seems to expose a performance problem in an older patch (from 15-Feb): once we've decided that there is a join ordering constraint, we will start trying clauseless joins between every combination of rels within the constraint, which pointlessly eats up lots of time and space if there are numerous rels below the outer join. That probably needs to be revisited :-(. Per gripe from Jakub Ouhrabka.
-
由 Alvaro Herrera 提交于
-
由 Alvaro Herrera 提交于
with the next table on schedule instead of exiting, in all cases instead of just on query cancel. Add a errcontext() line indicating the activity of the worker to the error message when it is cancelled. Change the WorkerInfo struct to contain a pointer to the worker's PGPROC instead of just the PID. Add forgotten post-auth delays, per Simon Riggs. Also to autovac launcher.
-
由 Tom Lane 提交于
then-delete on the current cursor row. The basic fix is that nodeTidscan.c has to apply heap_get_latest_tid() to the current-scan-TID obtained from the cursor query; this ensures we get the latest row version to work with. However, since that only works if the query plan is a TID scan, we also have to hack the planner to make sure only that type of plan will be selected. (Formerly, the planner might decide to apply a seqscan if the table is very small. This change is probably a Good Thing anyway, since it's hard to see how a seqscan could really win.) That means the execQual.c code to support CurrentOfExpr as a regular expression type is dead code, so replace it with just an elog(). Also, add regression tests covering these cases. Note that the added tests expose the fact that re-fetching an updated row misbehaves if the cursor used FOR UPDATE. That's an independent bug that should be fixed later. Per report from Dharmendra Goyal.
-
- 24 10月, 2007 6 次提交
-
-
由 Tom Lane 提交于
really change anything. Per report from Itagaki Takahiro. Fix by Pavan Deolasee.
-
由 Tom Lane 提交于
and ts_stat(), per my recent suggestion. Also add a possibly-not-needed- but-can't-hurt check for NULL SPI_tuptable, before we try to dereference same.
-
由 Tom Lane 提交于
if there are zero rows to aggregate over, and the API seems both conceptually and notationally ugly anyway. We should look for something that improves on the tsquery-and-text-SELECT version (which is also pretty ugly but at least it works...), but it seems that will take query infrastructure that doesn't exist today. (Hm, I wonder if there's anything in or near SQL2003 window functions that would help?) Per discussion.
-
由 Tom Lane 提交于
Needed to accommodate different layout on some platforms (Debian for one). Heikki Linnakangas
-
由 Tom Lane 提交于
categories, as per discussion. asciiword (formerly lword) is still ASCII-letters-only, and numword (formerly word) is still the most general mixed-alpha-and-digits case. But word (formerly nlword) is now any-group-of-letters-with-at-least-one-non-ASCII, rather than all-non-ASCII as before. This is no worse than before for parsing mixed Russian/English text, which seems to have been the design center for the original coding; and it should simplify matters for parsing most European languages. In particular it will not be necessary for any language to accept strings containing digits as being regular "words". The hyphenated-word categories are adjusted similarly.
-
由 Magnus Hagander 提交于
SHGetFolderPath. This removes the direct dependency on shell32.dll and user32.dll, which eats a lot of "desktop heap" for each backend that's started. The desktop heap is a very limited resource, causing backends to no longer start once it's been exhausted. We still have indirect depdendencies on user32.dll through third party libraries, but those can't easily be removed. Dave Page
-
- 23 10月, 2007 6 次提交
-
-
由 Tom Lane 提交于
a later rewrite rule should change a subtree modified by an earlier one. Per my gripe of a few days ago.
-
由 Tom Lane 提交于
miscomputation of required palloc size. The crash could only occur if the input contained lexemes both with and without positions, which is probably not common in practice. The miscomputation would definitely result in wasted space. Also fix some inconsistent coding around alignment of strings and positions in a tsvector value; these errors could also lead to crashes given mixed with/without position data and a machine that's picky about alignment. And be more careful about checking for overflow of string offsets. Patch is only against HEAD --- I have not looked to see if same bugs are in back-branch contrib/tsearch2 code.
-
由 Tom Lane 提交于
James Shaw. Also update a couple of examples to reflect 8.3's improved plan-printing code.
-
由 Tom Lane 提交于
active dictionary and its output lexemes as separate columns, instead of smashing them into one text column, and lowercase the column names. Also, define the output rowtype using OUT parameters instead of a composite type, to be consistent with the other built-in functions.
-
由 Tom Lane 提交于
ITAGAKI Takahiro
-
由 Tom Lane 提交于
representation of DECLARE CURSOR. Report and fix by Heikki.
-
- 22 10月, 2007 5 次提交
-
-
由 Magnus Hagander 提交于
Per Greg Stark & Dave Page
-
由 Tom Lane 提交于
users of tsearch. This isn't meant to be permanent documentation, but to call out the areas that need either fixing or real documentation.
-
由 Tom Lane 提交于
versions of gcc (I'm seeing it with Apple's gcc 4.0.1). I think the reason we did not see this before was that the assert() macros in the regex code were all no-ops till recently.
-
由 Tom Lane 提交于
tsvector" when we are really parsing a tsquery. Report the bogus input, too. Make styles of some related error messages more consistent.
-
由 Tom Lane 提交于
more clearly, improve a lot of unclear descriptions, add some missing material. We still need a migration guide though.
-