- 10 3月, 2007 1 次提交
-
-
由 Andrew Dunstan 提交于
-
- 04 3月, 2007 3 次提交
-
-
由 Neil Conway 提交于
with the recent largeobject cosmetic fixes. Jeremy Drake.
-
由 Bruce Momjian 提交于
Jeremy Drake
-
由 Bruce Momjian 提交于
Kris Jurka
-
- 17 2月, 2007 3 次提交
-
-
由 Bruce Momjian 提交于
Brendan Jurd
-
由 Bruce Momjian 提交于
as a performance enhancement. Mark Kirkwood
-
由 Alvaro Herrera 提交于
remove duplicated tests in timestamp, and complete timestamptz with the tests that were missing to more closely mirror timestamp.
-
- 16 2月, 2007 3 次提交
-
-
由 Alvaro Herrera 提交于
timestamp_tbl table into the timestamp test. Also, restore a test that used to exist as a valid test in the timestamptz test.
-
由 Bruce Momjian 提交于
to_timestamp(): - ID for day-of-week - IDDD for day-of-year This makes it possible to convert ISO week dates to and from text fully represented in either week ('IYYY-IW-ID') or day-of-year ('IYYY-IDDD') format. I have also added an 'isoyear' field for use with extract / date_part. Brendan Jurd
-
由 Tom Lane 提交于
considered when it is necessary to do so because of a join-order restriction (that is, an outer-join or IN-subselect construct). The former coding was a bit ad-hoc and inconsistent, and it missed some cases, as exposed by Mario Weilguni's recent bug report. His specific problem was that an IN could be turned into a "clauseless" join due to constant-propagation removing the IN's joinclause, and if the IN's subselect involved more than one relation and there was more than one such IN linking to the same upper relation, then the only valid join orders involve "bushy" plans but we would fail to consider the specific paths needed to get there. (See the example case added to the join regression test.) On examining the code I wonder if there weren't some other problem cases too; in particular it seems that GEQO was defending against a different set of corner cases than the main planner was. There was also an efficiency problem, in that when we did realize we needed a clauseless join because of an IN, we'd consider clauseless joins against every other relation whether this was sensible or not. It seems a better design is to use the outer-join and in-clause lists as a backup heuristic, just as the rule of joining only where there are joinclauses is a heuristic: we'll join two relations if they have a usable joinclause *or* this might be necessary to satisfy an outer-join or IN-clause join order restriction. I refactored the code to have just one place considering this instead of three, and made sure that it covered all the cases that any of them had been considering. Backpatch as far as 8.1 (which has only the IN-clause form of the disease). By rights 8.0 and 7.4 should have the bug too, but they accidentally fail to fail, because the joininfo structure used in those releases preserves some memory of there having once been a joinclause between the inner and outer sides of an IN, and so it leads the code in the right direction anyway. I'll be conservative and not touch them.
-
- 15 2月, 2007 1 次提交
-
-
由 Tom Lane 提交于
platform-specific result ordering. Per buildfarm results.
-
- 14 2月, 2007 1 次提交
-
-
由 Tom Lane 提交于
equality checks it applies, instead of a random dependence on whatever operators might be named "=". The equality operators will now be selected from the opfamily of the unique index that the FK constraint depends on to enforce uniqueness of the referenced columns; therefore they are certain to be consistent with that index's notion of equality. Among other things this should fix the problem noted awhile back that pg_dump may fail for foreign-key constraints on user-defined types when the required operators aren't in the search path. This also means that the former warning condition about "foreign key constraint will require costly sequential scans" is gone: if the comparison condition isn't indexable then we'll reject the constraint entirely. All per past discussions. Along the way, make the RI triggers look into pg_constraint for their information, instead of using pg_trigger.tgargs; and get rid of the always error-prone fixed-size string buffers in ri_triggers.c in favor of building up the RI queries in StringInfo buffers. initdb forced due to columns added to pg_constraint and pg_trigger.
-
- 10 2月, 2007 2 次提交
-
-
由 Tom Lane 提交于
order platform-specific. Add an ORDER BY clause to stop buildfarm failures.
-
由 Tom Lane 提交于
currently have any better strategy for this query than re-running the sub-select over and over; it seems unlikely that doing so 10000 times is a more useful test than doing it a few dozen times.
-
- 09 2月, 2007 3 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
keeping private state in each backend that has inserted and deleted the same tuple during its current top-level transaction. This is sufficient since there is no need to be able to determine the cmin/cmax from any other transaction. This gets us back down to 23-byte headers, removing a penalty paid in 8.0 to support subtransactions. Patch by Heikki Linnakangas, with minor revisions by moi, following a design hashed out awhile back on the pghackers list.
-
由 Tom Lane 提交于
-
- 08 2月, 2007 3 次提交
-
-
由 Bruce Momjian 提交于
For win32 in general, this makes it possible to run the regression tests as an admin user by using the same restricted token method that's used by pg_ctl and initdb. For vc++, it adds building of pg_regress.exe, adds a resultmap, and fixes how it runs the install. Magnus Hagander
-
由 Tom Lane 提交于
already collected in the current transaction; this allows plpgsql functions to watch for stats updates even though they are confined to a single transaction. Use this instead of the previous kluge involving pg_stat_file() to wait for the stats collector to update in the stats regression test. Internally, decouple storage of stats snapshots from transaction boundaries; they'll now stick around until someone calls pgstat_clear_snapshot --- which xact.c still does at transaction end, to maintain the previous behavior. This makes the logic a lot cleaner, at the price of a couple dozen cycles per transaction exit.
-
由 Tom Lane 提交于
changes (with an upper limit of 30 seconds), and record the delay time in the postmaster log. This should give us some info about what's happening with the intermittent stats failures in buildfarm. After an idea of Andrew Dunstan's.
-
- 07 2月, 2007 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 06 2月, 2007 2 次提交
-
-
由 Tom Lane 提交于
merges/hashes property settings.
-
由 Tom Lane 提交于
that aren't turned into true joins). Since this is the last missing bit of infrastructure, go ahead and fill out the hash integer_ops and float_ops opfamilies with cross-type operators. The operator family project is now DONE ... er, except for documentation ...
-
- 03 2月, 2007 1 次提交
-
-
由 Peter Eisentraut 提交于
observe the xmloption. Reorganize the representation of the XML option in the parse tree and the API to make it easier to manage and understand. Add regression tests for parsing back XML expressions.
-
- 02 2月, 2007 3 次提交
-
-
由 Neil Conway 提交于
recent may/might cleanup, in the hopes that this will unbreak the buildfarm. Per report from Stefan Kaltenbrunner.
-
由 Tom Lane 提交于
an error will be thrown correctly if the variable is of a NOT NULL domain. Report and almost-correct fix from Sergiy Vyshnevetskiy (bug #2948).
-
由 Bruce Momjian 提交于
Standard English uses "may", "can", and "might" in different ways: may - permission, "You may borrow my rake." can - ability, "I can lift that log." might - possibility, "It might rain today." Unfortunately, in conversational English, their use is often mixed, as in, "You may use this variable to do X", when in fact, "can" is a better choice. Similarly, "It may crash" is better stated, "It might crash".
-
- 01 2月, 2007 2 次提交
-
-
由 Neil Conway 提交于
targets, and refactor the tablespace setup code into a separate Makefile target.
-
由 Neil Conway 提交于
nonportable "hh" sprintf(3) length modifier. Instead, do the parsing and output by hand. The code to do this isn't ideal, but this is an interim measure anyway: the uuid type should probably use the in-memory struct layout specified by RFC 4122. For now, this patch should hopefully rectify the buildfarm failures for the uuid test. Along the way, re-add pg_cast entries for uuid <-> varchar, which I mistakenly removed earlier, and bump the catversion.
-
- 29 1月, 2007 1 次提交
-
-
由 Neil Conway 提交于
that defined in RFC 4122. This patch includes the basic implementation, plus regression tests. Documentation and perhaps some additional functionality will come later. Catversion bumped. Patch from Gevik Babakhani; review from Peter, Tom, and myself.
-
- 28 1月, 2007 1 次提交
-
-
由 Tom Lane 提交于
activity quiesce. Possibly this will fix the large increase in non-reproducible stats test failures we've noted since turning on stats_row_level by default.
-
- 25 1月, 2007 1 次提交
-
-
由 Peter Eisentraut 提交于
- Add new SQL command SET XML OPTION (also available via regular GUC) to control the DOCUMENT vs. CONTENT option in implicit parsing and serialization operations. - Subtle corrections in the handling of the standalone property in xmlroot(). - Allow xmlroot() to work on content fragments. - Subtle corrections in the handling of the version property in xmlconcat(). - Code refactoring for producing XML declarations.
-
- 24 1月, 2007 1 次提交
-
-
由 Peter Eisentraut 提交于
libxml as the detail message. As per <http://archives.postgresql.org/pgsql-hackers/2006-12/msg01087.php>. For converting error codes to messages, we only need to cover those codes that we raise ourselves now.
-
- 22 1月, 2007 1 次提交
-
-
由 Tom Lane 提交于
columns procost and prorows, to allow simple user adjustment of the estimated cost of a function call, as well as control of the estimated number of rows returned by a set-returning function. We might eventually wish to extend this to allow function-specific estimation routines, but there seems to be consensus that we should try a simple constant estimate first. In particular this provides a relatively simple way to control the order in which different WHERE clauses are applied in a plan node, which is a Good Thing in view of the fact that the recent EquivalenceClass planner rewrite made that much less predictable than before.
-
- 21 1月, 2007 2 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Neil Conway 提交于
-
- 20 1月, 2007 4 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
function xmlagg.
-
由 Alvaro Herrera 提交于
"input" and "output" dirs be necessarily present.
-
由 Peter Eisentraut 提交于
with new GUC parameter "xmlbinary" that controls the output encoding, as per SQL/XML standard.
-