- 17 5月, 2013 1 次提交
-
- 04 3月, 2013 1 次提交
-
-
由 Tom Lane 提交于
Also make sure other fields of the view's pg_class entry are appropriate for a view; it shouldn't have relfrozenxid set for instance. This ancient omission isn't believed to have any serious consequences in versions 8.4-9.2, so no backpatch. But let's fix it before it does bite us in some serious way. It's just luck that the case doesn't cause problems for autovacuum. (It did cause problems in 8.3, but that's out of support.) Andres Freund
-
- 09 2月, 2013 1 次提交
-
-
由 Tom Lane 提交于
Ali Dar, reviewed by Dean Rasheed.
-
- 25 10月, 2012 1 次提交
-
-
由 Tom Lane 提交于
Views should not have any pg_attribute entries for system columns. However, we forgot to remove such entries when converting a table to a view. This could lead to crashes later on, if someone attempted to reference such a column, as reported by Kohei KaiGai. Patch in HEAD only. This bug has been there forever, but in the back branches we will have to defend against existing mis-converted views, so it doesn't seem worthwhile to change the conversion code too.
-
- 20 8月, 2012 2 次提交
- 20 2月, 2012 1 次提交
-
-
由 Andrew Dunstan 提交于
Some line feeds are added to target lists and from lists to make them more readable. By default they wrap at 80 columns if possible, but the wrap column is also selectable - if 0 it wraps after every item. Andrew Dunstan, reviewed by Hitoshi Harada.
-
- 24 11月, 2010 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 22 9月, 2009 1 次提交
-
-
由 Tom Lane 提交于
Introduced in 8.4 rewrite of dependency.c. Per bug #5072 from Amit Khandekar.
-
- 19 1月, 2009 1 次提交
-
-
由 Peter Eisentraut 提交于
"cg" and "ci". This eliminates a test failure on the following glibc locales: br_FR, cs_CZ, cy_GB, es_EC, es_US, hsb_DE, ig_NG, ik_CA, sk_SK.
-
- 27 5月, 2007 1 次提交
-
-
由 Tom Lane 提交于
inheritance child of an UPDATE/DELETE target relation can be excluded by constraints. I had rearranged some code in set_append_rel_pathlist() to avoid "useless" work when a child is excluded, but overdid it and left the child with no cheapest_path entry, causing possible failure later if the appendrel was involved in a join. Also, it seems that the dummy plan generated by inheritance_planner() when all branches are excluded has to be a bit less dummy now than was required in 8.2. Per report from Jan Wieck. Add his test case to the regression tests.
-
- 28 2月, 2006 1 次提交
-
-
由 Peter Eisentraut 提交于
particular get rid of single quotes around language names and old WITH () construct.
-
- 07 4月, 2005 1 次提交
-
-
由 Neil Conway 提交于
in UPDATE. We also now issue a NOTICE if a query has _any_ implicit range table entries -- in the past, we would only warn about implicit RTEs in SELECTs with at least one explicit RTE. As a result of the warning change, 25 of the regression tests had to be updated. I also took the opportunity to remove some bogus whitespace differences between some of the float4 and float8 variants. I believe I have correctly updated all the platform-specific variants, but let me know if that's not the case. Original patch for DELETE ... USING from Euler Taveira de Oliveira, reworked by Neil Conway.
-
- 26 3月, 2005 1 次提交
-
-
由 Tom Lane 提交于
output ordering.
-
- 03 10月, 2004 1 次提交
-
-
由 Tom Lane 提交于
-
- 09 3月, 2004 1 次提交
-
-
由 Bruce Momjian 提交于
Fabien COELHO
-
- 22 11月, 2003 1 次提交
-
-
由 Tom Lane 提交于
large objects. Dump all these in pg_dump; also add code to pg_dump user-defined conversions. Make psql's large object code rely on the backend for inserting/deleting LOB comments, instead of trying to hack pg_description directly. Documentation and regression tests added. Christopher Kings-Lynne, code reviewed by Tom
-
- 31 10月, 2003 1 次提交
-
-
由 Jan Wieck 提交于
rule into the rule.sql since it affects the latter if run in paralell. Jan
-
- 14 12月, 2002 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 22 11月, 2002 1 次提交
-
-
由 Tom Lane 提交于
ordering of GROUP BY output due to hash-based aggregation.
-
- 21 11月, 2002 1 次提交
-
-
由 Tom Lane 提交于
parameter to allow it to be forced off for comparison purposes. Add ORDER BY clauses to a bunch of regression test queries that will otherwise produce randomly-ordered output in the new regime.
-
- 20 10月, 2002 1 次提交
-
-
由 Tom Lane 提交于
rather than being reordered according to INSTEAD attribute for implementation convenience. Also, increase compiled-in recursion depth limit from 10 to 100 rewrite cycles. 10 seems pretty marginal for situations where multiple rules exist for the same query. There was a complaint about this recently, so I'm going to bump it up. (Perhaps we should make the limit a GUC parameter, but that's too close to being a new feature to do in beta.)
-
- 02 9月, 2002 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
Gavin Sherry, Neil Conway, and Tom Lane all got their hands dirty on this one ...
-
- 03 5月, 2002 1 次提交
-
-
由 Tom Lane 提交于
handled as special productions. This is needed to keep us honest about user-schema type names that happen to coincide with system type names. Per pghackers discussion 24-Apr. To avoid bloating the keyword list too much, I removed the translations for datetime, timespan, and lztext, all of which were slated for destruction several versions back anyway.
-
- 19 4月, 2002 1 次提交
-
-
由 Tom Lane 提交于
DROP RULE and COMMENT ON RULE syntax adds an 'ON tablename' clause, similar to TRIGGER syntaxes. To allow loading of existing pg_dump files containing COMMENT ON RULE, the COMMENT code will still accept the old syntax --- but only if the target rulename is unique across the whole database.
-
- 12 4月, 2002 1 次提交
-
-
由 Tom Lane 提交于
entries, per pghackers discussion. This fixes aggregates to live in namespaces, and also simplifies/speeds up lookup in parse_func.c. Also, add a 'proimplicit' flag to pg_proc that controls whether a type coercion function may be invoked implicitly, or only explicitly. The current settings of these flags are more permissive than I would like, but we will need to debate and refine the behavior; for now, I avoided breaking regression tests as much as I could.
-
- 15 8月, 2001 1 次提交
-
-
由 Tom Lane 提交于
for speed reasons; its result type also changes to int8. avg() on these datatypes now accumulates the running sum in int8 for speed; but we still deliver the final result as numeric, so that fractional accuracy is preserved. count() now counts and returns in int8, not int4. I am a little nervous about this possibly breaking users' code, but there didn't seem to be a strong sentiment for avoiding the problem. If we get complaints during beta, we can change count back to int4 and add a "count8" aggregate. For that matter, users can do it for themselves with a simple CREATE AGGREGATE command; the int4inc function is still present, so no C hacking is needed. Also added max() and min() aggregates for OID that do proper unsigned comparison, instead of piggybacking on int4 aggregates. initdb forced.
-
- 10 7月, 2001 1 次提交
-
-
由 Tom Lane 提交于
in cases of qualified rules as well as unqualified ones. Tweak rules test to avoid cluttering output with dummy SELECT results. Update documentation to match code.
-
- 06 12月, 2000 1 次提交
-
-
由 Tom Lane 提交于
-
- 13 9月, 2000 1 次提交
-
-
由 Tom Lane 提交于
ends to clean up (see my message of same date to pghackers), but mostly it works. INITDB REQUIRED!
-
- 20 4月, 2000 1 次提交
-
-
由 Tom Lane 提交于
know if that case ever breaks again...
-
- 06 1月, 2000 1 次提交
-
-
由 Thomas G. Lockhart 提交于
-
- 01 8月, 1999 1 次提交
-
-
由 Tom Lane 提交于
every time I tweak the optimizer...
-
- 17 5月, 1999 1 次提交
-
-
由 Jan Wieck 提交于
Jan
-
- 13 5月, 1999 1 次提交
-
-
由 Jan Wieck 提交于
pg_rules to rules regression test. Jan
-
- 15 4月, 1999 1 次提交
-
-
由 Tom Lane 提交于
in rules regression test, in order to eliminate bogus test 'failures' that occur due to platform-dependent and join-implementation-dependent ordering of tuples. I'm not sure that I got all of the SELECTs that need ordering clauses --- we may need some more. But this takes care of the diffs between my platform and Jan's.
-
- 23 2月, 1999 1 次提交
-
-
由 Thomas G. Lockhart 提交于
string.
-
- 08 2月, 1999 2 次提交
-
-
由 Jan Wieck 提交于
Removed CURRENT keyword for rule queries and changed rules regression accordingly. CURRENT has beed announced to disappear in v6.5. Jan
-
由 Jan Wieck 提交于
rule system semantics by having Var nodes referenced across multiple parsetrees when rules split them. Added more tests to the rules regression test. The code in question resulted from v6.3 based development and was a little careless applied to the v6.5 source tree. Jan
-