postgres

Commit Graph

Author	SHA1	Message	Date
Bruce Momjian	6ceebcac3a	Adjust question spacing.	21 years ago
Tom Lane	4eec2f2407	Update misleading comment about the use of lanpltrusted ... it is significant regardless of the value of lanispl.	21 years ago
Bruce Momjian	051ecca022	Remove documentation that CSV didn't handle carriage returns and line feeds properly.	21 years ago
Tom Lane	160ca10609	Per core discussion, we should push out a 7.2.* release too while we are at it. Add release notes.	21 years ago
Bruce Momjian	e6e7e64345	Update "control" item. Rosser Schwarz	21 years ago
Bruce Momjian	45c2171024	Typo fix, Dave Held	21 years ago
Tom Lane	a5ed98ba5a	Preliminary release notes for 8.0.3, 7.4.8, 7.3.10.	21 years ago
Tom Lane	893b57c871	Alter the signature for encoding conversion functions to declare the output area as INTERNAL not CSTRING. This is to prevent people from calling the functions by hand. This is a permanent solution for the back branches but I hope it is just a stopgap for HEAD.	21 years ago
Bruce Momjian	47ce51c04a	Add FAQ on who controls the project.	21 years ago
Bruce Momjian	3de0e72b56	Completed: < * Remove unreferenced table files created by transactions that were > * -Check for unreferenced table files created by transactions that were	21 years ago
Bruce Momjian	76668e6eb4	Check the file system on postmaster startup and report any unreferenced files in the server log. Heikki Linnakangas	21 years ago
Neil Conway	b656150ec0	Add some missing "See Also" entries to the domain-related SQL reference pages. From Robert Treat.	21 years ago
Neil Conway	f478856c7f	Change SPI functions to use a `long' when specifying the number of tuples to produce when running the executor. This is consistent with the internal executor APIs (such as ExecutorRun), which also use a long for this purpose. It also allows FETCH_ALL to be passed -- since FETCH_ALL is defined as LONG_MAX, this wouldn't have worked on platforms where int and long are of different sizes. Per report from Tzahi Fadida.	21 years ago
Tom Lane	6c412f0605	Change CREATE TYPE to require datatype output and send functions to have only one argument. (Per recent discussion, the option to accept multiple arguments is pretty useless for user-defined types, and would be a likely source of security holes if it was used.) Simplify call sites of output/send functions to not bother passing more than one argument.	21 years ago
Tom Lane	ae793ff63c	Fix incorrect backslashing in regexp example, per Robert Treat.	21 years ago
Tom Lane	768eaf1416	Mention the actual stored size of NUMERIC values, per David Fetter.	21 years ago
Bruce Momjian	23cf3986cf	Update FAQ.	21 years ago
Bruce Momjian	ef1b4fbb56	Update replication FAQ. Christopher Browne	21 years ago
Bruce Momjian	daec16d0ba	Done: > * -Implement shared row locks and use them in RI triggers	21 years ago
Tom Lane	bedb78d386	Implement sharable row-level locks, and use them for foreign key references to eliminate unnecessary deadlocks. This commit adds SELECT ... FOR SHARE paralleling SELECT ... FOR UPDATE. The implementation uses a new SLRU data structure (managed much like pg_subtrans) to represent multiple- transaction-ID sets. When more than one transaction is holding a shared lock on a particular row, we create a MultiXactId representing that set of transactions and store its ID in the row's XMAX. This scheme allows an effectively unlimited number of row locks, just as we did before, while not costing any extra overhead except when a shared lock actually has to be shared. Still TODO: use the regular lock manager to control the grant order when multiple backends are waiting for a row lock. Alvaro Herrera and Tom Lane.	21 years ago
Bruce Momjian	a65b1b738c	Add psql \set ON_ERROR_ROLLBACK to allow statements in a transaction to error without affecting the entire transaction. Valid values are "on\|interactive\|off".	21 years ago
Bruce Momjian	989b55c550	Wording improvement.	21 years ago
Bruce Momjian	d3ee0279d6	Update PAM documentation, per Alvaro.	21 years ago
Bruce Momjian	eceb05b0b9	Mention that PAM requires the user already exist in the database, per Dick Davies.	21 years ago
Bruce Momjian	238fb0342e	Update description: < * Allow ORDER BY ... LIMIT 1 to select high/low value without sort or > * Allow ORDER BY ... LIMIT # to select high/low value without sort or 868c868 < Right now, if no index exists, ORDER BY ... LIMIT 1 requires we sort > Right now, if no index exists, ORDER BY ... LIMIT # requires we sort 870a871 > MIN/MAX already does this, but not for LIMIT > 1.	21 years ago
Bruce Momjian	61cf53516e	Re-add item with better description: > * Allow ORDER BY ... LIMIT 1 to select high/low value without sort or > index using a sequential scan for highest/lowest values > > Right now, if no index exists, ORDER BY ... LIMIT 1 requires we sort > all values to return the high/low value. Instead The idea is to do a > sequential scan to find the high/low value, thus avoiding the sort. >	21 years ago
Bruce Momjian	7a4c34c97c	Add description for concurrent sequential scans: > One possible implementation is to start sequential scans from the lowest > numbered buffer in the shared cache, and when reaching the end wrap > around to the beginning, rather than always starting sequential scans > at the start of the table.	21 years ago
Bruce Momjian	cdf39c7b61	Update wording: < This allows vacuum to reclaim free space without requiring < a sequential scan > This allows vacuum to target specific pages for possible free space > without requiring a sequential scan.	21 years ago
Bruce Momjian	5131b5bc7a	Update wording.	21 years ago
Bruce Momjian	c1cc62f614	Clean up HTML.	21 years ago
Bruce Momjian	7a35c637bc	Add replication FAQ item.	21 years ago
Bruce Momjian	a7f2a788ee	Add line break.	21 years ago
Bruce Momjian	6f8f0a9d7a	Update book items.	21 years ago
Bruce Momjian	ac8998f2e6	Turns out our existing page size is already optimal in most cases: < * Research the use of larger page sizes	21 years ago
Bruce Momjian	f4dcb52efe	Item already added to existing 'thread' item: < * Consider parallel processing a single query < < This would involve using multiple threads or processes to do optimization, < sorting, or execution of single query. The major advantage of such a < feature would be to allow multiple CPUs to work together to process a < single query. <	21 years ago
Bruce Momjian	6869683147	Remove item, not sure what it refers to: < * Allow ORDER BY ... LIMIT 1 to select high/low value without sort or < index using a sequential scan for highest/lowest values < < If only one value is needed, there is no need to sort the entire < table. Instead a sequential scan could get the matching value. <	21 years ago
Bruce Momjian	1207d5b64e	New item: > * Change WAL to use 32-bit CRC, for performance reasons	21 years ago
Bruce Momjian	e847558031	Update threading item: < Solaris) might benefit from threading. > Solaris) might benefit from threading. Also explore the idea of > a single session using multiple threads to execute a query faster.	21 years ago
Bruce Momjian	bb62899db5	Done: < * Improve SMP performance on i386 machines > * -Improve SMP performance on i386 machines	21 years ago
Bruce Momjian	95c7bff47c	Done: < * Optimize locale to have minimal performance impact when not used	21 years ago
Bruce Momjian	9ff49665ce	Fix typo: < * Add ISo INTERVAL handling > * Add ISO INTERVAL handling	21 years ago
Bruce Momjian	e8ad6d9666	Move info about lack of depencency checking in Makefiles to developer's faq.q	21 years ago
Bruce Momjian	f7e514d010	Update FAQ by eliminating non-frequent items like large objects and extending questions. Update wording of various entries.	21 years ago
Bruce Momjian	48e7a196ea	Done: > * -Allow non-bitmap indexes to be combined by creating bitmaps in memory	21 years ago
Bruce Momjian	97a4dad35f	Update H4 tag to H3 to be consistent with heading levels.	21 years ago
Bruce Momjian	9f1e864d02	Add item about server-side debugging.	21 years ago
Bruce Momjian	c34ea747a6	Update FAQ items to point to existing web pages rather than duplication such information. Remove MySQL mention. Move server-side debug item to developer's FAQ. Update URLs.	21 years ago
Bruce Momjian	0975b95bc3	Update FAQ release number to 8.0.2.	21 years ago
Bruce Momjian	25434e32cb	Add documentation stating how to determine if FSM settings are too low --- look at a database-wide VACUUM VERBOSE.	21 years ago
Bruce Momjian	ccbb07d922	Fix typo: < Currently indexes do not have enough tuple tuple visibility < information to allow data to be pulled from the index without < also accessing the heap. One way to allow this is to set a bit < to index tuples to indicate if a tuple is currently visible to < all transactions when the first valid heap lookup happens. This < bit would have to be cleared when a heap tuple is expired. > Currently indexes do not have enough tuple visibility information > to allow data to be pulled from the index without also accessing > the heap. One way to allow this is to set a bit to index tuples > to indicate if a tuple is currently visible to all transactions > when the first valid heap lookup happens. This bit would have to > be cleared when a heap tuple is expired.	21 years ago

... 3 4 5 6 7 ...

3951 Commits (d51df918970bcf42f915a3882bfdee5972aa9bad)