7559d8ebfa
Update copyrights for 2020
...
Backpatch-through: update all files in master, backpatch legal files through 9.4
2020-01-01 12:21:45 -05:00
e1f4c481b9
Remove unnecessary #include <limits.h>
...
This include was probably copied from tuplestore.c, but it's not needed.
Extracted from a larger patch submitted by vignesh C <vignesh21@gmail.com>
Discussion: https://postgr.es/m/CALDaNm1B9naPDTm3ox1m_yZvOm3KA5S4kZQSWWAeLHAQ=3gV1Q@mail.gmail.com
2019-08-07 16:55:31 -04:00
3412030205
Fix more typos and inconsistencies in the tree
...
Author: Alexander Lakhin
Discussion: https://postgr.es/m/0a5419ea-1452-a4e6-72ff-545b1a5a8076@gmail.com
2019-06-17 16:13:16 +09:00
8255c7a5ee
Phase 2 pgindent run for v12.
...
Switch to 2.1 version of pg_bsd_indent. This formats
multiline function declarations "correctly", that is with
additional lines of parameter declarations indented to match
where the first line's left parenthesis is.
Discussion: https://postgr.es/m/CAEepm=0P3FeTXRcU5B2W3jv3PgRVZ-kGUXLGfd42FFhUROO3ug@mail.gmail.com
2019-05-22 13:04:48 -04:00
97c39498e5
Update copyright for 2019
...
Backpatch-through: certain files through 9.4
2019-01-02 12:44:25 -05:00
edf59c40dd
Fix more wrong paths in header comments
...
It appears that there are more files, whose header comment paths are
wrong. So, fix those paths. No backpatching per proposal of Tom Lane.
Discussion: https://postgr.es/m/CAPpHfdsJyYbOj59MOQL%2B4XxdcomLSLfLqBtAvwR%2BpsCqj3ELdQ%40mail.gmail.com
2018-07-11 17:57:04 +03:00
bdf46af748
Post-feature-freeze pgindent run.
...
Discussion: https://postgr.es/m/15719.1523984266@sss.pgh.pa.us
2018-04-26 14:47:16 -04:00
0b11a674fb
Fix a boatload of typos in C comments.
...
Justin Pryzby
Discussion: https://postgr.es/m/20180331105640.GK28454@telsasoft.com
2018-04-01 15:01:28 -04:00
9d4649ca49
Update copyright for 2018
...
Backpatch-through: certain files through 9.3
2018-01-02 23:30:12 -05:00
ab9e0e718a
Add shared tuplestores.
...
SharedTuplestore allows multiple participants to write into it and
then read the tuples back from it in parallel. Each reader receives
partial results.
For now it always uses disk files, but other buffering policies and
other kinds of scans (ie each reader receives complete results) may be
useful in future.
The upcoming parallel hash join feature will use this facility.
Author: Thomas Munro
Reviewed-By: Peter Geoghegan, Andres Freund, Robert Haas
Discussion: https://postgr.es/m/CAEepm=2W=cOkiZxcg6qiFQP-dHUe09aqTrEMM7yJDrHMhDv_RA@mail.gmail.com
2017-12-18 14:23:19 -08:00
Bruce Momjian
Alvaro Herrera
Michael Paquier
Tom Lane
Alexander Korotkov
Andres Freund