7263 Commits (0b56be83441c01419fcf82ebe666e968e6f7b246)

Author	SHA1	Message	Date
Tom Lane	5725b9d9af	Support type modifiers for user-defined types, and pull most knowledge ... about typmod representation for standard types out into type-specific typmod I/O functions. Teodor Sigaev, with some editorialization by Tom Lane.	19 years ago
Bruce Momjian	24b1f14eae	Clarify wording on when ctid is modified by VACUUM FULL.	19 years ago
Bruce Momjian	3870341d1e	Add TLS thread URL: ... > http://archives.postgresql.org/pgsql-hackers/2006-12/msg01213.php	19 years ago
Bruce Momjian	bb554e0d9c	Remove: ... < * Add a GUC to control whether BEGIN inside a transcation should abort < the transaction.	19 years ago
Tom Lane	e1b8a55ec8	Remove caveat about avoiding cross-type operators in constraints intended ... for use with constraint exclusion. We can prove those cases now...	19 years ago
Bruce Momjian	91868e7df0	Done: ... < * Move some /contrib modules out to their own project sites < < Particularly, move GPL-licensed /contrib/userlock and < /contrib/dbmirror/clean_pending.pl. <	19 years ago
Tom Lane	de9be563d4	Use FROM clause in example UPDATE commands where appropriate. Also ... remove long-obsolete statement that there isn't a check for infinite recursion in view rules.	19 years ago
Bruce Momjian	4f1e49119e	Use "dead" rather than "expired" for vacuumable rows.	19 years ago
Tom Lane	4a836bad3a	Remove incorrect semicolon in example. Joachim Wieland	19 years ago
Tom Lane	c957c0bac7	Code review for XML patch. Instill a bit of sanity in the location of ... the XmlExpr code in various lists, use a representation that has some hope of reverse-listing correctly (though it's still a de-escaping function shy of correctness), generally try to make it look more like Postgres coding conventions.	19 years ago
Bruce Momjian	ef5870350a	Change a VACUUM manual page word from 'deleted' to 'expired', so DELETE ... and UPDATE are clearly covered by the term.	19 years ago
Bruce Momjian	05911de4da	Document that CREATE TYPE names should not begin with an underscore, ... rather than being disallowed.	19 years ago
Tom Lane	a78fcfb512	Restructure operator classes to allow improved handling of cross-data-type ... cases. Operator classes now exist within "operator families". While most families are equivalent to a single class, related classes can be grouped into one family to represent the fact that they are semantically compatible. Cross-type operators are now naturally adjunct parts of a family, without having to wedge them into a particular opclass as we had done originally. This commit restructures the catalogs and cleans up enough of the fallout so that everything still works at least as well as before, but most of the work needed to actually improve the planner's behavior will come later. Also, there are not yet CREATE/DROP/ALTER OPERATOR FAMILY commands; the only way to create a new family right now is to allow CREATE OPERATOR CLASS to make one by default. I owe some more documentation work, too. But that can all be done in smaller pieces once this infrastructure is in place.	19 years ago
Bruce Momjian	d31ccb6c3e	Add a link to the developer's FAQ for my article about how companies can ... work effectively with open source communities.	19 years ago
Bruce Momjian	03d2a1c688	Slight adjustments to xml documentation to reflect functionality just ... added.	19 years ago
Peter Eisentraut	8c1de5fb00	Initial SQL/XML support: xml data type and initial set of functions.	19 years ago
Bruce Momjian	ed1e9cd501	8.3 release schedule is year 2007, not 2006.	19 years ago
Bruce Momjian	1cacb3a098	Add timeline for next release to developer's FAQ.	19 years ago
Bruce Momjian	f528e242fc	Item done. ... < o Improve xid wraparound detection by recording per-table rather < than per-database	19 years ago
Andrew Dunstan	5133dd786b	Interpret a dbName param to PQsetdbLogin as a conninfo string if it contains an = sign. Tom Lane and Andrew Dunstan.	19 years ago
Tom Lane	93b4f0ff77	Set pg_am.amstrategies to zero for index AMs that don't have fixed ... operator strategy numbers, ie, GiST and GIN. This is almost cosmetic enough to not need a catversion bump, but since the opr_sanity regression test has to change in sync with the catalog entry, I figured I'd better do one.	19 years ago
Bruce Momjian	cdcee16588	Fix typo: ... < While PostgreSQL clients runs fine limited-resource environments, the > While PostgreSQL clients runs fine in limited-resource environments, the	19 years ago
Bruce Momjian	6874fb90c0	Move entry into CLUSTER section: ... < * Make CLUSTER preserve recently-dead tuples per MVCC requirements > o Make CLUSTER preserve recently-dead tuples per MVCC requirements	19 years ago
Bruce Momjian	421c1ca48d	Back out double-run of PDF/PS output. Requires building bookindex.sgml ... properly. Remove SGML docs about openjade performance patch, and instead add comment in style sheet where indenting code is commented out. Backpatch to 8.2.X.	19 years ago
Bruce Momjian	8186e7ef89	TODO item not wanted: ... > > * Embedded server (not wanted) > > While PostgreSQL clients runs fine limited-resource environments, the > server requires multiple processes and a stable pool of resources to > run reliabily and efficiently. Stripping down the PostgreSQL server > to run in the same process address space as the client application > would add too much complexity and failure cases.	19 years ago
Bruce Momjian	2356c9fc4c	Link to summary XML email, rather than thread top: ... < * Consider changing documentation from SGML to XML > * Consider changing documentation format from SGML to XML < http://archives.postgresql.org/pgsql-docs/2006-12/msg00033.php > http://archives.postgresql.org/pgsql-docs/2006-12/msg00152.php	19 years ago
Bruce Momjian	eb838baf49	Document issues for SGML and XML: ... > > * Consider changing documentation from SGML to XML > > http://archives.postgresql.org/pgsql-docs/2006-12/msg00033.php >	19 years ago
Bruce Momjian	c4dfc4137e	Document patch needed to get PDF and PS output in a reasonable amount of ... time.	19 years ago
Bruce Momjian	9c92007029	Remove unneeded tab in file.	19 years ago
Bruce Momjian	6f84d53110	Run Jade twice when outputting Postscript and PDF so the index is ... correct, add comments about other multiple runs in the Makefile. Backpatch to 8.2.X.	19 years ago
Bruce Momjian	8283cd7663	Update entry: ... < * Have EXPLAIN ANALYZE highlight poor optimizer estimates > * Have EXPLAIN ANALYZE issue NOTICE messages when the estimated and > actual row counts differ by a specified percentage	19 years ago
Bruce Momjian	0afabecbfd	Document that log_line_prefix %t does not print timezone on Win32.	19 years ago
Bruce Momjian	faf69ee4a3	Oops, removed: ... < * Allow REINDEX CONCURRENTLY	19 years ago
Bruce Momjian	0f45c0890b	Add: ... > * Allow REINDEX CONCURRENTLY	19 years ago
Bruce Momjian	876ef5d5c9	Remove blank lines in HTML FAQ.	19 years ago
Bruce Momjian	051b52c886	Add FAQ entry to mention using COALESCE() for concatenation of possible ... NULLs.	19 years ago
Peter Eisentraut	314c7b642b	Make separate targets for building printable documentation in A4 and ... US letter paper formats.	19 years ago
Peter Eisentraut	5f1f30d136	Reorganize XSLT stylesheet support. Put common things into a separate ... file (instead of repeating), add XSL-FO stylesheet and appropriate make rules.	19 years ago
Peter Eisentraut	0a265e487b	Add some information about increasing JadeTeX parameters.	19 years ago
Peter Eisentraut	465269b8ad	Drop indentation of verbatim environments in print output. This increased ... the build time by what seemed like infinity.	19 years ago
Peter Eisentraut	c605441c79	Generalize Texinfo rules. Prevent them from overriding the PostScript ... build rules.	19 years ago
Tom Lane	0cb91ccba9	Remove the logId/logSeg fields from pg_control, because they are not needed ... in normal operation, and we can avoid rewriting pg_control at every log segment switch if we don't insist that these values be valid. Reducing the number of pg_control updates is a good idea for both performance and reliability. It does make pg_resetxlog's life a bit harder, but that seems a good tradeoff; and anyway the change to pg_resetxlog amounts to automating something people formerly needed to do by hand, namely look at the existing pg_xlog files to make sure the new WAL start point was past them. In passing, change the wording of xlog.c's "database system was interrupted" messages: describe the pg_control timestamp as "last known up at" rather than implying it is the exact time of service interruption. With this change the timestamp will generally be the time of the last checkpoint, which could be many minutes before the failure; and we've already seen indications that people tend to misinterpret the old wording. initdb forced due to change in pg_control layout. Simon Riggs and Tom Lane	19 years ago
Tom Lane	98cacd1a0a	Fix broken markup.	19 years ago
Neil Conway	886a02d1cb	Add a txn_start column to pg_stat_activity. This makes it easier to ... identify long-running transactions. Since we already need to record the transaction-start time (e.g. for now()), we don't need any additional system calls to report this information. Catversion bumped, initdb required.	19 years ago
Bruce Momjian	a39e3958e9	Change psql \\ example to use single quotes, per TOm.	19 years ago
Bruce Momjian	a4242d7f87	Back out mention of port success from FAQs, per Tom, added by Simon.	19 years ago
Bruce Momjian	d7f316d28e	Clean up psql -c documentation that uses \\.	19 years ago
Bruce Momjian	a6f156b931	Make URL to docs use /current/.	19 years ago
Bruce Momjian	c08cfab407	Fix documentation example of using psql \x with a SELECT command, per ... Simon Riggs. Backpatch to 8.2.X.	19 years ago
Bruce Momjian	5b2def8969	Update of port patches, HEAD patch only. ... Simon Riggs	19 years ago