165 Commits (1fe11fad543fcaaf9ae7826f1234530a9d59c1b0)

Author	SHA1	Message	Date
Vadim B. Mikheev	40ac5a692b	heap_delete returns int now (for non-functional deletes).	29 years ago
Bruce Momjian	1d8bbfd2e7	Make functions static where possible, enclose unused functions in #ifdef NOT_USED.	29 years ago
Bruce Momjian	ea5b5357cd	Remove more (void) and fix -Wall warnings.	29 years ago
Vadim B. Mikheev	b3d8beaa1a	Catch non-functional delete attempts.	29 years ago
Marc G. Fournier	159f8c63ad	From: Dan McGuirk <mcguirk@indirect.com> ... Reply-To: hackers@hub.org, Dan McGuirk <mcguirk@indirect.com> To: hackers@hub.org Subject: [HACKERS] tmin writeback optimization I was doing some profiling of the backend, and noticed that during a certain benchmark I was running somewhere between 30% and 75% of the backend's CPU time was being spent in calls to TransactionIdDidCommit() from HeapTupleSatisfiesNow() or HeapTupleSatisfiesItself() to determine that changed rows' transactions had in fact been committed even though the rows' tmin values had not yet been set. When a query looks at a given row, it needs to figure out whether the transaction that changed the row has been committed and hence it should pay attention to the row, or whether on the other hand the transaction is still in progress or has been aborted and hence the row should be ignored. If a tmin value is set, it is known definitively that the row's transaction has been committed. However, if tmin is not set, the transaction referred to in xmin must be looked up in pg_log, and this is what the backend was spending a lot of time doing during my benchmark. So, implementing a method suggested by Vadim, I created the following patch that, the first time a query finds a committed row whose tmin value is not set, sets it, and marks the buffer where the row is stored as dirty. (It works for tmax, too.) This doesn't result in the boost in real time performance I was hoping for, however it does decrease backend CPU usage by up to two-thirds in certain situations, so it could be rather beneficial in high-concurrency settings.	29 years ago
Bruce Momjian	94515e3522	Removed unlinked patch that is not neede now that Vadim has properly fixed it.	29 years ago
Bruce Momjian	6da0055274	Fix for SELECT INTO ... GROUP/ORDER BY where table already exists unlink error.	29 years ago
Marc G. Fournier	466f5fd729	More cleanups	30 years ago
Marc G. Fournier	302b809793	Changes required so that access/* compiles cleanly... ... cleaning up behind myself before *yawn* bed :)	30 years ago
Marc G. Fournier	f578f8fb68	Cleaned out -I../.. -I../../include from Makefile ... Added missing include files	30 years ago
Marc G. Fournier	b446f38510	-Wall'd	30 years ago
Marc G. Fournier	5a0b450c78	First pass at fixing my own mistakes ... Mainly...fix up the includes I removed, as well as prototypes Pointed out by D'Arcy	30 years ago
Marc G. Fournier	dd007d4c39	Another directory cleaned out	30 years ago
Marc G. Fournier	208a30f23d	The patch does several things: ... It adds a WITH OIDS option to the copy command, which allows dumping and loading of oids. If a copy command tried to load in an oid that is greater than its current system max oid, the system max oid is incremented. No checking is done to see if other backends are running and have cached oids. pg_dump as its first step when using the -o (oid) option, will copy in a dummy row to set the system max oid value so as rows are loaded in, they are certain to be lower than the system oid. pg_dump now creates indexes at the end to speed loading Submitted by: Bruce Momjian <maillist@candle.pha.pa.us>	30 years ago
Marc G. Fournier	d31084e9d1	Postgres95 1.01 Distribution - Virgin Sources	30 years ago