- 21 7月, 2007 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 20 7月, 2007 4 次提交
-
-
由 Tom Lane 提交于
lot more sensible if we check the chunk-output case first. Not back-patched since it's just a cosmetic improvement.
-
由 Tom Lane 提交于
when handed an invalidly-encoded pattern. The previous coding could get into an infinite loop if pg_mb2wchar_with_len() returned a zero-length string after we'd tested for nonempty pattern; which is exactly what it will do if the string consists only of an incomplete multibyte character. This led to either an out-of-memory error or a backend crash depending on platform. Per report from Wiktor Wodecki.
-
由 Andrew Dunstan 提交于
be catching stderr output, and we are not ourselves the syslogger. Otherwise, go directly to stderr. Bug noticed by Tom Lane. Backpatch as far as 8.0.
-
由 Tom Lane 提交于
Minor rearrangements to make a few tests in a more logical order.
-
- 19 7月, 2007 2 次提交
-
-
由 Tom Lane 提交于
a MIN or MAX aggregate call into an indexscan: the initplan is being made at the current query nesting level and so we shouldn't increment query_level. Though usually harmless, this mistake could lead to bogus "plan should not reference subplan's variable" failures on complex queries. Per bug report from David Sanchez i Gregori.
-
由 Alvaro Herrera 提交于
some platforms and possibly a bug. Per report from Stefan and subsequent discussion.
-
- 18 7月, 2007 6 次提交
-
-
由 Magnus Hagander 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Patch from Tom.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
> > o Allow GLOBAL temporary tables to exist as empty by default in > all sessions > > http://archives.postgresql.org/pgsql-hackers/2007-07/msg00006.php >
-
由 Tom Lane 提交于
referencing table does not change the tuple's FK column(s), we don't bother to check the PK table since the constraint was presumably already valid. However, the check is still necessary if the tuple was inserted by our own transaction, since in that case the INSERT trigger will conclude it need not make the check (since its version of the tuple has been deleted). We got this right for simple cases, but not when the insert and update are in different subtransactions of the current top-level transaction; in such cases the FK check would never be made at all. (Hence, problem dates back to 8.0 when subtransactions were added --- it's actually the subtransaction version of a bug fixed in 7.3.5.) Fix, and add regression test cases. Report and fix by Affan Salman.
-
- 17 7月, 2007 10 次提交
-
-
-
由 Neil Conway 提交于
based in part on an earlier patch from Trevor Hardcastle, and reviewed by myself.
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
been broken since forever, but was not noticed because people seldom look at raw parse trees. AFAIK, no impact on users except that debug_print_parse might fail; but patch it all the way back anyway. Per report from Jeff Ross.
-
由 Bruce Momjian 提交于
> * Allow multiple indexes to be created concurrently, ideally via a > single heap scan, and have a restore of a pg_dump somehow use it > > http://archives.postgresql.org/pgsql-general/2007-05/msg01274.php Small blank line additions.
-
由 Bruce Momjian 提交于
on other errors.
-
由 Tom Lane 提交于
and add a note about why. This is not tremendously important right now, probably, but it will get more urgent if NUM_BUFFER_PARTITIONS is increased as much as proposed.
-
由 Tom Lane 提交于
partition locks in reverse order.
-
由 Neil Conway 提交于
--enable-debug is used, to avoid complaints about debugging and optimization being mutually exclusive. Patch from Stefan Kaltenbrunner.
-
由 Tom Lane 提交于
name. With this patch, it is always possible for the user to qualify a plpgsql variable name if needed to avoid ambiguity. While there is much more work to be done in this area, this simple change removes one unnecessary incompatibility with Oracle. Per discussion.
-
- 16 7月, 2007 16 次提交
-
-
由 Tom Lane 提交于
int not unsigned int. Third try to get grebe building without warnings...
-
由 Magnus Hagander 提交于
spaces in them. ISHIDA Akio
-
由 Tom Lane 提交于
nattering about casting away volatile. Losers.
-
由 Tom Lane 提交于
TAS support are properly declared.
-
由 Tom Lane 提交于
for 'bool'. Per buildfarm warnings.
-
由 Tom Lane 提交于
a warning but was outright wrong.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
error messages look at least a little bit like the message style guidelines say.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
not-too-bright compilers. Per buildfarm results.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
three slightly different copies of this file?)
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
theoretically vary depending on what the compile-time locale setting is. Hence, force it to see LC_CTYPE=C to ensure consistent build results. (It's likely that this makes no difference in practice, since our specification for "identifier" surely includes both ends of any possible uppercase/lowercase pair anyway. But it should silence warnings about ambiguous character classes that are reported by some buildfarm members.)
-
- 15 7月, 2007 1 次提交
-
-
由 Tom Lane 提交于
sanely if the loop value overflows int32 on the way to the end value. Avoid useless computation of "SELECT 1" when BY is omitted. Avoid some type-punning between Datum and int4 that dates from the original coding.
-