- 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.
-
- 11 8月, 2001 2 次提交
-
-
由 Tom Lane 提交于
default, but OIDS are removed from many system catalogs that don't need them. Some interesting side effects: TOAST pointers are 20 bytes not 32 now; pg_description has a three-column key instead of one. Bugs fixed in passing: BINARY cursors work again; pg_class.relhaspkey has some usefulness; pg_dump dumps comments on indexes, rules, and triggers in a valid order. initdb forced.
-
由 Tom Lane 提交于
-
- 10 8月, 2001 2 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
consistent type naming.
-
- 07 8月, 2001 2 次提交
-
-
由 Tom Lane 提交于
since it's completely redundant with regress.sgml. I think we agreed to remove it awhile back, actually, but no one got around to doing it.
-
由 Peter Eisentraut 提交于
Add some resultmap entries for SCO OpenServer.
-
- 16 7月, 2001 3 次提交
-
-
由 Tom Lane 提交于
Note: I didn't force an initdb, figuring that one today was enough. However, there is a new function in pg_proc.h, and pg_dump won't be able to dump partial indexes until you add that function.
-
由 Tom Lane 提交于
per previous discussion on pghackers. Most of the duplicate code in different AMs' ambuild routines has been moved out to a common routine in index.c; this means that all index types now do the right things about inserting recently-dead tuples, etc. (I also removed support for EXTEND INDEX in the ambuild routines, since that's about to go away anyway, and it cluttered the code a lot.) The retail indextuple deletion routines have been replaced by a "bulk delete" routine in which the indexscan is inside the access method. I haven't pushed this change as far as it should go yet, but it should allow considerable simplification of the internal bookkeeping for deletions. Also, add flag columns to pg_am to eliminate various hardcoded tests on AM OIDs, and remove unused pg_am columns. Fix rtree and gist index types to not attempt to store NULLs; before this, gist usually crashed, while rtree managed not to crash but computed wacko bounding boxes for NULL entries (which might have had something to do with the performance problems we've heard about occasionally). Add AtEOXact routines to hash, rtree, and gist, all of which have static state that needs to be reset after an error. We discovered this need long ago for btree, but missed the other guys. Oh, one more thing: concurrent VACUUM is now the default.
-
由 Tom Lane 提交于
as predictable as it used to be, due to recycling of free space with new VACUUM.
-
- 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.
-
- 03 7月, 2001 1 次提交
-
-
由 Tom Lane 提交于
Probably the right fix is to remove 'current' special value entirely, but I don't want to see regression test failures until that happens.
-
- 23 6月, 2001 1 次提交
-
-
由 Jan Wieck 提交于
it's hard to keep such massive changes in sync with the tree so I need to get it in and work from there now). Jan
-
- 19 6月, 2001 1 次提交
-
-
由 Bruce Momjian 提交于
functions to clear date cache. Allow regression tests to pass when timezone set.
-
- 17 6月, 2001 1 次提交
-
-
由 Tom Lane 提交于
-
- 15 6月, 2001 1 次提交
-
-
由 Tom Lane 提交于
pg_stats to provide controlled (and, hopefully, more readable) access to statistics. Comments on definition of pg_stats welcome. I didn't force initdb, but the rules regress test will fail until you do one.
-
- 14 6月, 2001 2 次提交
-
-
由 Tom Lane 提交于
Tom Lane). For the moment, only the OID/name variants are provided. I didn't force initdb, but the additions to the 'privileges' regress test won't pass until you do one.
-
由 Bruce Momjian 提交于
inet(text), cidr(text): convert a text value into inet/cidr set_masklen(inet): set masklen on the inet value Patch also contains regression checks for these functions. Alex Pilosov
-
- 13 6月, 2001 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 12 6月, 2001 2 次提交
-
-
由 Bruce Momjian 提交于
It "make"s and "make check"s clean against current cvs tip. There are now both Text and Name variants, and the regression test support is rolled into the patch. Note that to be complete wrt Name based variants, there are now 12 user visible versions of has_table_privilege: has_table_privilege(Text usename, Text relname, Text priv_type) has_table_privilege(Text usename, Name relname, Text priv_type) has_table_privilege(Name usename, Text relname, Text priv_type) has_table_privilege(Name usename, Name relname, Text priv_type) has_table_privilege(Text relname, Text priv_type) /* assumes current_user */ has_table_privilege(Name relname, Text priv_type) /* assumes current_user */ has_table_privilege(Text usename, Oid reloid, Text priv_type) has_table_privilege(Name usename, Oid reloid, Text priv_type) has_table_privilege(Oid reloid, Text priv_type) /* assumes current_user */ has_table_privilege(Oid usesysid, Text relname, Text priv_type) has_table_privilege(Oid usesysid, Name relname, Text priv_type) has_table_privilege(Oid usesysid, Oid reloid, Text priv_type) For the Text based inputs, a new internal function, get_Name is used (shamelessly copied from get_seq_name in sequence.c) to downcase if not quoted, or remove quotes if quoted, and truncate. I also added a few test cases for the downcasing, quote removal, and Name based variants to the regression test. Joe Conway
-
由 Tom Lane 提交于
pg_database now has unique indexes on oid and on datname. pg_shadow now has unique indexes on usename and on usesysid. pg_am now has unique index on oid. pg_opclass now has unique index on oid. pg_amproc now has unique index on amid+amopclaid+amprocnum. Remove pg_rewrite's unnecessary index on oid, delete unused RULEOID syscache. Remove index on pg_listener and associated syscache for performance reasons (caching rows that are certain to change before you need 'em again is rather pointless). Change pg_attrdef's nonunique index on adrelid into a unique index on adrelid+adnum. Fix various incorrect settings of pg_class.relisshared, make that the primary reference point for whether a relation is shared or not. IsSharedSystemRelationName() is now only consulted to initialize relisshared during initial creation of tables and indexes. In theory we might now support shared user relations, though it's not clear how one would get entries for them into pg_class &etc of multiple databases. Fix recently reported bug that pg_attribute rows created for an index all have the same OID. (Proof that non-unique OID doesn't matter unless it's actually used to do lookups ;-)) There's no need to treat pg_trigger, pg_attrdef, pg_relcheck as bootstrap relations. Convert them into plain system catalogs without hardwired entries in pg_class and friends. Unify global.bki and template1.bki into a single init script postgres.bki, since the alleged distinction between them was misleading and pointless. Not to mention that it didn't work for setting up indexes on shared system relations. Rationalize locking of pg_shadow, pg_group, pg_attrdef (no need to use AccessExclusiveLock where ExclusiveLock or even RowExclusiveLock will do). Also, hold locks until transaction commit where necessary.
-
- 10 6月, 2001 1 次提交
-
-
由 Peter Eisentraut 提交于
for GRANT/REVOKE is now just that, not "CHANGE". On the way, migrate some of the aclitem internal representation away from the parser and build a real parse tree instead. Also add some 'const' qualifiers.
-
- 05 6月, 2001 1 次提交
-
-
由 Bruce Momjian 提交于
types. This version has an elog() to remind the user the type resolution is not dynamic. Ian Lance Taylor
-
- 02 6月, 2001 1 次提交
-
-
由 Tom Lane 提交于
right, but it failed to get the padding case right. This was obscured by subsequent application of bpchar() in all but one regression test case, and that one didn't fail in an obvious way --- trailing blanks are hard to see. Add another test case to make it more obvious if it breaks again.
-
- 30 5月, 2001 1 次提交
-
-
由 Bruce Momjian 提交于
when added by alter table add constraint. The first file patches backend/commands/command.c and the latter is a patch to the alter table regression test. Stephan Szabo
-
- 27 5月, 2001 1 次提交
-
-
由 Peter Eisentraut 提交于
privileges. INSERT and COPY FROM now require INSERT (only). Add privileges regression test.
-
- 23 5月, 2001 1 次提交
-
-
由 Peter Eisentraut 提交于
to do that, but inconsistently.) Make bit type reject too short input, too, per SQL. Since it no longer zero pads, 'zpbit*' has been renamed to 'bit*' in the source, hence initdb.
-
- 22 5月, 2001 1 次提交
-
-
由 Peter Eisentraut 提交于
too long. While I was adjusting the regression tests I moved the array things all into array.sql, to make things more manageable.
-
- 21 5月, 2001 1 次提交
-
-
由 Tom Lane 提交于
create_index_paths are not immediately discarded, but are available for subsequent planner work. This allows avoiding redundant syscache lookups in several places. Change interface to operator selectivity estimation procedures to allow faster and more flexible estimation. Initdb forced due to change of pg_proc entries for selectivity functions!
-
- 19 5月, 2001 1 次提交
-
-
由 Tom Lane 提交于
aggregate seems uniquely fragile, because it's the only one with an agginitval that's at all likely to change in format.
-
- 15 5月, 2001 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 11 5月, 2001 2 次提交
-
-
由 Tom Lane 提交于
name in two different tests. This solution does not meet with universal approval, so it may get changed later ...
-
由 Bruce Momjian 提交于
-
- 10 5月, 2001 1 次提交
-
-
由 Bruce Momjian 提交于
in referencing and referenced columns of an fk constraint aren't comparable using '=' at constraint definition time rather than insert/update time. Stephan Szabo
-
- 07 5月, 2001 1 次提交
-
-
由 Tom Lane 提交于
a separate statement (though it can still be invoked as part of VACUUM, too). pg_statistic redesigned to be more flexible about what statistics are stored. ANALYZE now collects a list of several of the most common values, not just one, plus a histogram (not just the min and max values). Random sampling is used to make the process reasonably fast even on very large tables. The number of values and histogram bins collected is now user-settable via an ALTER TABLE command. There is more still to do; the new stats are not being used everywhere they could be in the planner. But the remaining changes for this project should be localized, and the behavior is already better than before. A not-very-related change is that sorting now makes use of btree comparison routines if it can find one, rather than invoking '<' twice.
-
- 04 5月, 2001 1 次提交
-
-
由 Tom Lane 提交于
give consistent results for all datatypes. Types float4, float8, and numeric were broken for NaN values; abstime, timestamp, and interval were broken for INVALID values; timetz was just plain broken (some possible pairs of values were neither < nor = nor >). Also clean up text, bpchar, varchar, and bit/varbit to eliminate duplicate code and thereby reduce the probability of similar inconsistencies arising in the future.
-
- 06 4月, 2001 1 次提交
-
-
由 Thomas G. Lockhart 提交于
(which failed miserably during DST) to just compare against a time derived from a timestamp value. Certainly not a direct check for a correct result, but should work at any time of year.
-
- 05 4月, 2001 2 次提交