- 20 7月, 2006 3 次提交
-
-
由 Tom Lane 提交于
switches passed from the Makefile. This looks like it will fix problem with virtual vs real paths under msys.
-
由 Tom Lane 提交于
just exec instead of creating a subprocess. This reduces process usage from four processes per parallel test to two. I have no idea whether a comparable optimization is possible or useful in the Windows port.
-
由 Tom Lane 提交于
'make install' or 'initdb' fails. Also minor simplification of fgets() usage --- fgets guarantees a trailing null anyway.
-
- 19 7月, 2006 4 次提交
- 18 7月, 2006 1 次提交
-
-
由 Tom Lane 提交于
code to forcibly drop regressuser[1-4] and regressgroup[1-2]. Instead, let the privileges.sql test do that for itself (this is made easy by the recent addition of DROP ROLE IF EXISTS). Per a recent patch proposed by Joachim Wieland --- the rest of his patch is superseded by the rewrite into C, but this is a good idea we should adopt.
-
- 14 7月, 2006 1 次提交
-
-
由 Bruce Momjian 提交于
Strip unused include files out unused include files, and add needed includes to C files. The next step is to remove unused include files in C files.
-
- 12 7月, 2006 1 次提交
-
-
由 Teodor Sigaev 提交于
-
- 06 7月, 2006 1 次提交
-
-
由 Bruce Momjian 提交于
for the usage of full time zone names. Joachim Wieland
-
- 02 7月, 2006 2 次提交
-
-
由 Neil Conway 提交于
the read lock we hold on the table's parent relation until commit. Update equalfuncs.c for the new field in AlterTableCmd. Various improvements to comments, variable names, and error reporting. There is room for further improvement here, but this is at least a step in the right direction.
-
由 Bruce Momjian 提交于
Open items: There were a few tangentially related issues that have come up that I think are TODOs. I'm likely to tackle one or two of these next so I'm interested in hearing feedback on them as well. . Constraints currently do not know anything about inheritance. Tom suggested adding a coninhcount and conislocal like attributes have to track their inheritance status. . Foreign key constraints currently do not get copied to new children (and therefore my code doesn't verify them). I don't think it would be hard to add them and treat them like CHECK constraints. . No constraints at all are copied to tables defined with LIKE. That makes it hard to use LIKE to define new partitions. The standard defines LIKE and specifically says it does not copy constraints. But the standard already has an option called INCLUDING DEFAULTS; we could always define a non-standard extension LIKE table INCLUDING CONSTRAINTS that gives the user the option to request a copy including constraints. . Personally, I think the whole attislocal thing is bunk. The decision about whether to drop a column from children tables or not is something that should be up to the user and trying to DWIM based on whether there was ever a local definition or the column was acquired purely through inheritance is hardly ever going to match up with user expectations. . And of course there's the whole unique and primary key constraint issue. I think to get any traction at all on this you have a prerequisite of a real partitioned table implementation where the system knows what the partition key is so it can recognize when it's a leading part of an index key. Greg Stark
-
- 30 6月, 2006 1 次提交
-
-
由 Tom Lane 提交于
the order in which it visits tables is not dependent on the physical order of pg_constraint entries, and neither are the error messages it gives. This should correct recently-noticed instability in regression tests.
-
- 27 6月, 2006 2 次提交
-
-
由 Bruce Momjian 提交于
Greg Stark
-
由 Tom Lane 提交于
will be expanded to a list of their member fields, rather than creating a nested rowtype field as formerly. (The old behavior is still available by omitting '.*'.) This syntax is not allowed by the SQL spec AFAICS, so changing its behavior doesn't violate the spec. The new behavior is substantially more useful since it allows, for example, triggers to check for data changes with 'if row(new.*) is distinct from row(old.*)'. Per my recent proposal.
-
- 19 6月, 2006 1 次提交
-
-
由 Tom Lane 提交于
We have once or twice seen failures suggesting that control didn't get to the exception block before the timeout elapsed, which is unlikely but not impossible in a parallel regression test (with a dozen other backends competing for cycles). This change doesn't completely prevent the problem of course, but it should reduce the probability enough that we don't see it anymore. Per buildfarm results.
-
- 31 5月, 2006 1 次提交
-
-
由 Tom Lane 提交于
as this seems only likely to create headaches for module developers. Put the macro in the pre-existing fmgr.h file instead. Avoid being too cute about how many fields we can cram into a word, and avoid trying to fetch from a library we've already unlinked. Along the way, it occurred to me that the magic block really ought to be 'const' so it can be stored in the program text area. Do the same for the existing data blocks for PG_FUNCTION_INFO_V1 functions.
-
- 30 5月, 2006 5 次提交
-
-
由 Bruce Momjian 提交于
It now only checks four things: Major version number (7.4 or 8.1 for example) NAMEDATALEN FUNC_MAX_ARGS INDEX_MAX_KEYS The three constants were chosen because: 1. We document them in the config page in the docs 2. We mark them as changable in pg_config_manual.h 3. Changing any of these will break some of the more popular modules: FUNC_MAX_ARGS changes fmgr interface, every module uses this NAMEDATALEN changes syscache interface, every PL as well as tsearch uses this INDEX_MAX_KEYS breaks tsearch and anything using GiST. Martijn van Oosterhout
-
由 Bruce Momjian 提交于
--------------------------------------------------------------------------- Add dynamic record inspection to PL/PgSQL, useful for generic triggers: tval2 := r.(cname); or columns := r.(*); Titus von Boxberg
-
由 Bruce Momjian 提交于
tval2 := r.(cname); or columns := r.(*); Titus von Boxberg
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Joachim Wieland
-
- 28 5月, 2006 2 次提交
-
-
由 Andrew Dunstan 提交于
fix typo
-
由 Andrew Dunstan 提交于
TG_table_name and TG_table_schema for plpgsql, plus docs and regression.
-
- 22 5月, 2006 1 次提交
-
-
由 Tom Lane 提交于
characters in all cases. Formerly we mostly just threw warnings for invalid input, and failed to detect it at all if no encoding conversion was required. The tighter check is needed to defend against SQL-injection attacks as per CVE-2006-2313 (further details will be published after release). Embedded zero (null) bytes will be rejected as well. The checks are applied during input to the backend (receipt from client or COPY IN), so it no longer seems necessary to check in textin() and related routines; any string arriving at those functions will already have been validated. Conversion failure reporting (for characters with no equivalent in the destination encoding) has been cleaned up and made consistent while at it. Also, fix a few longstanding errors in little-used encoding conversion routines: win1251_to_iso, win866_to_iso, euc_tw_to_big5, euc_tw_to_mic, mic_to_euc_tw were all broken to varying extents. Patches by Tatsuo Ishii and Tom Lane. Thanks to Akio Ishida and Yasuo Ohgaki for identifying the security issues.
-
- 20 5月, 2006 1 次提交
-
-
由 Alvaro Herrera 提交于
issued by autovacuum. Add accessor functions to them, and use those in the pg_stat_*_tables system views. Catalog version bumped due to changes in the pgstat views and the pgstat file. Patch from Larry Rosenman, minor improvements by me.
-
- 12 5月, 2006 1 次提交
-
-
由 Tom Lane 提交于
throw warnings for 100%-SQL-standard constructs, clean up some minor infelicities, try to un-break ecpg to the best of my ability. (It's not clear how ecpg is going to find out the setting of standard_conforming_strings, though.) I think pg_dump still needs work, too.
-
- 06 5月, 2006 2 次提交
-
-
由 Bruce Momjian 提交于
patch reverted.
-
由 Bruce Momjian 提交于
Backpatch to 8.1.X. Simon Burge
-
- 02 5月, 2006 1 次提交
-
-
由 Teodor Sigaev 提交于
text[], int4[], Tsearch2 support for GIN.
-
- 16 4月, 2006 1 次提交
-
-
由 Tom Lane 提交于
CREATE AGGREGATE aggname (input_type) (parameter_list) along with the old syntax where the input type was named in the parameter list. This fits more naturally with the way that the aggregate is identified in DROP AGGREGATE and other utility commands; furthermore it has a natural extension to handle multiple-input aggregates, where the basetype-parameter method would get ugly. In fact, this commit fixes the grammar and all the utility commands to support multiple-input aggregates; but DefineAggregate rejects it because the executor isn't fixed yet. I didn't do anything about treating agg(*) as a zero-input aggregate instead of artificially making it a one-input aggregate, but that should be considered in combination with supporting multi-input aggregates.
-
- 07 4月, 2006 1 次提交
-
-
由 Peter Eisentraut 提交于
generated text files. Fix build of that file, too. Put the text files in the right place during make dist, so there are no extra manual steps required anymore.
-
- 06 4月, 2006 1 次提交
-
-
由 Tom Lane 提交于
that apply the necessary domain constraint checks immediately. This fixes cases where domain constraints went unchecked for statement parameters, PL function local variables and results, etc. We can also eliminate existing special cases for domains in places that had gotten it right, eg COPY. Also, allow domains over domains (base of a domain is another domain type). This almost worked before, but was disallowed because the original patch hadn't gotten it quite right.
-
- 03 4月, 2006 1 次提交
-
-
由 Tom Lane 提交于
Strange that we missed this DST dependence while fixing the others.
-
- 23 3月, 2006 2 次提交
-
-
由 Tom Lane 提交于
command or expression, rather than one copy for each textual occurrence as it did before. This might result in some small performance improvement, but the compelling reason to do it is that not doing so can result in unexpected grouping failures because the main SQL parser won't see different parameter numbers as equivalent. Add a regression test for the failure case. Per report from Robert Davidson.
-
由 Tom Lane 提交于
for various mistakes involving INSERT and UPDATE target columns.
-
- 19 3月, 2006 1 次提交
-
-
由 Tom Lane 提交于
test, per Dave Page and buildfarm. Perhaps we will need a join_2 instead, but for the moment assume that this test tracks the other diffs.
-
- 18 3月, 2006 1 次提交
-
-
由 Tom Lane 提交于
2005-05-13. When we find that a new inner tuple can't possibly match any outer tuple (because it contains a NULL), we can't immediately skip the tuple when we are in NEXTINNER state. Doing so can lead to emitting multiple copies of the tuple in FillInner mode, because we may rescan the tuple after returning to a previous marked tuple. Instead, proceed to NEXTOUTER state the same as we used to do. After we've found that there's no need to return to the marked position, we can go to SKIPINNER_ADVANCE state instead of SKIP_TEST when the inner tuple is unmatchable; this preserves the performance improvement. Per bug report from Bruce. I also made a couple of cosmetic code rearrangements and added a regression test for the problem.
-
- 15 3月, 2006 1 次提交
-
-
由 Tom Lane 提交于
-