postgresql - postgresql mirror

	Commit message (Collapse)	Author	Age
*	Remove unnecessary parentheses in return statements	Peter Eisentraut	2017-09-05
\| \| \| \| \| \| \| \|	The parenthesized style has only been used in a few modules. Change that to use the style that is predominant across the whole tree. Reviewed-by: Michael Paquier <michael.paquier@gmail.com> Reviewed-by: Ryan Murphy <ryanfmurphy@gmail.com>
*	Establish conventions about global object names used in regression tests.	Tom Lane	2016-07-17
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	To ensure that "make installcheck" can be used safely against an existing installation, we need to be careful about what global object names (database, role, and tablespace names) we use; otherwise we might accidentally clobber important objects. There's been a weak consensus that test databases should have names including "regression", and that test role names should start with "regress_", but we didn't have any particular rule about tablespace names; and neither of the other rules was followed with any consistency either. This commit moves us a long way towards having a hard-and-fast rule that regression test databases must have names including "regression", and that test role and tablespace names must start with "regress_". It's not completely there because I did not touch some test cases in rolenames.sql that test creation of special role names like "session_user". That will require some rethinking of exactly what we want to test, whereas the intent of this patch is just to hit all the cases in which the needed renamings are cosmetic. There is no enforcement mechanism in this patch either, but if we don't add one we can expect that the tests will soon be violating the convention again. Again, that's not such a cosmetic change and it will require discussion. (But I did use a quick-hack enforcement patch to find these cases.) Discussion: <16638.1468620817@sss.pgh.pa.us>
*	Several fixes to array handling in ecpg.	Michael Meskes	2014-04-09
\| \| \| \|	Patches by Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>
*	Do not use the variable name when defining a varchar structure in ecpg.	Michael Meskes	2012-02-13
\| \| \| \|	With a unique counter being added anyway, there is no need anymore to have the variable name listed, too.
*	In ecpg's parser removed a fixed length limit for constants defining an ↵	Michael Meskes	2011-01-08
\| \| \| \|	array dimension.
*	Remove useless whitespace at end of lines	Peter Eisentraut	2010-11-23
\|
*	ecpg now adds a unique counter to its varchar struct definitions to make ↵	Michael Meskes	2010-03-09
\| \| \| \|	these definitions unique, too. It used to use the linenumber but in the rare case of two definitions in one line this was not unique.
*	More variables gcc moans about	Michael Meskes	2009-05-20
\|
*	First rounf of whitespace changes. Everything but connect-test1 should be fine.	Michael Meskes	2008-12-29
\|
*	Replaced manually synced preproc.y by the one created by the new script.	Michael Meskes	2008-11-11
\| \| \| \|	Adapted regression test files accordingly.
*	Fixed bug that caused arrays of varchar to be output with incomplete name.	Michael Meskes	2008-03-02
\| \| \| \|	In the process expanded one test case,
*	- Removed duplicate include of ecpgtype.h which meant I had to adapt all ↵	Michael Meskes	2008-02-17
\| \| \| \| \| \|	expected results. - Changed INFORMIX mode symbol definition yet again because the old way didn't work on NetBSD. Hopefully this one does.
*	Fixed compiler warning for enum handling	Michael Meskes	2007-08-14
\|
*	- Finished major rewrite to use new protocol version	Michael Meskes	2007-08-14
	- Really prepare statements - Added more regression tests - Added auto-prepare mode - Use '$n' for positional variables, '?' is still possible via ecpg option - Cleaned up the sources a little bit