summaryrefslogtreecommitdiff
path: root/contrib/intarray/bench
Commit message (Collapse)AuthorAgeFilesLines
* Update copyright for 2023Bruce Momjian2023-01-022-2/+2
| | | | Backpatch-through: 11
* Update copyright for 2022Bruce Momjian2022-01-072-2/+2
| | | | Backpatch-through: 10
* Prohibit map and grep in void contextDaniel Gustafsson2021-08-311-1/+1
| | | | | | | | | | | | | map and grep are not intended to be used as mutators, iterating with side-effects should be done with for or foreach loops. This fixes the one occurrence of the pattern, and bumps the perlcritic policy to severity 5 for the map and grep policies. Author: Dagfinn Ilmari Mannsåker <ilmari@ilmari.org> Reviewed-by: Michael Paquier <michael@paquier.xyz> Reviewed-by: Andrew Dunstan <andrew@dunslane.net> Reviewed-by: Julien Rouhaud <rjuju123@gmail.com> Discussion: https://postgr.es/m/87fsvzhhc4.fsf@wibble.ilmari.org
* Remove extraneous newlines added by perl copyright patchAndrew Dunstan2021-05-072-2/+0
|
* Add a copyright notice to perl files lacking one.Andrew Dunstan2021-05-072-0/+6
|
* Use perl warnings pragma consistentlyAndrew Dunstan2020-04-132-0/+3
| | | | | | | | | | We've had a mixture of the warnings pragma, the -w switch on the shebang line, and no warnings at all. This patch removes the -w swicth and add the warnings pragma to all perl sources missing it. It raises the severity of the TestingAndDebugging::RequireUseWarnings perlcritic policy to level 5, so that we catch any future violations. Discussion: https://postgr.es/m/20200412074245.GB623763@rfd.leadboat.com
* Don't fall off the end of perl functionsAndrew Dunstan2018-05-271-0/+1
| | | | | | | | | | | | | | | This complies with the perlcritic policy Subroutines::RequireFinalReturn, which is a severity 4 policy. Since we only currently check at severity level 5, the policy is raised to that level until we move to level 4 or lower, so that any new infringements will be caught. A small cosmetic piece of tidying of the pgperlcritic script is included. Mike Blackwell Discussion: https://postgr.es/m/CAESHdJpfFm_9wQnQ3koY3c91FoRQsO-fh02za9R3OEMndOn84A@mail.gmail.com
* Post-PG 10 beta1 pgperltidy runBruce Momjian2017-05-171-1/+2
|
* Clean up Perl code according to perlcriticPeter Eisentraut2017-03-271-10/+10
| | | | | | | | Fix all perlcritic warnings of severity level 5, except in src/backend/utils/Gen_dummy_probes.pl, which is automatically generated. Reviewed-by: Dagfinn Ilmari Mannsåker <ilmari@ilmari.org> Reviewed-by: Daniel Gustafsson <daniel@yesql.se>
* Fix -e option in contrib/intarray/bench/bench.pl.Tom Lane2016-08-171-1/+2
| | | | | | | | | | As implemented, -e ran an EXPLAIN but then discarded the output, which certainly seems pointless. Make it print to stdout instead. It's been like that forever, so back-patch to all supported branches. Daniel Gustafsson, reviewed by Andreas Scherbaum Patch: <B97BDCB7-A3B3-4734-90B5-EDD586941629@yesql.se>
* pgindent run for 9.4Bruce Momjian2014-05-061-1/+1
| | | | | This includes removing tabs after periods in C comments, which was applied to back branches, so this change should not effect backpatching.
* Fix whitespace issues found by git diff --check, add gitattributesPeter Eisentraut2013-11-101-1/+1
| | | | | Set per file type attributes in .gitattributes to fine-tune whitespace checks. With the associated cleanups, the tree is now clean for git
* Run newly-configured perltidy script on Perl files.Bruce Momjian2012-07-042-55/+96
| | | | Run on HEAD and 9.2.
* Remove useless whitespace at end of linesPeter Eisentraut2010-11-232-13/+13
|
* Remove cvs keywords from all files.Magnus Hagander2010-09-201-1/+1
|
* Remove extra newlines at end and beginning of files, add missing newlinesPeter Eisentraut2010-08-191-1/+0
| | | | at end of files.
* Add CVS tag lines to files that were lacking them.Bruce Momjian2006-03-111-0/+2
|
* Optimize benchmark query and update benchmark's results.Teodor Sigaev2005-10-031-1/+3
|
* Restructure pg_opclass, pg_amop, and pg_amproc per previous discussions inTom Lane2001-08-211-1/+1
| | | | | | | | | | | | | | | | | | | | pgsql-hackers. pg_opclass now has a row for each opclass supported by each index AM, not a row for each opclass name. This allows pg_opclass to show directly whether an AM supports an opclass, and furthermore makes it possible to store additional information about an opclass that might be AM-dependent. pg_opclass and pg_amop now store "lossy" and "haskeytype" information that we previously expected the user to remember to provide in CREATE INDEX commands. Lossiness is no longer an index-level property, but is associated with the use of a particular operator in a particular index opclass. Along the way, IndexSupportInitialize now uses the syscaches to retrieve pg_amop and pg_amproc entries. I find this reduces backend launch time by about ten percent, at the cost of a couple more special cases in catcache.c's IndexScanOK. Initial work by Oleg Bartunov and Teodor Sigaev, further hacking by Tom Lane. initdb forced.
* Update contrib intarray to Jan 25 version.Bruce Momjian2001-03-171-1/+1
|
* commit Oleg and Teodor's RD-tree implementation ... this provides theMarc G. Fournier2001-01-122-0/+177
regression tests for the GiST changes ... this should be integrated into the regular regression tests similar to Vadim's SPI contrib stuff ...
View Lorry Controller Status