- 28 6月, 2001 1 次提交
-
-
由 Tom Lane 提交于
do anything yet, but it has the necessary connections to initialization and so forth. Make some gestures towards allowing number of blocks in a relation to be BlockNumber, ie, unsigned int, rather than signed int. (I doubt I got all the places that are sloppy about it, yet.) On the way, replace the hardwired NLOCKS_PER_XACT fudge factor with a GUC variable.
-
- 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
-
- 14 6月, 2001 1 次提交
-
-
由 Tom Lane 提交于
database, including system catalogs (but not the shared catalogs, since they don't really belong to his database). This is per recent mailing list discussion. Clean up some other code that also checks for database ownerness by introducing a test function is_dbadmin().
-
- 25 5月, 2001 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Python) to support shared extension modules, I have learned that Guido prefers the style of the attached patch to solve the above problem. I feel that this solution is particularly appropriate in this case because the following: PglargeType PgType PgQueryType are already being handled in the way that I am proposing for PgSourceType. Jason Tishler
-
- 19 5月, 2001 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 17 5月, 2001 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
library code. Tweak progress messages to include elapsed real time, not only CPU time.
-
- 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.
-
- 26 3月, 2001 1 次提交
-
-
由 Tom Lane 提交于
-
- 22 3月, 2001 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 14 3月, 2001 1 次提交
-
-
由 Hiroshi Inoue 提交于
-
- 25 1月, 2001 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 24 1月, 2001 1 次提交
-
-
由 Tom Lane 提交于
-
- 20 1月, 2001 1 次提交
-
-
由 Tom Lane 提交于
into distinct concepts, per recent discussion on pghackers.
-
- 14 1月, 2001 1 次提交
-
-
由 Tom Lane 提交于
are treated more like 'cancel' interrupts: the signal handler sets a flag that is examined at well-defined spots, rather than trying to cope with an interrupt that might happen anywhere. See pghackers discussion of 1/12/01.
-
- 13 1月, 2001 1 次提交
-
-
由 Tom Lane 提交于
are now critical sections, so as to ensure die() won't interrupt us while we are munging shared-memory data structures. Avoid insecure intermediate states in some code that proc_exit will call, like palloc/pfree. Rename START/END_CRIT_CODE to START/END_CRIT_SECTION, since that seems to be what people tend to call them anyway, and make them be called with () like a function call, in hopes of not confusing pg_indent. I doubt that this is sufficient to make SIGTERM safe anywhere; there's just too much code that could get invoked during proc_exit().
-
- 30 12月, 2000 1 次提交
-
-
由 Vadim B. Mikheev 提交于
2. Log record for PageRepaireFragmentation now keeps array of !LP_USED offnums to redo cleanup properly.
-
- 28 12月, 2000 1 次提交
-
-
由 Vadim B. Mikheev 提交于
-
- 23 12月, 2000 1 次提交
-
-
由 Tom Lane 提交于
table that inherits from a temp table. Make sure the right things happen if one creates a temp table, creates another temp that inherits from it, then renames the first one. (Previously, system would end up trying to delete the temp tables in the wrong order.)
-
- 22 12月, 2000 1 次提交
-
-
由 Tom Lane 提交于
level" locks. A session lock is not released at transaction commit (but it is released on transaction abort, to ensure recovery after an elog(ERROR)). In VACUUM, use a session lock to protect the master table while vacuuming a TOAST table, so that the TOAST table can be done in an independent transaction. I also took this opportunity to do some cleanup and renaming in the lock code. The previously noted bug in ProcLockWakeup, that it couldn't wake up any waiters beyond the first non-wakeable waiter, is now fixed. Also found a previously unknown bug of the same kind (failure to scan all members of a lock queue in some cases) in DeadLockCheck. This might have led to failure to detect a deadlock condition, resulting in indefinite waits, but it's difficult to characterize the conditions required to trigger a failure.
-
- 08 12月, 2000 1 次提交
-
-
由 Hiroshi Inoue 提交于
-
- 03 12月, 2000 2 次提交
-
-
由 Vadim B. Mikheev 提交于
critical sections of code.
-
由 Tom Lane 提交于
a toasted datum in VACUUM ANALYZE.
-
- 30 11月, 2000 1 次提交
-
-
由 Vadim B. Mikheev 提交于
-
- 17 11月, 2000 1 次提交
-
-
由 Tom Lane 提交于
maintained for each cache entry. A cache entry will not be freed until the matching ReleaseSysCache call has been executed. This eliminates worries about cache entries getting dropped while still in use. See my posting to pg-hackers of even date for more info.
-
- 16 11月, 2000 1 次提交
-
-
由 Bruce Momjian 提交于
Context diff this time. Remove -m486 compile args for FreeBSD-i386, compile -O2 on i386. Compile with only -O on alpha for codegen safety. Make the port use the TEST_AND_SET for alpha and i386 on FreeBSD. Fix a lot of bogus string formats for outputting pointers (cast to int and %u/%x replaced with no cast and %p), and 'Size'(size_t) are now cast to 'unsigned long' and output with %lu/ Remove an unused variable. Alfred Perlstein
-
- 29 10月, 2000 1 次提交
-
-
由 Vadim B. Mikheev 提交于
-
- 24 10月, 2000 1 次提交
-
-
由 Vadim B. Mikheev 提交于
-
- 23 10月, 2000 1 次提交
-
-
由 Tom Lane 提交于
and destination of a tuple lie on the same page. (Previously fixed in REL7_0 branch, now apply to current.)
-
- 17 10月, 2000 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 06 10月, 2000 1 次提交
-
-
由 Bruce Momjian 提交于
Fix misspelling of disbursion to dispersion.
-
- 20 9月, 2000 1 次提交
-
-
由 Tom Lane 提交于
vacuum.c. This is needed to make the world safe for pg_upgrade.
-
- 12 9月, 2000 1 次提交
-
-
由 Bruce Momjian 提交于
for views. Views are now have a "relkind" of RELKIND_VIEW instead of RELKIND_RELATION. Also, views no longer have actual heap storage files. The following changes were made 1. CREATE VIEW sets the new relkind 2. The executor complains if a DELETE or INSERT references a view. 3. DROP RULE complains if an attempt is made to delete a view SELECT rule. 4. CREATE RULE "_RETmytable" AS ON SELECT TO mytable DO INSTEAD ... 1. checks to make sure mytable is empty. 2. sets the relkind to RELKIND_VIEW. 3. deletes the heap storage files. 5. LOCK myview is not allowed. :) 6. the regression test type_sanity was changed to account for the new relkind value. 7. CREATE INDEX ON myview ... is not allowed. 8. VACUUM myview is not allowed. VACUUM automatically skips views when do the entire database. 9. TRUNCATE myview is not allowed. THINGS LEFT TO THINK ABOUT o pg_views o pg_dump o pgsql (\d \dv) o Do we really want to be able to inherit from views? o Is 'DROP TABLE myview' OK? -- Mark Hollomon
-
- 06 9月, 2000 1 次提交
-
-
由 Peter Eisentraut 提交于
user is now defined in terms of the user id, the user name is only computed upon request (for display purposes). This is kind of the opposite of the previous state, which would maintain the user name and compute the user id for permission checks. Besides perhaps saving a few cycles (integer vs string), this now creates a single point of attack for changing the user id during a connection, for purposes of "setuid" functions, etc.
-
- 15 7月, 2000 1 次提交
-
-
由 Tom Lane 提交于
pass-by-ref data types --- eg, an index on lower(textfield) --- no longer leak memory during index creation or update. Clean up a lot of redundant code ... did you know that copy, vacuum, truncate, reindex, extend index, and bootstrap each basically duplicated the main executor's logic for extracting information about an index and preparing index entries? Functional indexes should be a little faster now too, due to removal of repeated function lookups. CREATE INDEX 'opt_type' clause is deimplemented by these changes, but I haven't removed it from the parser yet (need to merge with Thomas' latest change set first).
-
- 06 7月, 2000 1 次提交
-
-
由 Jan Wieck 提交于
Special handling of TOAST relations during VACUUM. TOAST relations are vacuumed while the lock on the master table is still active. The ANALYZE flag doesn't propagate to their vacuuming because the toaster access routines allways use index access ignoring stats, so why compute them at all. Protection of TOAST relations against normal INSERT/UPDATE/DELETE while offering SELECT for debugging purposes. Jan
-
- 28 6月, 2000 1 次提交
-
-
由 Tom Lane 提交于
for details). It doesn't really do that much yet, since there are no short-term memory contexts in the executor, but the infrastructure is in place and long-term contexts are handled reasonably. A few long- standing bugs have been fixed, such as 'VACUUM; anything' in a single query string crashing. Also, out-of-memory is now considered a recoverable ERROR, not FATAL. Eliminate a large amount of crufty, now-dead code in and around memory management. Fix problem with holding off SIGTRAP, SIGSEGV, etc in postmaster and backend startup.
-
- 18 6月, 2000 1 次提交
-
-
由 Tom Lane 提交于
discussion of 5/19/00). pg_index is now searched for indexes of a relation using an indexscan. Moreover, this is done once and cached in the relcache entry for the relation, in the form of a list of OIDs for the indexes. This list is used by the parser and executor to drive lookups in the pg_index syscache when they want to know the properties of the indexes. Net result: index information will be fully cached for repetitive operations such as inserts.
-
- 30 5月, 2000 1 次提交
-
-
由 Bruce Momjian 提交于
-