- 06 1月, 2012 2 次提交
-
-
由 Peter Eisentraut 提交于
ALTER DOMAIN / DROP CONSTRAINT on a nonexistent constraint name did not report any error. Now it reports an error. The IF EXISTS option was added to get the usual behavior of ignoring nonexistent objects to drop.
-
由 Andrew Dunstan 提交于
Certain things like typeglobs or readonly things like $^V cause perl's SvPVutf8() to die nastily and crash the backend. To avoid that bug we make a copy of the object, which will subsequently be garbage collected. Back patched to 9.1 where we first started using SvPVutf8(). Per -hackers discussion. Original problem reported by David Wheeler.
-
- 05 1月, 2012 2 次提交
-
-
由 Michael Meskes 提交于
This list is now freed when the last connection has been closed. Closes: #6366
-
由 Tom Lane 提交于
As previously coded, the QueryDesc's dest pointer was left dangling (pointing at an already-freed receiver object) after ExecutorEnd. It's a bit astonishing that it took us this long to notice, and I'm not sure that the known problem case with SQL functions is the only one. Fix it by saving and restoring the original receiver pointer, which seems the most bulletproof way of ensuring any related bugs are also covered. Per bug #6379 from Paul Ramsey. Back-patch to 8.4 where the current handling of SELECT INTO was introduced.
-
- 04 1月, 2012 3 次提交
-
-
由 Michael Meskes 提交于
-
由 Andrew Dunstan 提交于
-
由 Tom Lane 提交于
Further testing convinces me that this is helpful at sufficiently high contention levels, though it's still worrisome that it loses slightly at lower contention levels. Per Manabu Ori.
-
- 03 1月, 2012 4 次提交
-
-
由 Andrew Dunstan 提交于
Brar Piening, reviewed by Craig Ringer.
-
由 Peter Eisentraut 提交于
atexit() hook
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
Because coerce_type recurses into the argument of a CollateExpr, coerce_to_target_type's longstanding code for detecting whether coerce_type had actually done anything (to wit, returned a different node than it passed in) was broken in 9.1. This resulted in unexpected failures in hide_coercion_node; which was not the latter's fault, since it's critical that we never call it on anything that wasn't inserted by coerce_type. (Else we might decide to "hide" a user-written function call.) Fix by removing and replacing the CollateExpr in coerce_to_target_type itself. This is all pretty ugly but I don't immediately see a way to make it nicer. Per report from Jean-Yves F. Barbier.
-
- 02 1月, 2012 12 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
This is allegedly a win, at least on some PPC implementations, according to the PPC ISA documents. However, as with LWARX hints, some PPC platforms give an illegal-instruction failure. Use the same trick as before of assuming that PPC64 platforms will accept it; we might need to refine that based on experience, but there are other projects doing likewise according to google. I did not add an assembler compatibility test because LWSYNC has been around much longer than hint bits, and it seems unlikely that any toolchains currently in use don't recognize it.
-
由 Tom Lane 提交于
Previously we defined slock_t as 8 bytes on PPC64, but the TAS assembly code uses word-wide operations regardless, so that the second word was just wasted space. There doesn't appear to be any performance benefit in adding the second word, so get rid of it to simplify the code.
-
由 Tom Lane 提交于
The hint bit makes for a small but measurable performance improvement in access to contended spinlocks. On the other hand, some PPC chips give an illegal-instruction failure. There doesn't seem to be a completely bulletproof way to tell whether the hint bit will cause an illegal-instruction failure other than by trying it; but most if not all 64-bit PPC machines should accept it, so follow the Linux kernel's lead and assume it's okay to use it in 64-bit builds. Of course we must also check whether the assembler accepts the command, since even with a recent CPU the toolchain could be old. Patch by Manabu Ori, significantly modified by me.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
directories. Per suggestion from Andrew Dunstan.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
those files corrupts the index.
-
- 31 12月, 2011 3 次提交
-
-
由 Simon Riggs 提交于
Allows streaming replication users to calculate transfer latency and apply delay via internal functions. No external functions yet.
-
由 Bruce Momjian 提交于
to 'make' rather than 'gmake' for the binary name.
-
- 30 12月, 2011 3 次提交
-
-
由 Tom Lane 提交于
The original test cases gave varying results depending on whether the locale sorts digits before or after letters. Since that's not really what we wish to test here, adjust the test data to not contain any strings beginning with digits. Per report from Pavel Stehule.
-
由 Peter Eisentraut 提交于
For easier source reading
-
由 Peter Eisentraut 提交于
This is to get a deterministic dump order independent of the order in which the user mappings were created.
-
- 29 12月, 2011 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 28 12月, 2011 5 次提交
-
-
由 Peter Eisentraut 提交于
Always compare the return value to 0, don't use cute tricks like if (!strcmp(...)).
-
由 Peter Eisentraut 提交于
All supported platforms support the C89 standard function atexit() (SunOS 4 probably being the last one not to), and supporting both makes the code clumsy.
-
由 Peter Eisentraut 提交于
This is the standard behavior but was forgotten in some places.
-
由 Peter Eisentraut 提交于
That way, the result of a msgmerge is more deterministic and not dependent on the order in which the files are found.
-
由 Peter Eisentraut 提交于
That way, the created .pot file is more deterministic and not dependent on the order in which the files are found.
-
- 27 12月, 2011 1 次提交
-
-
由 Alvaro Herrera 提交于
Author: Erik Rijkers
-
- 25 12月, 2011 1 次提交
-
-
由 Tom Lane 提交于
In commit e2c2c2e8 I made use of nested list structures to show which clauses went with which index columns, but on reflection that's a data structure that only an old-line Lisp hacker could love. Worse, it adds unnecessary complication to the many places that don't much care which clauses go with which index columns. Revert to the previous arrangement of flat lists of clauses, and instead add a parallel integer list of column numbers. The places that care about the pairing can chase both lists with forboth(), while the places that don't care just examine one list the same as before. The only real downside to this is that there are now two more lists that need to be passed to amcostestimate functions in case they care about column matching (which btcostestimate does, so not passing the info is not an option). Rather than deal with 11-argument amcostestimate functions, pass just the IndexPath and expect the functions to extract fields from it. That gets us down to 7 arguments which is better than 11, and it seems more future-proof against likely additions to the information we keep about an index path.
-
- 24 12月, 2011 1 次提交
-
-
由 Tom Lane 提交于
It's potentially useful for an index to repeat the same indexable column or expression in multiple index columns, if the columns have different opclasses. (If they share opclasses too, the duplicate column is pretty useless, but nonetheless we've allowed such cases since 9.0.) However, the planner failed to cope with this, because createplan.c was relying on simple equal() matching to figure out which index column each index qual is intended for. We do have that information available upstream in indxpath.c, though, so the fix is to not flatten the multi-level indexquals list when putting it into an IndexPath. Then we can rely on the sublist structure to identify target index columns in createplan.c. There's a similar issue for index ORDER BYs (the KNNGIST feature), so introduce a multi-level-list representation for that too. This adds a bit more representational overhead, but we might more or less buy that back by not having to search for matching index columns anymore in createplan.c; likewise btcostestimate saves some cycles. Per bug #6351 from Christian Rudolph. Likely symptoms include the "btree index keys must be ordered by attribute" failure shown there, as well as "operator MMMM is not a member of opfamily NNNN". Although this is a pre-existing problem that can be demonstrated in 9.0 and 9.1, I'm not going to back-patch it, because the API changes in the planner seem likely to break things such as index plugins. The corner cases where this matters seem too narrow to justify possibly breaking things in a minor release.
-
- 23 12月, 2011 2 次提交
-
-
由 Robert Haas 提交于
Pavel Stehule
-
由 Robert Haas 提交于
All noted by Jaime Casanova.
-