- 10 6月, 2008 3 次提交
-
-
由 Tom Lane 提交于
running on a 64-bit platform ... strtol() will happily return 64-bit output in that case. Per bug #4231 from Geoff Tolley.
-
由 Tom Lane 提交于
is testing. Ah, the perils of making keywords optional ...
-
由 Neil Conway 提交于
-
- 09 6月, 2008 6 次提交
-
-
由 Neil Conway 提交于
-
由 Alvaro Herrera 提交于
-
由 Tom Lane 提交于
algorithm, replacing the original intention of a one-pass search, which had been hacked up over time to be partially two-pass in hopes of handling various corner cases better. It still wasn't quite there, especially as regards emitting unwanted NOTICE messages. More importantly, this approach lets us fix a number of open bugs concerning concurrent DROP scenarios, because we can take locks during the first pass and avoid traversing to dependent objects that were just deleted by someone else. There is more that can be done here, but I'll go ahead and commit the base patch before working on the options.
-
由 Alvaro Herrera 提交于
more logical that way, and also it reduces the amount of unnecessary includes in bufpage.h, which is widely used. Zdenek Kotala. My previous patch to bufpage.h should also have credited him as author, but I forgot (sorry about that).
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
patches that dealt with object ownership. It wasn't updating pg_shdepend nor adjusting the aggregate's ACL. In 8.2 and up, fix this permanently by making it use AlterFunctionOwner_oid. In 8.1, the function code wasn't factored that way, so just copy and paste.
-
- 08 6月, 2008 1 次提交
-
-
由 Tom Lane 提交于
-
- 07 6月, 2008 2 次提交
-
-
由 Alvaro Herrera 提交于
-
由 Tom Lane 提交于
This is needed because :: casting binds more tightly than minus, so for example -1::integer is not the same as (-1)::integer, and there are cases where the difference is important. In particular this caused a failure in SELECT DISTINCT ... ORDER BY ... where expressions that should have matched were seen as different by the parser; but I suspect that there could be other cases where failure to parenthesize leads to subtler semantic differences in reloaded rules. Per report from Alexandr Popov.
-
- 06 6月, 2008 1 次提交
-
-
由 Alvaro Herrera 提交于
-
- 05 6月, 2008 2 次提交
-
-
由 Alvaro Herrera 提交于
always pass as a single element anyway.) In passing, fix an outdated comment.
-
由 Alvaro Herrera 提交于
-
- 04 6月, 2008 2 次提交
-
-
由 Michael Meskes 提交于
-
由 Tom Lane 提交于
-
- 02 6月, 2008 4 次提交
-
-
由 Tom Lane 提交于
doesn't work, and the real reason why not is it's unclear where the path is relative to (initdb's CWD, or the data directory?). We could make an arbitrary decision, but it seems best to make the user be unambiguous. Per gripe from Devrim.
-
由 Tom Lane 提交于
Morocco, Iraq, Choibalsan, Pakistan, Syria, Cuba, Argentina/San_Luis).
-
由 Tom Lane 提交于
the PARAM_FLAG_CONST flag on the parameters that are passed into the portal, while the former's behavior is unchanged. This should only affect the case where the portal is executing an EXPLAIN; it will cause the generated plan to look more like what would be generated if the portal were actually executing the command being explained. Per gripe from Pavel.
-
由 Tom Lane 提交于
-
- 31 5月, 2008 1 次提交
-
-
由 Andrew Dunstan 提交于
-
- 30 5月, 2008 4 次提交
-
-
由 Tom Lane 提交于
"make all", and then reference them there during the actual tests. This makes the handling of these files more parallel to that of regress.so, and in particular simplifies use of the regression tests outside the original build tree. The PGDG and Red Hat RPMs have been doing this via patches for a very long time. Inclusion of the change in core was requested by Jørgen Austvik of Sun, and I can't see any reason not to. I attempted to fix the MSVC scripts for this too, but they may need further tweaking ...
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
we are on a 64-bit machine (ie, size_t is wider than int) and someone passes in a query string that approaches or exceeds INT_MAX bytes. Also, just for paranoia's sake, guard against similar overflows in sizing the input buffer. The backend will not in the foreseeable future be prepared to send or receive strings exceeding 1GB, so I didn't take the more invasive step of switching all the buffer index variables from int to size_t; though someday we might want to do that. I have a suspicion that this is not the only such bug in libpq, but this fix is enough to take care of the crash reported by Francisco Reyes.
-
由 Tom Lane 提交于
calling convention. cube_inter and cube_distance could attempt to pfree their input arguments, and cube_dim returned a value from a struct it might have just pfree'd (which would only really cause a problem in a debug build, but it's still wrong). Per bug #4208 and additional code reading. In HEAD and 8.3, I also made a batch of cosmetic changes to bring these functions into line with the preferred coding style for V1 functions, ie declare and fetch all the arguments at the top so readers can easily see what they are.
-
- 29 5月, 2008 2 次提交
-
-
由 Bruce Momjian 提交于
* Add deferred trigger queue file < This item involves dumping large queues into files. > This item involves dumping large queues into files, or doing some > kind of join to process all the triggers, or some bulk operation.
-
由 Bruce Momjian 提交于
* Add deferred trigger queue file > http://archives.postgresql.org/pgsql-hackers/2008-05/msg00876.php
-
- 28 5月, 2008 5 次提交
-
-
由 Magnus Hagander 提交于
-
由 Magnus Hagander 提交于
still accepting them as input, used to allow alternate syntax for the same setting. Alex Hunsaker
-
由 Tom Lane 提交于
require SELECT privilege as well, since you normally need to read existing column values within such commands. This behavior is according to spec, but we'd never documented it before. Per gripe from Volkan Yazici.
-
由 Tom Lane 提交于
GNU gettext before 0.10.36 does not have that function, and is generally too incomplete to be usable.
-
由 Tom Lane 提交于
-
- 27 5月, 2008 3 次提交
-
-
由 Magnus Hagander 提交于
This is required on Windows due to the special locale handling for UTF8 that doesn't change the full environment. Fixes crash with translated error messages per bugs 4180 and 4196. Tom Lane
-
由 Tom Lane 提交于
the associated datatype as their equality member. This means that these opclasses can now support plain equality comparisons along with LIKE tests, thus avoiding the need for an extra index in some applications. This optimization was not possible when the pattern opclasses were first introduced, because we didn't insist that text equality meant bitwise equality; but we do now, so there is no semantic difference between regular and pattern equality operators. I removed the name_pattern_ops opclass altogether, since it's really useless: name's regular comparisons are just strcmp() and are unlikely to become something different. Instead teach indxpath.c that btree name_ops can be used for LIKE whether or not the locale is C. This might lead to a useful speedup in LIKE queries on the system catalogs in non-C locales. The ~=~ and ~<>~ operators are gone altogether. (It would have been nice to keep them for backward compatibility's sake, but since the pg_amop structure doesn't allow multiple equality operators per opclass, there's no way.) A not-immediately-obvious incompatibility is that the sort order within bpchar_pattern_ops indexes changes --- it had been identical to plain strcmp, but is now trailing-blank-insensitive. This will impact in-place upgrades, if those ever happen. Per discussions a couple months ago.
-
由 Tom Lane 提交于
called before, not after, calling the assign_hook if any. This is because push_old_value might fail (due to palloc out-of-memory), and in that case there would be no stack entry to tell transaction abort to undo the GUC assignment. Of course the actual assignment to the GUC variable hasn't happened yet --- but the assign_hook might have altered subsidiary state. Without a stack entry we won't call it again to make it undo such actions. So this is necessary to make the world safe for assign_hooks with side effects. Per a discussion a couple weeks ago with Magnus. Back-patch to 8.0. 7.x did not have the problem because it did not have allocatable stacks of GUC values.
-
- 26 5月, 2008 1 次提交
-
-
由 Tom Lane 提交于
cases. Recent buildfarm experience shows that it is sometimes possible to execute several SQL commands in less time than the granularity of Windows' not-very-high-resolution gettimeofday(), leading to a failure because the tests expect the value of now() to change and it doesn't. Also, it was recognized some time ago that the same area of the tests could fail if local midnight passes between the insertion and the checking of the values for 'yesterday', 'tomorrow', etc. Clean all this up per ideas from myself and Greg Stark. There remains a window for failure if the transaction block is entered exactly at local midnight (so that 'now' and 'today' have the same value), but that seems low-probability enough to live with. Since the point of this change is mostly to eliminate buildfarm noise, back-patch to all versions we are still actively testing.
-
- 22 5月, 2008 3 次提交
-
-
由 Michael Meskes 提交于
Use #define/#ifdef instead of sed to fix include files, this should work on Windows too.
-
由 Magnus Hagander 提交于
Per red Windows buildfarm members.
-
由 Magnus Hagander 提交于
compiler warnings on msvc.
-