18 Commits (e7128e8dbb305059c30ec085461297e619bcbff4)

Author	SHA1	Message	Date
Peter Eisentraut	e7128e8dbb	Create function prototype as part of PG_FUNCTION_INFO_V1 macro ... Because of gcc -Wmissing-prototypes, all functions in dynamically loadable modules must have a separate prototype declaration. This is meant to detect global functions that are not declared in header files, but in cases where the function is called via dfmgr, this is redundant. Besides filling up space with boilerplate, this is a frequent source of compiler warnings in extension modules. We can fix that by creating the function prototype as part of the PG_FUNCTION_INFO_V1 macro, which such modules have to use anyway. That makes the code of modules cleaner, because there is one less place where the entry points have to be listed, and creates an additional check that functions have the right prototype. Remove now redundant prototypes from contrib and other modules.	11 years ago
Peter Eisentraut	b8b2e3b2de	Replace int2/int4 in C code with int16/int32 ... The latter was already the dominant use, and it's preferable because in C the convention is that intXX means XX bits. Therefore, allowing mixed use of int2, int4, int8, int16, int32 is obviously confusing. Remove the typedefs for int2 and int4 for now. They don't seem to be widely used outside of the PostgreSQL source tree, and the few uses can probably be cleaned up by the time this ships.	13 years ago
Peter Eisentraut	1b81c2fe6e	Remove many -Wcast-qual warnings ... This addresses only those cases that are easy to fix by adding or moving a const qualifier or removing an unnecessary cast. There are many more complicated cases remaining.	14 years ago
Bruce Momjian	6416a82a62	Remove unnecessary #include references, per pgrminclude script.	14 years ago
Magnus Hagander	9f2e211386	Remove cvs keywords from all files.	15 years ago
Tom Lane	cd55aa2e00	Fix two new-in-9.0 bugs in hstore. ... There was an incorrect Assert in hstoreValidOldFormat(), which would cause immediate core dumps when attempting to work with pre-9.0 hstore data, but of course only in an assert-enabled build. Also, ghstore_decompress() incorrectly applied DatumGetHStoreP() to a datum that wasn't actually an hstore, but rather a ghstore (ie, a gist signature bitstring). That used to be harmless, but could now result in misbehavior if the hstore format conversion code happened to trigger. In reality, since ghstore is not marked toastable (and doesn't need to be), this function is useless anyway; we can lobotomize it down to returning the passed-in pointer. Both bugs found by Andrew Gierth, though this isn't exactly his proposed patch.	15 years ago
Bruce Momjian	65e806cba1	pgindent run for 9.0	16 years ago
Tom Lane	172eacba43	Assorted improvements in contrib/hstore. ... Remove the 64K limit on the lengths of keys and values within an hstore. (This changes the on-disk format, but the old format can still be read.) Add support for btree/hash opclasses for hstore --- this is not so much for actual indexing purposes as to allow use of GROUP BY, DISTINCT, etc. Add various other new functions and operators. Andrew Gierth	16 years ago
Bruce Momjian	d747140279	8.4 pgindent run, with new combined Linux/FreeBSD/MinGW typedef list ... provided by Andrew.	16 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.	17 years ago
Tom Lane	9b5c8d45f6	Push index operator lossiness determination down to GIST/GIN opclass ... "consistent" functions, and remove pg_amop.opreqcheck, as per recent discussion. The main immediate benefit of this is that we no longer need 8.3's ugly hack of requiring @@@ rather than @@ to test weight-using tsquery searches on GIN indexes. In future it should be possible to optimize some other queries better than is done now, by detecting at runtime whether the index match is exact or not. Tom Lane, after an idea of Heikki's, and with some help from Teodor.	17 years ago
Bruce Momjian	5f0bf6cb0d	Run pgindent on remaining files now that LOOPBYTE is a usable macro.	18 years ago
Bruce Momjian	224f91f66d	Modify LOOPBYTE/LOOPBIT macros to be more logical; rather than have the ... for() body passed as a parameter, make the macros act as simple headers to code blocks. This allows pgindent to be run on these files.	18 years ago
Tom Lane	3e23b68dac	Support varlena fields with single-byte headers and unaligned storage. ... This commit breaks any code that assumes that the mere act of forming a tuple (without writing it to disk) does not "toast" any fields. While all available regression tests pass, I'm not totally sure that we've fixed every nook and cranny, especially in contrib. Greg Stark with some help from Tom Lane	18 years ago
Teodor Sigaev	754148d81f	Add GIN support for pg_trgm. From Guillaume Smet <guillaume.smet@gmail.com> ... with minor editorization by me. Hstore improvements * add operation hstore ? text - excat equivalent of exist() * remove undocumented behaviour of contains operation with NULL value * now 'key'::text=>NULL returns '"key"=>NULL' instead of NULL * Add GIN support for contains and exist operations * Add GiST support for exist operatiion * improve regression tests	19 years ago
Tom Lane	9f652d430f	Fix up several contrib modules that were using varlena datatypes in not-so-obvious ... ways. I'm not totally sure that I caught everything, but at least now they pass their regression tests with VARSIZE/SET_VARSIZE defined to reverse byte order.	19 years ago
Bruce Momjian	f99a569a2e	pgindent run for 8.2.	19 years ago
Teodor Sigaev	642194ba0c	Add hstore contrib module. ... Per discussion http://archives.postgresql.org/pgsql-hackers/2006-08/msg01409.php	19 years ago