12 Commits (262c71ab63d5781cd68b23d2058cbb45ad67a54c)

Author	SHA1	Message	Date
Bruce Momjian	d747140279	8.4 pgindent run, with new combined Linux/FreeBSD/MinGW typedef list ... provided by Andrew.	17 years ago
Alvaro Herrera	a3540b0f65	Improve our #include situation by moving pointer types away from the ... corresponding struct definitions. This allows other headers to avoid including certain highly-loaded headers such as rel.h and relscan.h, instead using just relcache.h, heapam.h or genam.h, which are more lightweight and thus cause less unnecessary dependencies.	17 years ago
Alvaro Herrera	f8c4d7db60	Restructure some header files a bit, in particular heapam.h, by removing some ... unnecessary #include lines in it. Also, move some tuple routine prototypes and macros to htup.h, which allows removal of heapam.h inclusion from some .c files. For this to work, a new header file access/sysattr.h needed to be created, initially containing attribute numbers of system columns, for pg_dump usage. While at it, make contrib ltree, intarray and hstore header files more consistent with our header style.	18 years ago
Alvaro Herrera	73b0300b2a	Move the HTSU_Result enum definition into snapshot.h, to avoid including ... tqual.h into heapam.h. This makes all inclusion of tqual.h explicit. I also sorted alphabetically the includes on some source files.	18 years ago
Tom Lane	895a94de6d	Avoid incrementing the CommandCounter when CommandCounterIncrement is called ... but no database changes have been made since the last CommandCounterIncrement. This should result in a significant improvement in the number of "commands" that can typically be performed within a transaction before hitting the 2^32 CommandId size limit. In particular this buys back (and more) the possible adverse consequences of my previous patch to fix plan caching behavior. The implementation requires tracking whether the current CommandCounter value has been "used" to mark any tuples. CommandCounter values stored into snapshots are presumed not to be used for this purpose. This requires some small executor changes, since the executor used to conflate the curcid of the snapshot it was using with the command ID to mark output tuples with. Separating these concepts allows some small simplifications in executor APIs. Something for the TODO list: look into having CommandCounterIncrement not do AcceptInvalidationMessages. It seems fairly bogus to be doing it there, but exactly where to do it instead isn't clear, and I'm disinclined to mess with asynchronous behavior during late beta.	18 years ago
Tom Lane	89fefd9416	Reduce the permissions check needed to use pgrowlocks() to having ... SELECT on the target table. Per discussion.	18 years ago
Tom Lane	56f3fb3ba1	Restrict pgrowlocks function to superusers. (This might be too strict, ... but no permissions check at all is certainly no good.) Clean up usage of some deprecated APIs.	18 years ago
Bruce Momjian	f99a569a2e	pgindent run for 8.2.	19 years ago
Bruce Momjian	66c15dfda1	Adjust /contrib for new include file contents.	19 years ago
Tom Lane	a0ffab351e	Magic blocks don't do us any good unless we use 'em ... so install one ... in every shared library.	20 years ago
Tatsuo Ishii	a34fd95977	Fix bug reported by Michael Fuhr on Sun, 23 Apr 2006 09:52:31 -0600 ... (pgsql-committers@postgresql.org).	20 years ago
Tatsuo Ishii	66126f9687	Add new contrib function pgrowlocks. See README.pgrowlocks for more details.	20 years ago