| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | plpython: Remove regression test infrastructure for Python 2. | Andres Freund | 2022-03-07 | 1 | -3/+1 |
| | | | | | | | | | | | Since 19252e8ec93 we reject Python 2 during build configuration. Now that the dust on the buildfarm has settled, remove regression testing infrastructure dealing with differing output between Python 2 / 3. Reviewed-By: Peter Eisentraut <peter@eisentraut.org> Reviewed-By: Tom Lane <tgl@sss.pgh.pa.us> Discussion: https://postgr.es/m/20211031184548.g4sxfe47n2kyi55r@alap3.anarazel.de | ||||
| * | Create extension infrastructure for the core procedural languages. | Tom Lane | 2011-03-04 | 1 | -1/+3 |
| | | | | | | | | | | | | | | | | | | | | | This mostly just involves creating control, install, and update-from-unpackaged scripts for them. However, I had to adjust plperl and plpython to not share the same support functions between variants, because we can't put the same function into multiple extensions. catversion bump forced due to new contents of pg_pltemplate, and because initdb now installs plpgsql as an extension not a bare language. Add support for regression testing these as extensions not bare languages. Fix a couple of other issues that popped up while testing this: my initial hack at pg_dump binary-upgrade support didn't work right, and we don't want an extra schema permissions test after all. Documentation changes still to come, but I'm committing now to see whether the MSVC build scripts need work (likely they do). | ||||
| * | Convert the existing regression test scripts for the various optional | Tom Lane | 2005-05-14 | 1 | -0/+6 |
| PLs to use the standard pg_regress infrastructure. No changes in the tests themselves. Andrew Dunstan | |||||
 |
index : delta/postgresql.git | |
| git.postgresql.org: git/postgresql.git |
| summaryrefslogtreecommitdiff |