notbugAs an Amazon Associate I earn from qualifying purchases.
Want a good read? Try FreeBSD Mastery: Jails (IT Mastery Book 15)
Ukraine
Some details on the 2023-01-16 website outage.
We just rebooted with several updates: * new HMTLify code * no port maintainer is now highly visible (e.g. https://freshports.org/security/sssd/) * fixed search logic error when using plain/ text details at https://github.com/FreshPorts/freshports/releases/tag/2.2.34
Port details
postgresql10-server PostgreSQL is the most advanced open-source database available anywhere
10.23_1 databases on this many watch lists=5 search for ports that depend on this port An older version of this port was marked as vulnerable. Find issues related to this port Report an issue related to this port View this port on Repology. pkg-fallout Version of this port present on the latest quarterly branch.
Maintainer: pgsql@FreeBSD.org search for ports maintained by this maintainer
Port Added: 2017-08-10 14:23:49
Last Update: 2022-11-15 15:40:59
Commit Hash: d512e8c
People watching this port, also watch:: nginx, coreutils, smartmontools, pkg, node
License: PostgreSQL
Description:
Homepage    cgit ¦ Codeberg ¦ GitHub ¦ GitLab ¦ SVNWeb
pkg-plist: as obtained via: make generate-plist
Expand this list (855 items)
Collapse this list.
  1. /usr/local/share/licenses/postgresql10-server-10.23_1/catalog.mk
  2. /usr/local/share/licenses/postgresql10-server-10.23_1/LICENSE
  3. /usr/local/share/licenses/postgresql10-server-10.23_1/PostgreSQL
  4. bin/initdb
  5. bin/pg_archivecleanup
  6. bin/pg_basebackup
  7. bin/pg_controldata
  8. bin/pg_ctl
  9. bin/pg_receivewal
  10. bin/pg_recvlogical
  11. bin/pg_resetwal
  12. bin/pg_rewind
  13. bin/pg_test_fsync
  14. bin/pg_test_timing
  15. bin/pg_upgrade
  16. bin/pg_waldump
  17. bin/postgres
  18. bin/postmaster
  19. etc/periodic/daily/502.pgsql
  20. include/postgresql/server/plpgsql.h
  21. lib/postgresql/ascii_and_mic.so
  22. lib/postgresql/cyrillic_and_mic.so
  23. lib/postgresql/dict_snowball.so
  24. lib/postgresql/euc2004_sjis2004.so
  25. lib/postgresql/euc_cn_and_mic.so
  26. lib/postgresql/euc_jp_and_sjis.so
  27. lib/postgresql/euc_kr_and_mic.so
  28. lib/postgresql/euc_tw_and_big5.so
  29. lib/postgresql/latin2_and_win1250.so
  30. lib/postgresql/latin_and_mic.so
  31. lib/postgresql/libpqwalreceiver.so
  32. lib/postgresql/pgoutput.so
  33. lib/postgresql/plpgsql.so
  34. lib/postgresql/utf8_and_ascii.so
  35. lib/postgresql/utf8_and_big5.so
  36. lib/postgresql/utf8_and_cyrillic.so
  37. lib/postgresql/utf8_and_euc2004.so
  38. lib/postgresql/utf8_and_euc_cn.so
  39. lib/postgresql/utf8_and_euc_jp.so
  40. lib/postgresql/utf8_and_euc_kr.so
  41. lib/postgresql/utf8_and_euc_tw.so
  42. lib/postgresql/utf8_and_gb18030.so
  43. lib/postgresql/utf8_and_gbk.so
  44. lib/postgresql/utf8_and_iso8859.so
  45. lib/postgresql/utf8_and_iso8859_1.so
  46. lib/postgresql/utf8_and_johab.so
  47. lib/postgresql/utf8_and_sjis.so
  48. lib/postgresql/utf8_and_sjis2004.so
  49. lib/postgresql/utf8_and_uhc.so
  50. lib/postgresql/utf8_and_win.so
  51. lib/libpgcommon.a
  52. share/doc/postgresql/README-server
  53. share/postgresql/conversion_create.sql
  54. share/postgresql/information_schema.sql
  55. share/postgresql/pg_hba.conf.sample
  56. share/postgresql/pg_ident.conf.sample
  57. share/postgresql/postgres.bki
  58. share/postgresql/postgres.description
  59. share/postgresql/postgresql.conf.sample
  60. share/postgresql/recovery.conf.sample
  61. share/postgresql/sql_features.txt
  62. share/postgresql/system_views.sql
  63. share/postgresql/extension/plpgsql--1.0.sql
  64. share/postgresql/extension/plpgsql--unpackaged--1.0.sql
  65. share/postgresql/extension/plpgsql.control
  66. share/postgresql/postgres.shdescription
  67. share/locale/cs/LC_MESSAGES/initdb-10.mo
  68. share/locale/cs/LC_MESSAGES/pg_archivecleanup-10.mo
  69. share/locale/cs/LC_MESSAGES/pg_basebackup-10.mo
  70. share/locale/cs/LC_MESSAGES/pg_controldata-10.mo
  71. share/locale/cs/LC_MESSAGES/pg_ctl-10.mo
  72. share/locale/cs/LC_MESSAGES/pg_resetwal-10.mo
  73. share/locale/cs/LC_MESSAGES/pg_rewind-10.mo
  74. share/locale/cs/LC_MESSAGES/pg_test_fsync-10.mo
  75. share/locale/cs/LC_MESSAGES/pg_test_timing-10.mo
  76. share/locale/cs/LC_MESSAGES/pg_upgrade-10.mo
  77. share/locale/cs/LC_MESSAGES/pg_waldump-10.mo
  78. share/locale/cs/LC_MESSAGES/plpgsql-10.mo
  79. share/locale/de/LC_MESSAGES/initdb-10.mo
  80. share/locale/de/LC_MESSAGES/pg_archivecleanup-10.mo
  81. share/locale/de/LC_MESSAGES/pg_basebackup-10.mo
  82. share/locale/de/LC_MESSAGES/pg_controldata-10.mo
  83. share/locale/de/LC_MESSAGES/pg_ctl-10.mo
  84. share/locale/de/LC_MESSAGES/pg_resetwal-10.mo
  85. share/locale/de/LC_MESSAGES/pg_rewind-10.mo
  86. share/locale/de/LC_MESSAGES/pg_test_fsync-10.mo
  87. share/locale/de/LC_MESSAGES/pg_test_timing-10.mo
  88. share/locale/de/LC_MESSAGES/pg_upgrade-10.mo
  89. share/locale/de/LC_MESSAGES/pg_waldump-10.mo
  90. share/locale/de/LC_MESSAGES/plpgsql-10.mo
  91. share/locale/de/LC_MESSAGES/postgres-10.mo
  92. share/locale/es/LC_MESSAGES/initdb-10.mo
  93. share/locale/es/LC_MESSAGES/pg_archivecleanup-10.mo
  94. share/locale/es/LC_MESSAGES/pg_basebackup-10.mo
  95. share/locale/es/LC_MESSAGES/pg_controldata-10.mo
  96. share/locale/es/LC_MESSAGES/pg_ctl-10.mo
  97. share/locale/es/LC_MESSAGES/pg_resetwal-10.mo
  98. share/locale/es/LC_MESSAGES/pg_rewind-10.mo
  99. share/locale/es/LC_MESSAGES/pg_test_fsync-10.mo
  100. share/locale/es/LC_MESSAGES/pg_test_timing-10.mo
  101. share/locale/es/LC_MESSAGES/pg_upgrade-10.mo
  102. share/locale/es/LC_MESSAGES/pg_waldump-10.mo
  103. share/locale/es/LC_MESSAGES/plpgsql-10.mo
  104. share/locale/es/LC_MESSAGES/postgres-10.mo
  105. share/locale/fr/LC_MESSAGES/initdb-10.mo
  106. share/locale/fr/LC_MESSAGES/pg_archivecleanup-10.mo
  107. share/locale/fr/LC_MESSAGES/pg_basebackup-10.mo
  108. share/locale/fr/LC_MESSAGES/pg_controldata-10.mo
  109. share/locale/fr/LC_MESSAGES/pg_ctl-10.mo
  110. share/locale/fr/LC_MESSAGES/pg_resetwal-10.mo
  111. share/locale/fr/LC_MESSAGES/pg_rewind-10.mo
  112. share/locale/fr/LC_MESSAGES/pg_test_fsync-10.mo
  113. share/locale/fr/LC_MESSAGES/pg_test_timing-10.mo
  114. share/locale/fr/LC_MESSAGES/pg_upgrade-10.mo
  115. share/locale/fr/LC_MESSAGES/pg_waldump-10.mo
  116. share/locale/fr/LC_MESSAGES/plpgsql-10.mo
  117. share/locale/fr/LC_MESSAGES/postgres-10.mo
  118. share/locale/he/LC_MESSAGES/initdb-10.mo
  119. share/locale/he/LC_MESSAGES/pg_basebackup-10.mo
  120. share/locale/he/LC_MESSAGES/pg_ctl-10.mo
  121. share/locale/it/LC_MESSAGES/initdb-10.mo
  122. share/locale/it/LC_MESSAGES/pg_basebackup-10.mo
  123. share/locale/it/LC_MESSAGES/pg_controldata-10.mo
  124. share/locale/it/LC_MESSAGES/pg_ctl-10.mo
  125. share/locale/it/LC_MESSAGES/pg_rewind-10.mo
  126. share/locale/it/LC_MESSAGES/plpgsql-10.mo
  127. share/locale/it/LC_MESSAGES/postgres-10.mo
  128. share/locale/ja/LC_MESSAGES/initdb-10.mo
  129. share/locale/ja/LC_MESSAGES/pg_archivecleanup-10.mo
  130. share/locale/ja/LC_MESSAGES/pg_basebackup-10.mo
  131. share/locale/ja/LC_MESSAGES/pg_controldata-10.mo
  132. share/locale/ja/LC_MESSAGES/pg_ctl-10.mo
  133. share/locale/ja/LC_MESSAGES/pg_resetwal-10.mo
  134. share/locale/ja/LC_MESSAGES/pg_rewind-10.mo
  135. share/locale/ja/LC_MESSAGES/pg_test_fsync-10.mo
  136. share/locale/ja/LC_MESSAGES/pg_test_timing-10.mo
  137. share/locale/ja/LC_MESSAGES/pg_upgrade-10.mo
  138. share/locale/ja/LC_MESSAGES/pg_waldump-10.mo
  139. share/locale/ja/LC_MESSAGES/plpgsql-10.mo
  140. share/locale/ja/LC_MESSAGES/postgres-10.mo
  141. share/locale/ko/LC_MESSAGES/initdb-10.mo
  142. share/locale/ko/LC_MESSAGES/pg_archivecleanup-10.mo
  143. share/locale/ko/LC_MESSAGES/pg_basebackup-10.mo
  144. share/locale/ko/LC_MESSAGES/pg_controldata-10.mo
  145. share/locale/ko/LC_MESSAGES/pg_ctl-10.mo
  146. share/locale/ko/LC_MESSAGES/pg_resetwal-10.mo
  147. share/locale/ko/LC_MESSAGES/pg_rewind-10.mo
  148. share/locale/ko/LC_MESSAGES/pg_test_fsync-10.mo
  149. share/locale/ko/LC_MESSAGES/pg_test_timing-10.mo
  150. share/locale/ko/LC_MESSAGES/pg_upgrade-10.mo
  151. share/locale/ko/LC_MESSAGES/pg_waldump-10.mo
  152. share/locale/ko/LC_MESSAGES/plpgsql-10.mo
  153. share/locale/ko/LC_MESSAGES/postgres-10.mo
  154. share/locale/pl/LC_MESSAGES/initdb-10.mo
  155. share/locale/pl/LC_MESSAGES/pg_archivecleanup-10.mo
  156. share/locale/pl/LC_MESSAGES/pg_basebackup-10.mo
  157. share/locale/pl/LC_MESSAGES/pg_controldata-10.mo
  158. share/locale/pl/LC_MESSAGES/pg_ctl-10.mo
  159. share/locale/pl/LC_MESSAGES/pg_resetwal-10.mo
  160. share/locale/pl/LC_MESSAGES/pg_rewind-10.mo
  161. share/locale/pl/LC_MESSAGES/pg_test_fsync-10.mo
  162. share/locale/pl/LC_MESSAGES/pg_test_timing-10.mo
  163. share/locale/pl/LC_MESSAGES/plpgsql-10.mo
  164. share/locale/pl/LC_MESSAGES/postgres-10.mo
  165. share/locale/pt_BR/LC_MESSAGES/initdb-10.mo
  166. share/locale/pt_BR/LC_MESSAGES/pg_controldata-10.mo
  167. share/locale/pt_BR/LC_MESSAGES/pg_ctl-10.mo
  168. share/locale/pt_BR/LC_MESSAGES/pg_resetwal-10.mo
  169. share/locale/pt_BR/LC_MESSAGES/pg_rewind-10.mo
  170. share/locale/pt_BR/LC_MESSAGES/plpgsql-10.mo
  171. share/locale/ro/LC_MESSAGES/plpgsql-10.mo
  172. share/locale/ru/LC_MESSAGES/initdb-10.mo
  173. share/locale/ru/LC_MESSAGES/pg_archivecleanup-10.mo
  174. share/locale/ru/LC_MESSAGES/pg_basebackup-10.mo
  175. share/locale/ru/LC_MESSAGES/pg_controldata-10.mo
  176. share/locale/ru/LC_MESSAGES/pg_ctl-10.mo
  177. share/locale/ru/LC_MESSAGES/pg_resetwal-10.mo
  178. share/locale/ru/LC_MESSAGES/pg_rewind-10.mo
  179. share/locale/ru/LC_MESSAGES/pg_test_fsync-10.mo
  180. share/locale/ru/LC_MESSAGES/pg_test_timing-10.mo
  181. share/locale/ru/LC_MESSAGES/pg_upgrade-10.mo
  182. share/locale/ru/LC_MESSAGES/pg_waldump-10.mo
  183. share/locale/ru/LC_MESSAGES/plpgsql-10.mo
  184. share/locale/ru/LC_MESSAGES/postgres-10.mo
  185. share/locale/sv/LC_MESSAGES/initdb-10.mo
  186. share/locale/sv/LC_MESSAGES/pg_archivecleanup-10.mo
  187. share/locale/sv/LC_MESSAGES/pg_basebackup-10.mo
  188. share/locale/sv/LC_MESSAGES/pg_controldata-10.mo
  189. share/locale/sv/LC_MESSAGES/pg_ctl-10.mo
  190. share/locale/sv/LC_MESSAGES/pg_resetwal-10.mo
  191. share/locale/sv/LC_MESSAGES/pg_rewind-10.mo
  192. share/locale/sv/LC_MESSAGES/pg_test_fsync-10.mo
  193. share/locale/sv/LC_MESSAGES/pg_test_timing-10.mo
  194. share/locale/sv/LC_MESSAGES/pg_upgrade-10.mo
  195. share/locale/sv/LC_MESSAGES/pg_waldump-10.mo
  196. share/locale/sv/LC_MESSAGES/plpgsql-10.mo
  197. share/locale/sv/LC_MESSAGES/postgres-10.mo
  198. share/locale/tr/LC_MESSAGES/initdb-10.mo
  199. share/locale/tr/LC_MESSAGES/pg_archivecleanup-10.mo
  200. share/locale/tr/LC_MESSAGES/pg_basebackup-10.mo
  201. share/locale/tr/LC_MESSAGES/pg_controldata-10.mo
  202. share/locale/tr/LC_MESSAGES/pg_ctl-10.mo
  203. share/locale/tr/LC_MESSAGES/pg_resetwal-10.mo
  204. share/locale/tr/LC_MESSAGES/pg_rewind-10.mo
  205. share/locale/tr/LC_MESSAGES/pg_test_fsync-10.mo
  206. share/locale/tr/LC_MESSAGES/pg_test_timing-10.mo
  207. share/locale/tr/LC_MESSAGES/pg_upgrade-10.mo
  208. share/locale/tr/LC_MESSAGES/pg_waldump-10.mo
  209. share/locale/tr/LC_MESSAGES/plpgsql-10.mo
  210. share/locale/tr/LC_MESSAGES/postgres-10.mo
  211. share/locale/zh_CN/LC_MESSAGES/initdb-10.mo
  212. share/locale/zh_CN/LC_MESSAGES/pg_controldata-10.mo
  213. share/locale/zh_CN/LC_MESSAGES/pg_ctl-10.mo
  214. share/locale/zh_CN/LC_MESSAGES/pg_resetwal-10.mo
  215. share/locale/zh_CN/LC_MESSAGES/pg_rewind-10.mo
  216. share/locale/zh_CN/LC_MESSAGES/plpgsql-10.mo
  217. share/locale/zh_CN/LC_MESSAGES/postgres-10.mo
  218. share/locale/zh_TW/LC_MESSAGES/plpgsql-10.mo
  219. share/postgresql/snowball_create.sql
  220. @comment share/postgresql/timezone/Africa/Abidjan
  221. @comment share/postgresql/timezone/Africa/Accra
  222. @comment share/postgresql/timezone/Africa/Addis_Ababa
  223. @comment share/postgresql/timezone/Africa/Algiers
  224. @comment share/postgresql/timezone/Africa/Asmara
  225. @comment share/postgresql/timezone/Africa/Asmera
  226. @comment share/postgresql/timezone/Africa/Bamako
  227. @comment share/postgresql/timezone/Africa/Bangui
  228. @comment share/postgresql/timezone/Africa/Banjul
  229. @comment share/postgresql/timezone/Africa/Bissau
  230. @comment share/postgresql/timezone/Africa/Blantyre
  231. @comment share/postgresql/timezone/Africa/Brazzaville
  232. @comment share/postgresql/timezone/Africa/Bujumbura
  233. @comment share/postgresql/timezone/Africa/Cairo
  234. @comment share/postgresql/timezone/Africa/Casablanca
  235. @comment share/postgresql/timezone/Africa/Ceuta
  236. @comment share/postgresql/timezone/Africa/Conakry
  237. @comment share/postgresql/timezone/Africa/Dakar
  238. @comment share/postgresql/timezone/Africa/Dar_es_Salaam
  239. @comment share/postgresql/timezone/Africa/Djibouti
  240. @comment share/postgresql/timezone/Africa/Douala
  241. @comment share/postgresql/timezone/Africa/El_Aaiun
  242. @comment share/postgresql/timezone/Africa/Freetown
  243. @comment share/postgresql/timezone/Africa/Gaborone
  244. @comment share/postgresql/timezone/Africa/Harare
  245. @comment share/postgresql/timezone/Africa/Johannesburg
  246. @comment share/postgresql/timezone/Africa/Juba
  247. @comment share/postgresql/timezone/Africa/Kampala
  248. @comment share/postgresql/timezone/Africa/Khartoum
  249. @comment share/postgresql/timezone/Africa/Kigali
  250. @comment share/postgresql/timezone/Africa/Kinshasa
  251. @comment share/postgresql/timezone/Africa/Lagos
  252. @comment share/postgresql/timezone/Africa/Libreville
  253. @comment share/postgresql/timezone/Africa/Lome
  254. @comment share/postgresql/timezone/Africa/Luanda
  255. @comment share/postgresql/timezone/Africa/Lubumbashi
  256. @comment share/postgresql/timezone/Africa/Lusaka
  257. @comment share/postgresql/timezone/Africa/Malabo
  258. @comment share/postgresql/timezone/Africa/Maputo
  259. @comment share/postgresql/timezone/Africa/Maseru
  260. @comment share/postgresql/timezone/Africa/Mbabane
  261. @comment share/postgresql/timezone/Africa/Mogadishu
  262. @comment share/postgresql/timezone/Africa/Monrovia
  263. @comment share/postgresql/timezone/Africa/Nairobi
  264. @comment share/postgresql/timezone/Africa/Ndjamena
  265. @comment share/postgresql/timezone/Africa/Niamey
  266. @comment share/postgresql/timezone/Africa/Nouakchott
  267. @comment share/postgresql/timezone/Africa/Ouagadougou
  268. @comment share/postgresql/timezone/Africa/Porto-Novo
  269. @comment share/postgresql/timezone/Africa/Sao_Tome
  270. @comment share/postgresql/timezone/Africa/Timbuktu
  271. @comment share/postgresql/timezone/Africa/Tripoli
  272. @comment share/postgresql/timezone/Africa/Tunis
  273. @comment share/postgresql/timezone/Africa/Windhoek
  274. @comment share/postgresql/timezone/America/Adak
  275. @comment share/postgresql/timezone/America/Anchorage
  276. @comment share/postgresql/timezone/America/Anguilla
  277. @comment share/postgresql/timezone/America/Antigua
  278. @comment share/postgresql/timezone/America/Araguaina
  279. @comment share/postgresql/timezone/America/Argentina/Buenos_Aires
  280. @comment share/postgresql/timezone/America/Argentina/Catamarca
  281. @comment share/postgresql/timezone/America/Argentina/ComodRivadavia
  282. @comment share/postgresql/timezone/America/Argentina/Cordoba
  283. @comment share/postgresql/timezone/America/Argentina/Jujuy
  284. @comment share/postgresql/timezone/America/Argentina/La_Rioja
  285. @comment share/postgresql/timezone/America/Argentina/Mendoza
  286. @comment share/postgresql/timezone/America/Argentina/Rio_Gallegos
  287. @comment share/postgresql/timezone/America/Argentina/Salta
  288. @comment share/postgresql/timezone/America/Argentina/San_Juan
  289. @comment share/postgresql/timezone/America/Argentina/San_Luis
  290. @comment share/postgresql/timezone/America/Argentina/Tucuman
  291. @comment share/postgresql/timezone/America/Argentina/Ushuaia
  292. @comment share/postgresql/timezone/America/Aruba
  293. @comment share/postgresql/timezone/America/Asuncion
  294. @comment share/postgresql/timezone/America/Atikokan
  295. @comment share/postgresql/timezone/America/Atka
  296. @comment share/postgresql/timezone/America/Bahia
  297. @comment share/postgresql/timezone/America/Bahia_Banderas
  298. @comment share/postgresql/timezone/America/Barbados
  299. @comment share/postgresql/timezone/America/Belem
  300. @comment share/postgresql/timezone/America/Belize
  301. @comment share/postgresql/timezone/America/Blanc-Sablon
  302. @comment share/postgresql/timezone/America/Boa_Vista
  303. @comment share/postgresql/timezone/America/Bogota
  304. @comment share/postgresql/timezone/America/Boise
  305. @comment share/postgresql/timezone/America/Buenos_Aires
  306. @comment share/postgresql/timezone/America/Cambridge_Bay
  307. @comment share/postgresql/timezone/America/Campo_Grande
  308. @comment share/postgresql/timezone/America/Cancun
  309. @comment share/postgresql/timezone/America/Caracas
  310. @comment share/postgresql/timezone/America/Catamarca
  311. @comment share/postgresql/timezone/America/Cayenne
  312. @comment share/postgresql/timezone/America/Cayman
  313. @comment share/postgresql/timezone/America/Chicago
  314. @comment share/postgresql/timezone/America/Chihuahua
  315. @comment share/postgresql/timezone/America/Coral_Harbour
  316. @comment share/postgresql/timezone/America/Cordoba
  317. @comment share/postgresql/timezone/America/Costa_Rica
  318. @comment share/postgresql/timezone/America/Creston
  319. @comment share/postgresql/timezone/America/Cuiaba
  320. @comment share/postgresql/timezone/America/Curacao
  321. @comment share/postgresql/timezone/America/Danmarkshavn
  322. @comment share/postgresql/timezone/America/Dawson
  323. @comment share/postgresql/timezone/America/Dawson_Creek
  324. @comment share/postgresql/timezone/America/Denver
  325. @comment share/postgresql/timezone/America/Detroit
  326. @comment share/postgresql/timezone/America/Dominica
  327. @comment share/postgresql/timezone/America/Edmonton
  328. @comment share/postgresql/timezone/America/Eirunepe
  329. @comment share/postgresql/timezone/America/El_Salvador
  330. @comment share/postgresql/timezone/America/Ensenada
  331. @comment share/postgresql/timezone/America/Fort_Nelson
  332. @comment share/postgresql/timezone/America/Fort_Wayne
  333. @comment share/postgresql/timezone/America/Fortaleza
  334. @comment share/postgresql/timezone/America/Glace_Bay
  335. @comment share/postgresql/timezone/America/Godthab
  336. @comment share/postgresql/timezone/America/Goose_Bay
  337. @comment share/postgresql/timezone/America/Grand_Turk
  338. @comment share/postgresql/timezone/America/Grenada
  339. @comment share/postgresql/timezone/America/Guadeloupe
  340. @comment share/postgresql/timezone/America/Guatemala
  341. @comment share/postgresql/timezone/America/Guayaquil
  342. @comment share/postgresql/timezone/America/Guyana
  343. @comment share/postgresql/timezone/America/Halifax
  344. @comment share/postgresql/timezone/America/Havana
  345. @comment share/postgresql/timezone/America/Hermosillo
  346. @comment share/postgresql/timezone/America/Indiana/Indianapolis
  347. @comment share/postgresql/timezone/America/Indiana/Knox
  348. @comment share/postgresql/timezone/America/Indiana/Marengo
  349. @comment share/postgresql/timezone/America/Indiana/Petersburg
  350. @comment share/postgresql/timezone/America/Indiana/Tell_City
  351. @comment share/postgresql/timezone/America/Indiana/Vevay
  352. @comment share/postgresql/timezone/America/Indiana/Vincennes
  353. @comment share/postgresql/timezone/America/Indiana/Winamac
  354. @comment share/postgresql/timezone/America/Indianapolis
  355. @comment share/postgresql/timezone/America/Inuvik
  356. @comment share/postgresql/timezone/America/Iqaluit
  357. @comment share/postgresql/timezone/America/Jamaica
  358. @comment share/postgresql/timezone/America/Jujuy
  359. @comment share/postgresql/timezone/America/Juneau
  360. @comment share/postgresql/timezone/America/Kentucky/Louisville
  361. @comment share/postgresql/timezone/America/Kentucky/Monticello
  362. @comment share/postgresql/timezone/America/Knox_IN
  363. @comment share/postgresql/timezone/America/Kralendijk
  364. @comment share/postgresql/timezone/America/La_Paz
  365. @comment share/postgresql/timezone/America/Lima
  366. @comment share/postgresql/timezone/America/Los_Angeles
  367. @comment share/postgresql/timezone/America/Louisville
  368. @comment share/postgresql/timezone/America/Lower_Princes
  369. @comment share/postgresql/timezone/America/Maceio
  370. @comment share/postgresql/timezone/America/Managua
  371. @comment share/postgresql/timezone/America/Manaus
  372. @comment share/postgresql/timezone/America/Marigot
  373. @comment share/postgresql/timezone/America/Martinique
  374. @comment share/postgresql/timezone/America/Matamoros
  375. @comment share/postgresql/timezone/America/Mazatlan
  376. @comment share/postgresql/timezone/America/Mendoza
  377. @comment share/postgresql/timezone/America/Menominee
  378. @comment share/postgresql/timezone/America/Merida
  379. @comment share/postgresql/timezone/America/Metlakatla
  380. @comment share/postgresql/timezone/America/Mexico_City
  381. @comment share/postgresql/timezone/America/Miquelon
  382. @comment share/postgresql/timezone/America/Moncton
  383. @comment share/postgresql/timezone/America/Monterrey
  384. @comment share/postgresql/timezone/America/Montevideo
  385. @comment share/postgresql/timezone/America/Montreal
  386. @comment share/postgresql/timezone/America/Montserrat
  387. @comment share/postgresql/timezone/America/Nassau
  388. @comment share/postgresql/timezone/America/New_York
  389. @comment share/postgresql/timezone/America/Nipigon
  390. @comment share/postgresql/timezone/America/Nome
  391. @comment share/postgresql/timezone/America/Noronha
  392. @comment share/postgresql/timezone/America/North_Dakota/Beulah
  393. @comment share/postgresql/timezone/America/North_Dakota/Center
  394. @comment share/postgresql/timezone/America/North_Dakota/New_Salem
  395. @comment share/postgresql/timezone/America/Nuuk
  396. @comment share/postgresql/timezone/America/Ojinaga
  397. @comment share/postgresql/timezone/America/Panama
  398. @comment share/postgresql/timezone/America/Pangnirtung
  399. @comment share/postgresql/timezone/America/Paramaribo
  400. @comment share/postgresql/timezone/America/Phoenix
  401. @comment share/postgresql/timezone/America/Port-au-Prince
  402. @comment share/postgresql/timezone/America/Port_of_Spain
  403. @comment share/postgresql/timezone/America/Porto_Acre
  404. @comment share/postgresql/timezone/America/Porto_Velho
  405. @comment share/postgresql/timezone/America/Puerto_Rico
  406. @comment share/postgresql/timezone/America/Punta_Arenas
  407. @comment share/postgresql/timezone/America/Rainy_River
  408. @comment share/postgresql/timezone/America/Rankin_Inlet
  409. @comment share/postgresql/timezone/America/Recife
  410. @comment share/postgresql/timezone/America/Regina
  411. @comment share/postgresql/timezone/America/Resolute
  412. @comment share/postgresql/timezone/America/Rio_Branco
  413. @comment share/postgresql/timezone/America/Rosario
  414. @comment share/postgresql/timezone/America/Santa_Isabel
  415. @comment share/postgresql/timezone/America/Santarem
  416. @comment share/postgresql/timezone/America/Santiago
  417. @comment share/postgresql/timezone/America/Santo_Domingo
  418. @comment share/postgresql/timezone/America/Sao_Paulo
  419. @comment share/postgresql/timezone/America/Scoresbysund
  420. @comment share/postgresql/timezone/America/Shiprock
  421. @comment share/postgresql/timezone/America/Sitka
  422. @comment share/postgresql/timezone/America/St_Barthelemy
  423. @comment share/postgresql/timezone/America/St_Johns
  424. @comment share/postgresql/timezone/America/St_Kitts
  425. @comment share/postgresql/timezone/America/St_Lucia
  426. @comment share/postgresql/timezone/America/St_Thomas
  427. @comment share/postgresql/timezone/America/St_Vincent
  428. @comment share/postgresql/timezone/America/Swift_Current
  429. @comment share/postgresql/timezone/America/Tegucigalpa
  430. @comment share/postgresql/timezone/America/Thule
  431. @comment share/postgresql/timezone/America/Thunder_Bay
  432. @comment share/postgresql/timezone/America/Tijuana
  433. @comment share/postgresql/timezone/America/Toronto
  434. @comment share/postgresql/timezone/America/Tortola
  435. @comment share/postgresql/timezone/America/Vancouver
  436. @comment share/postgresql/timezone/America/Virgin
  437. @comment share/postgresql/timezone/America/Whitehorse
  438. @comment share/postgresql/timezone/America/Winnipeg
  439. @comment share/postgresql/timezone/America/Yakutat
  440. @comment share/postgresql/timezone/America/Yellowknife
  441. @comment share/postgresql/timezone/Antarctica/Casey
  442. @comment share/postgresql/timezone/Antarctica/Davis
  443. @comment share/postgresql/timezone/Antarctica/DumontDUrville
  444. @comment share/postgresql/timezone/Antarctica/Macquarie
  445. @comment share/postgresql/timezone/Antarctica/Mawson
  446. @comment share/postgresql/timezone/Antarctica/McMurdo
  447. @comment share/postgresql/timezone/Antarctica/Palmer
  448. @comment share/postgresql/timezone/Antarctica/Rothera
  449. @comment share/postgresql/timezone/Antarctica/South_Pole
  450. @comment share/postgresql/timezone/Antarctica/Syowa
  451. @comment share/postgresql/timezone/Antarctica/Troll
  452. @comment share/postgresql/timezone/Antarctica/Vostok
  453. @comment share/postgresql/timezone/Arctic/Longyearbyen
  454. @comment share/postgresql/timezone/Asia/Aden
  455. @comment share/postgresql/timezone/Asia/Almaty
  456. @comment share/postgresql/timezone/Asia/Amman
  457. @comment share/postgresql/timezone/Asia/Anadyr
  458. @comment share/postgresql/timezone/Asia/Aqtau
  459. @comment share/postgresql/timezone/Asia/Aqtobe
  460. @comment share/postgresql/timezone/Asia/Ashgabat
  461. @comment share/postgresql/timezone/Asia/Ashkhabad
  462. @comment share/postgresql/timezone/Asia/Atyrau
  463. @comment share/postgresql/timezone/Asia/Baghdad
  464. @comment share/postgresql/timezone/Asia/Bahrain
  465. @comment share/postgresql/timezone/Asia/Baku
  466. @comment share/postgresql/timezone/Asia/Bangkok
  467. @comment share/postgresql/timezone/Asia/Barnaul
  468. @comment share/postgresql/timezone/Asia/Beirut
  469. @comment share/postgresql/timezone/Asia/Bishkek
  470. @comment share/postgresql/timezone/Asia/Brunei
  471. @comment share/postgresql/timezone/Asia/Calcutta
  472. @comment share/postgresql/timezone/Asia/Chita
  473. @comment share/postgresql/timezone/Asia/Choibalsan
  474. @comment share/postgresql/timezone/Asia/Chongqing
  475. @comment share/postgresql/timezone/Asia/Chungking
  476. @comment share/postgresql/timezone/Asia/Colombo
  477. @comment share/postgresql/timezone/Asia/Dacca
  478. @comment share/postgresql/timezone/Asia/Damascus
  479. @comment share/postgresql/timezone/Asia/Dhaka
  480. @comment share/postgresql/timezone/Asia/Dili
  481. @comment share/postgresql/timezone/Asia/Dubai
  482. @comment share/postgresql/timezone/Asia/Dushanbe
  483. @comment share/postgresql/timezone/Asia/Famagusta
  484. @comment share/postgresql/timezone/Asia/Gaza
  485. @comment share/postgresql/timezone/Asia/Harbin
  486. @comment share/postgresql/timezone/Asia/Hebron
  487. @comment share/postgresql/timezone/Asia/Ho_Chi_Minh
  488. @comment share/postgresql/timezone/Asia/Hong_Kong
  489. @comment share/postgresql/timezone/Asia/Hovd
  490. @comment share/postgresql/timezone/Asia/Irkutsk
  491. @comment share/postgresql/timezone/Asia/Istanbul
  492. @comment share/postgresql/timezone/Asia/Jakarta
  493. @comment share/postgresql/timezone/Asia/Jayapura
  494. @comment share/postgresql/timezone/Asia/Jerusalem
  495. @comment share/postgresql/timezone/Asia/Kabul
  496. @comment share/postgresql/timezone/Asia/Kamchatka
  497. @comment share/postgresql/timezone/Asia/Karachi
  498. @comment share/postgresql/timezone/Asia/Kashgar
  499. @comment share/postgresql/timezone/Asia/Kathmandu
  500. @comment share/postgresql/timezone/Asia/Katmandu
  501. @comment share/postgresql/timezone/Asia/Khandyga
  502. @comment share/postgresql/timezone/Asia/Kolkata
  503. @comment share/postgresql/timezone/Asia/Krasnoyarsk
  504. @comment share/postgresql/timezone/Asia/Kuala_Lumpur
  505. @comment share/postgresql/timezone/Asia/Kuching
  506. @comment share/postgresql/timezone/Asia/Kuwait
  507. @comment share/postgresql/timezone/Asia/Macao
  508. @comment share/postgresql/timezone/Asia/Macau
  509. @comment share/postgresql/timezone/Asia/Magadan
  510. @comment share/postgresql/timezone/Asia/Makassar
  511. @comment share/postgresql/timezone/Asia/Manila
  512. @comment share/postgresql/timezone/Asia/Muscat
  513. @comment share/postgresql/timezone/Asia/Nicosia
  514. @comment share/postgresql/timezone/Asia/Novokuznetsk
  515. @comment share/postgresql/timezone/Asia/Novosibirsk
  516. @comment share/postgresql/timezone/Asia/Omsk
  517. @comment share/postgresql/timezone/Asia/Oral
  518. @comment share/postgresql/timezone/Asia/Phnom_Penh
  519. @comment share/postgresql/timezone/Asia/Pontianak
  520. @comment share/postgresql/timezone/Asia/Pyongyang
  521. @comment share/postgresql/timezone/Asia/Qatar
  522. @comment share/postgresql/timezone/Asia/Qostanay
  523. @comment share/postgresql/timezone/Asia/Qyzylorda
  524. @comment share/postgresql/timezone/Asia/Rangoon
  525. @comment share/postgresql/timezone/Asia/Riyadh
  526. @comment share/postgresql/timezone/Asia/Saigon
  527. @comment share/postgresql/timezone/Asia/Sakhalin
  528. @comment share/postgresql/timezone/Asia/Samarkand
  529. @comment share/postgresql/timezone/Asia/Seoul
  530. @comment share/postgresql/timezone/Asia/Shanghai
  531. @comment share/postgresql/timezone/Asia/Singapore
  532. @comment share/postgresql/timezone/Asia/Srednekolymsk
  533. @comment share/postgresql/timezone/Asia/Taipei
  534. @comment share/postgresql/timezone/Asia/Tashkent
  535. @comment share/postgresql/timezone/Asia/Tbilisi
  536. @comment share/postgresql/timezone/Asia/Tehran
  537. @comment share/postgresql/timezone/Asia/Tel_Aviv
  538. @comment share/postgresql/timezone/Asia/Thimbu
  539. @comment share/postgresql/timezone/Asia/Thimphu
  540. @comment share/postgresql/timezone/Asia/Tokyo
  541. @comment share/postgresql/timezone/Asia/Tomsk
  542. @comment share/postgresql/timezone/Asia/Ujung_Pandang
  543. @comment share/postgresql/timezone/Asia/Ulaanbaatar
  544. @comment share/postgresql/timezone/Asia/Ulan_Bator
  545. @comment share/postgresql/timezone/Asia/Urumqi
  546. @comment share/postgresql/timezone/Asia/Ust-Nera
  547. @comment share/postgresql/timezone/Asia/Vientiane
  548. @comment share/postgresql/timezone/Asia/Vladivostok
  549. @comment share/postgresql/timezone/Asia/Yakutsk
  550. @comment share/postgresql/timezone/Asia/Yangon
  551. @comment share/postgresql/timezone/Asia/Yekaterinburg
  552. @comment share/postgresql/timezone/Asia/Yerevan
  553. @comment share/postgresql/timezone/Atlantic/Azores
  554. @comment share/postgresql/timezone/Atlantic/Bermuda
  555. @comment share/postgresql/timezone/Atlantic/Canary
  556. @comment share/postgresql/timezone/Atlantic/Cape_Verde
  557. @comment share/postgresql/timezone/Atlantic/Faeroe
  558. @comment share/postgresql/timezone/Atlantic/Faroe
  559. @comment share/postgresql/timezone/Atlantic/Jan_Mayen
  560. @comment share/postgresql/timezone/Atlantic/Madeira
  561. @comment share/postgresql/timezone/Atlantic/Reykjavik
  562. @comment share/postgresql/timezone/Atlantic/South_Georgia
  563. @comment share/postgresql/timezone/Atlantic/St_Helena
  564. @comment share/postgresql/timezone/Atlantic/Stanley
  565. @comment share/postgresql/timezone/Australia/ACT
  566. @comment share/postgresql/timezone/Australia/Adelaide
  567. @comment share/postgresql/timezone/Australia/Brisbane
  568. @comment share/postgresql/timezone/Australia/Broken_Hill
  569. @comment share/postgresql/timezone/Australia/Canberra
  570. @comment share/postgresql/timezone/Australia/Currie
  571. @comment share/postgresql/timezone/Australia/Darwin
  572. @comment share/postgresql/timezone/Australia/Eucla
  573. @comment share/postgresql/timezone/Australia/Hobart
  574. @comment share/postgresql/timezone/Australia/LHI
  575. @comment share/postgresql/timezone/Australia/Lindeman
  576. @comment share/postgresql/timezone/Australia/Lord_Howe
  577. @comment share/postgresql/timezone/Australia/Melbourne
  578. @comment share/postgresql/timezone/Australia/NSW
  579. @comment share/postgresql/timezone/Australia/North
  580. @comment share/postgresql/timezone/Australia/Perth
  581. @comment share/postgresql/timezone/Australia/Queensland
  582. @comment share/postgresql/timezone/Australia/South
  583. @comment share/postgresql/timezone/Australia/Sydney
  584. @comment share/postgresql/timezone/Australia/Tasmania
  585. @comment share/postgresql/timezone/Australia/Victoria
  586. @comment share/postgresql/timezone/Australia/West
  587. @comment share/postgresql/timezone/Australia/Yancowinna
  588. @comment share/postgresql/timezone/Brazil/Acre
  589. @comment share/postgresql/timezone/Brazil/DeNoronha
  590. @comment share/postgresql/timezone/Brazil/East
  591. @comment share/postgresql/timezone/Brazil/West
  592. @comment share/postgresql/timezone/CET
  593. @comment share/postgresql/timezone/CST6CDT
  594. @comment share/postgresql/timezone/Canada/Atlantic
  595. @comment share/postgresql/timezone/Canada/Central
  596. @comment share/postgresql/timezone/Canada/Eastern
  597. @comment share/postgresql/timezone/Canada/Mountain
  598. @comment share/postgresql/timezone/Canada/Newfoundland
  599. @comment share/postgresql/timezone/Canada/Pacific
  600. @comment share/postgresql/timezone/Canada/Saskatchewan
  601. @comment share/postgresql/timezone/Canada/Yukon
  602. @comment share/postgresql/timezone/Chile/Continental
  603. @comment share/postgresql/timezone/Chile/EasterIsland
  604. @comment share/postgresql/timezone/Cuba
  605. @comment share/postgresql/timezone/EET
  606. @comment share/postgresql/timezone/EST
  607. @comment share/postgresql/timezone/EST5EDT
  608. @comment share/postgresql/timezone/Egypt
  609. @comment share/postgresql/timezone/Eire
  610. @comment share/postgresql/timezone/Etc/GMT
  611. @comment share/postgresql/timezone/Etc/GMT+0
  612. @comment share/postgresql/timezone/Etc/GMT+1
  613. @comment share/postgresql/timezone/Etc/GMT+10
  614. @comment share/postgresql/timezone/Etc/GMT+11
  615. @comment share/postgresql/timezone/Etc/GMT+12
  616. @comment share/postgresql/timezone/Etc/GMT+2
  617. @comment share/postgresql/timezone/Etc/GMT+3
  618. @comment share/postgresql/timezone/Etc/GMT+4
  619. @comment share/postgresql/timezone/Etc/GMT+5
  620. @comment share/postgresql/timezone/Etc/GMT+6
  621. @comment share/postgresql/timezone/Etc/GMT+7
  622. @comment share/postgresql/timezone/Etc/GMT+8
  623. @comment share/postgresql/timezone/Etc/GMT+9
  624. @comment share/postgresql/timezone/Etc/GMT-0
  625. @comment share/postgresql/timezone/Etc/GMT-1
  626. @comment share/postgresql/timezone/Etc/GMT-10
  627. @comment share/postgresql/timezone/Etc/GMT-11
  628. @comment share/postgresql/timezone/Etc/GMT-12
  629. @comment share/postgresql/timezone/Etc/GMT-13
  630. @comment share/postgresql/timezone/Etc/GMT-14
  631. @comment share/postgresql/timezone/Etc/GMT-2
  632. @comment share/postgresql/timezone/Etc/GMT-3
  633. @comment share/postgresql/timezone/Etc/GMT-4
  634. @comment share/postgresql/timezone/Etc/GMT-5
  635. @comment share/postgresql/timezone/Etc/GMT-6
  636. @comment share/postgresql/timezone/Etc/GMT-7
  637. @comment share/postgresql/timezone/Etc/GMT-8
  638. @comment share/postgresql/timezone/Etc/GMT-9
  639. @comment share/postgresql/timezone/Etc/GMT0
  640. @comment share/postgresql/timezone/Etc/Greenwich
  641. @comment share/postgresql/timezone/Etc/UCT
  642. @comment share/postgresql/timezone/Etc/UTC
  643. @comment share/postgresql/timezone/Etc/Universal
  644. @comment share/postgresql/timezone/Etc/Zulu
  645. @comment share/postgresql/timezone/Europe/Amsterdam
  646. @comment share/postgresql/timezone/Europe/Andorra
  647. @comment share/postgresql/timezone/Europe/Astrakhan
  648. @comment share/postgresql/timezone/Europe/Athens
  649. @comment share/postgresql/timezone/Europe/Belfast
  650. @comment share/postgresql/timezone/Europe/Belgrade
  651. @comment share/postgresql/timezone/Europe/Berlin
  652. @comment share/postgresql/timezone/Europe/Bratislava
  653. @comment share/postgresql/timezone/Europe/Brussels
  654. @comment share/postgresql/timezone/Europe/Bucharest
  655. @comment share/postgresql/timezone/Europe/Budapest
  656. @comment share/postgresql/timezone/Europe/Busingen
  657. @comment share/postgresql/timezone/Europe/Chisinau
  658. @comment share/postgresql/timezone/Europe/Copenhagen
  659. @comment share/postgresql/timezone/Europe/Dublin
  660. @comment share/postgresql/timezone/Europe/Gibraltar
  661. @comment share/postgresql/timezone/Europe/Guernsey
  662. @comment share/postgresql/timezone/Europe/Helsinki
  663. @comment share/postgresql/timezone/Europe/Isle_of_Man
  664. @comment share/postgresql/timezone/Europe/Istanbul
  665. @comment share/postgresql/timezone/Europe/Jersey
  666. @comment share/postgresql/timezone/Europe/Kaliningrad
  667. @comment share/postgresql/timezone/Europe/Kiev
  668. @comment share/postgresql/timezone/Europe/Kirov
  669. @comment share/postgresql/timezone/Europe/Kyiv
  670. @comment share/postgresql/timezone/Europe/Lisbon
  671. @comment share/postgresql/timezone/Europe/Ljubljana
  672. @comment share/postgresql/timezone/Europe/London
  673. @comment share/postgresql/timezone/Europe/Luxembourg
  674. @comment share/postgresql/timezone/Europe/Madrid
  675. @comment share/postgresql/timezone/Europe/Malta
  676. @comment share/postgresql/timezone/Europe/Mariehamn
  677. @comment share/postgresql/timezone/Europe/Minsk
  678. @comment share/postgresql/timezone/Europe/Monaco
  679. @comment share/postgresql/timezone/Europe/Moscow
  680. @comment share/postgresql/timezone/Europe/Nicosia
  681. @comment share/postgresql/timezone/Europe/Oslo
  682. @comment share/postgresql/timezone/Europe/Paris
  683. @comment share/postgresql/timezone/Europe/Podgorica
  684. @comment share/postgresql/timezone/Europe/Prague
  685. @comment share/postgresql/timezone/Europe/Riga
  686. @comment share/postgresql/timezone/Europe/Rome
  687. @comment share/postgresql/timezone/Europe/Samara
  688. @comment share/postgresql/timezone/Europe/San_Marino
  689. @comment share/postgresql/timezone/Europe/Sarajevo
  690. @comment share/postgresql/timezone/Europe/Saratov
  691. @comment share/postgresql/timezone/Europe/Simferopol
  692. @comment share/postgresql/timezone/Europe/Skopje
  693. @comment share/postgresql/timezone/Europe/Sofia
  694. @comment share/postgresql/timezone/Europe/Stockholm
  695. @comment share/postgresql/timezone/Europe/Tallinn
  696. @comment share/postgresql/timezone/Europe/Tirane
  697. @comment share/postgresql/timezone/Europe/Tiraspol
  698. @comment share/postgresql/timezone/Europe/Ulyanovsk
  699. @comment share/postgresql/timezone/Europe/Uzhgorod
  700. @comment share/postgresql/timezone/Europe/Vaduz
  701. @comment share/postgresql/timezone/Europe/Vatican
  702. @comment share/postgresql/timezone/Europe/Vienna
  703. @comment share/postgresql/timezone/Europe/Vilnius
  704. @comment share/postgresql/timezone/Europe/Volgograd
  705. @comment share/postgresql/timezone/Europe/Warsaw
  706. @comment share/postgresql/timezone/Europe/Zagreb
  707. @comment share/postgresql/timezone/Europe/Zaporozhye
  708. @comment share/postgresql/timezone/Europe/Zurich
  709. @comment share/postgresql/timezone/Factory
  710. @comment share/postgresql/timezone/GB
  711. @comment share/postgresql/timezone/GB-Eire
  712. @comment share/postgresql/timezone/GMT
  713. @comment share/postgresql/timezone/GMT+0
  714. @comment share/postgresql/timezone/GMT-0
  715. @comment share/postgresql/timezone/GMT0
  716. @comment share/postgresql/timezone/Greenwich
  717. @comment share/postgresql/timezone/HST
  718. @comment share/postgresql/timezone/Hongkong
  719. @comment share/postgresql/timezone/Iceland
  720. @comment share/postgresql/timezone/Indian/Antananarivo
  721. @comment share/postgresql/timezone/Indian/Chagos
  722. @comment share/postgresql/timezone/Indian/Christmas
  723. @comment share/postgresql/timezone/Indian/Cocos
  724. @comment share/postgresql/timezone/Indian/Comoro
  725. @comment share/postgresql/timezone/Indian/Kerguelen
  726. @comment share/postgresql/timezone/Indian/Mahe
  727. @comment share/postgresql/timezone/Indian/Maldives
  728. @comment share/postgresql/timezone/Indian/Mauritius
  729. @comment share/postgresql/timezone/Indian/Mayotte
  730. @comment share/postgresql/timezone/Indian/Reunion
  731. @comment share/postgresql/timezone/Iran
  732. @comment share/postgresql/timezone/Israel
  733. @comment share/postgresql/timezone/Jamaica
  734. @comment share/postgresql/timezone/Japan
  735. @comment share/postgresql/timezone/Kwajalein
  736. @comment share/postgresql/timezone/Libya
  737. @comment share/postgresql/timezone/MET
  738. @comment share/postgresql/timezone/MST
  739. @comment share/postgresql/timezone/MST7MDT
  740. @comment share/postgresql/timezone/Mexico/BajaNorte
  741. @comment share/postgresql/timezone/Mexico/BajaSur
  742. @comment share/postgresql/timezone/Mexico/General
  743. @comment share/postgresql/timezone/NZ
  744. @comment share/postgresql/timezone/NZ-CHAT
  745. @comment share/postgresql/timezone/Navajo
  746. @comment share/postgresql/timezone/PRC
  747. @comment share/postgresql/timezone/PST8PDT
  748. @comment share/postgresql/timezone/Pacific/Apia
  749. @comment share/postgresql/timezone/Pacific/Auckland
  750. @comment share/postgresql/timezone/Pacific/Bougainville
  751. @comment share/postgresql/timezone/Pacific/Chatham
  752. @comment share/postgresql/timezone/Pacific/Chuuk
  753. @comment share/postgresql/timezone/Pacific/Easter
  754. @comment share/postgresql/timezone/Pacific/Efate
  755. @comment share/postgresql/timezone/Pacific/Enderbury
  756. @comment share/postgresql/timezone/Pacific/Fakaofo
  757. @comment share/postgresql/timezone/Pacific/Fiji
  758. @comment share/postgresql/timezone/Pacific/Funafuti
  759. @comment share/postgresql/timezone/Pacific/Galapagos
  760. @comment share/postgresql/timezone/Pacific/Gambier
  761. @comment share/postgresql/timezone/Pacific/Guadalcanal
  762. @comment share/postgresql/timezone/Pacific/Guam
  763. @comment share/postgresql/timezone/Pacific/Honolulu
  764. @comment share/postgresql/timezone/Pacific/Johnston
  765. @comment share/postgresql/timezone/Pacific/Kanton
  766. @comment share/postgresql/timezone/Pacific/Kiritimati
  767. @comment share/postgresql/timezone/Pacific/Kosrae
  768. @comment share/postgresql/timezone/Pacific/Kwajalein
  769. @comment share/postgresql/timezone/Pacific/Majuro
  770. @comment share/postgresql/timezone/Pacific/Marquesas
  771. @comment share/postgresql/timezone/Pacific/Midway
  772. @comment share/postgresql/timezone/Pacific/Nauru
  773. @comment share/postgresql/timezone/Pacific/Niue
  774. @comment share/postgresql/timezone/Pacific/Norfolk
  775. @comment share/postgresql/timezone/Pacific/Noumea
  776. @comment share/postgresql/timezone/Pacific/Pago_Pago
  777. @comment share/postgresql/timezone/Pacific/Palau
  778. @comment share/postgresql/timezone/Pacific/Pitcairn
  779. @comment share/postgresql/timezone/Pacific/Pohnpei
  780. @comment share/postgresql/timezone/Pacific/Ponape
  781. @comment share/postgresql/timezone/Pacific/Port_Moresby
  782. @comment share/postgresql/timezone/Pacific/Rarotonga
  783. @comment share/postgresql/timezone/Pacific/Saipan
  784. @comment share/postgresql/timezone/Pacific/Samoa
  785. @comment share/postgresql/timezone/Pacific/Tahiti
  786. @comment share/postgresql/timezone/Pacific/Tarawa
  787. @comment share/postgresql/timezone/Pacific/Tongatapu
  788. @comment share/postgresql/timezone/Pacific/Truk
  789. @comment share/postgresql/timezone/Pacific/Wake
  790. @comment share/postgresql/timezone/Pacific/Wallis
  791. @comment share/postgresql/timezone/Pacific/Yap
  792. @comment share/postgresql/timezone/Poland
  793. @comment share/postgresql/timezone/Portugal
  794. @comment share/postgresql/timezone/ROC
  795. @comment share/postgresql/timezone/ROK
  796. @comment share/postgresql/timezone/Singapore
  797. @comment share/postgresql/timezone/Turkey
  798. @comment share/postgresql/timezone/UCT
  799. @comment share/postgresql/timezone/US/Alaska
  800. @comment share/postgresql/timezone/US/Aleutian
  801. @comment share/postgresql/timezone/US/Arizona
  802. @comment share/postgresql/timezone/US/Central
  803. @comment share/postgresql/timezone/US/East-Indiana
  804. @comment share/postgresql/timezone/US/Eastern
  805. @comment share/postgresql/timezone/US/Hawaii
  806. @comment share/postgresql/timezone/US/Indiana-Starke
  807. @comment share/postgresql/timezone/US/Michigan
  808. @comment share/postgresql/timezone/US/Mountain
  809. @comment share/postgresql/timezone/US/Pacific
  810. @comment share/postgresql/timezone/US/Samoa
  811. @comment share/postgresql/timezone/UTC
  812. @comment share/postgresql/timezone/Universal
  813. @comment share/postgresql/timezone/W-SU
  814. @comment share/postgresql/timezone/WET
  815. @comment share/postgresql/timezone/Zulu
  816. @comment share/postgresql/timezone/posixrules
  817. share/postgresql/timezonesets/Africa.txt
  818. share/postgresql/timezonesets/America.txt
  819. share/postgresql/timezonesets/Antarctica.txt
  820. share/postgresql/timezonesets/Asia.txt
  821. share/postgresql/timezonesets/Atlantic.txt
  822. share/postgresql/timezonesets/Australia
  823. share/postgresql/timezonesets/Australia.txt
  824. share/postgresql/timezonesets/Default
  825. share/postgresql/timezonesets/Etc.txt
  826. share/postgresql/timezonesets/Europe.txt
  827. share/postgresql/timezonesets/India
  828. share/postgresql/timezonesets/Indian.txt
  829. share/postgresql/timezonesets/Pacific.txt
  830. share/postgresql/tsearch_data/danish.stop
  831. share/postgresql/tsearch_data/dutch.stop
  832. share/postgresql/tsearch_data/english.stop
  833. share/postgresql/tsearch_data/finnish.stop
  834. share/postgresql/tsearch_data/french.stop
  835. share/postgresql/tsearch_data/german.stop
  836. share/postgresql/tsearch_data/hungarian.stop
  837. share/postgresql/tsearch_data/hunspell_sample.affix
  838. share/postgresql/tsearch_data/hunspell_sample_long.affix
  839. share/postgresql/tsearch_data/hunspell_sample_long.dict
  840. share/postgresql/tsearch_data/hunspell_sample_num.affix
  841. share/postgresql/tsearch_data/hunspell_sample_num.dict
  842. share/postgresql/tsearch_data/ispell_sample.affix
  843. share/postgresql/tsearch_data/ispell_sample.dict
  844. share/postgresql/tsearch_data/italian.stop
  845. share/postgresql/tsearch_data/norwegian.stop
  846. share/postgresql/tsearch_data/portuguese.stop
  847. share/postgresql/tsearch_data/russian.stop
  848. share/postgresql/tsearch_data/spanish.stop
  849. share/postgresql/tsearch_data/swedish.stop
  850. share/postgresql/tsearch_data/synonym_sample.syn
  851. share/postgresql/tsearch_data/thesaurus_sample.ths
  852. share/postgresql/tsearch_data/turkish.stop
  853. @owner
  854. @group
  855. @mode
Collapse this list.
Dependency lines:
  • postgresql10-server>0:databases/postgresql10-server
Conflicts:
CONFLICTS:
  • postgresql1[^0]*
Conflicts Matches:
There are no Conflicts Matches for this port. This is usually an error.
To install the port:
cd /usr/ports/databases/postgresql10-server/ && make install clean
To add the package, run one of these commands:
  • pkg install databases/postgresql10-server
  • pkg install postgresql10-server
NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above.
PKGNAME: postgresql10-server
Flavors: there is no flavor information for this port.
distinfo:

Packages (timestamps in pop-ups are UTC):
postgresql10-server
ABIlatestquarterly
FreeBSD:11:aarch6410.510.13_2
FreeBSD:11:amd6410.1810.17_2
FreeBSD:11:armv6pkg-fallout10.13_2
FreeBSD:11:i38610.1810.17_2
FreeBSD:11:mipspkg-falloutpkg-fallout
FreeBSD:11:mips64pkg-falloutpkg-fallout
FreeBSD:12:aarch6410.510.23_1
FreeBSD:12:amd6410.23_110.23_1
FreeBSD:12:armv610.510.14
FreeBSD:12:armv710.510.14
FreeBSD:12:i38610.23_110.23_1
FreeBSD:12:mipspkg-falloutpkg-fallout
FreeBSD:12:mips64pkg-falloutpkg-fallout
FreeBSD:12:powerpc64pkg-fallout10.17
FreeBSD:13:aarch6410.23_110.23_1
FreeBSD:13:amd6410.23_110.23_1
FreeBSD:13:armv610.1510.21_1
FreeBSD:13:armv710.23_110.23_1
FreeBSD:13:i38610.23_110.23_1
FreeBSD:13:mipspkg-falloutpkg-fallout
FreeBSD:13:mips64pkg-falloutpkg-fallout
FreeBSD:13:powerpc6410.1510.23_1
FreeBSD:13:riscv64pkg-fallout10.21_1
FreeBSD:14:aarch6410.23_1pkg-fallout
FreeBSD:14:amd6410.23_1pkg-fallout
FreeBSD:14:armv610.23_1pkg-fallout
FreeBSD:14:armv710.23_1pkg-fallout
FreeBSD:14:i38610.23_1pkg-fallout
FreeBSD:14:mipspkg-falloutpkg-fallout
FreeBSD:14:mips64pkg-falloutpkg-fallout
FreeBSD:14:powerpc6410.23_1pkg-fallout
FreeBSD:14:riscv64pkg-falloutpkg-fallout
 
Slave ports:
  1. databases/postgresql10-client
  2. databases/postgresql10-contrib
  3. databases/postgresql10-docs
  4. databases/postgresql10-plperl
  5. databases/postgresql10-plpython
  6. databases/postgresql10-pltcl
Dependencies
NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
Build dependencies:
  1. gmake>=4.3 : devel/gmake
  2. pkgconf>=1.3.0_1 : devel/pkgconf
  3. msgfmt : devel/gettext-tools
Library dependencies:
  1. libicudata.so : devel/icu
  2. libpq.so.5 : databases/postgresql10-client
  3. libintl.so : devel/gettext-runtime
This port is required by:
for Build
  1. databases/postgresql10-plpython
  2. databases/postgresql10-pltcl
for Run
  1. databases/postgresql10-plperl
  2. databases/postgresql10-plpython
  3. databases/postgresql10-pltcl

Configuration Options:
Options name:
USES:
pkg-message:
For install:
WWW: https://www.postgresql.org/
Master Sites:
Expand this list (1 items)
Collapse this list.
  1. https://ftp.postgresql.org/pub/source/v10.23/
Collapse this list.
Notes from UPDATING
These upgrade notes are taken from /usr/ports/UPDATING
  • 2021-10-24
    Affects: users of databases/postgresql* and other software using PostgreSQL to run
    Author: kbowling@FreeBSD.org
    Reason: 
      The default version of PostgreSQL has been switched from 12 to 13.
      The upgrade procedure can use up twice the space the databases
      currently needs. If you have a big amount of stored data take a
      closer look at the manpage of pg_upgrade for avoidance and/or
      speedup of the upgrade.
    
      The upgrade instructions consider a basic usage and do not match
      complex scenarios like replication, sharding, or similar.
    
      Upgrade instructions:
    
      First stop your PostgreSQL, create PostgreSQL-binaries and backup your data.
      If you have another Version of PostgreSQL installed, for example 12.8, your
      files are named according to this.
    
      # service postgresql stop
      # pkg create postgresql12-server postgresql12-contrib
      # mkdir /tmp/pg-upgrade
      # tar xf postgresql12-server-12.8.pkg -C /tmp/pg-upgrade
      # tar xf postgresql12-contrib-12.8.pkg -C /tmp/pg-upgrade
      # pkg delete -f databases/postgresql12-server databases/postgresql12-contrib databases/postgresql12-client
    
      Now update PostgreSQL:
    
        pkg user:
        # pkg install databases/postgresql13-server databases/postgresql13-contrib
        # pkg upgrade
    
        Portmaster users:
        # portmaster databases/postgresql13-server databases/postgresql13-contrib
        # portmaster -a
    
        Portupgrade users:
        # portinstall databases/postgresql13-server databases/postgresql13-contrib
        # portupgrade -a
    
      After installing the new PostgreSQL version you need to convert
      all your databases to new version:
    
      # su -l postgres -c "/usr/local/bin/initdb --encoding=utf-8 --lc-collate=C -D /var/db/postgres/data13 -U postgres"
      # su -l postgres -c "pg_upgrade -b /tmp/pg-upgrade/usr/local/bin/ -d /var/db/postgres/data12/ -B /usr/local/bin/ -D /var/db/postgres/data13/ -U postgres "
    
      Now the migration is finished. You can start PostgreSQL again with:
    
      # service postgresql start
    
      ATTENTION:
      1) The default user changed from "pgsql" to "postgres" in 11. The migration steps above now assume
         the "postgres" database user and FreeBSD user.
      2) See the updating entry 20190829 if you are updating from a release prior to 11.
      3) If you use non-default initdb options, you have to adjust the initdb-command accordingly
    
    
Expand this list (5 items)
  • 2020-09-21
    Affects: users of databases/postgresql* and other software using PostgreSQL to run
    Author: kbowling@FreeBSD.org
    Reason: 
      The default version of PostgreSQL has been switched from 11 to 12.
      The upgrade procedure can use up twice the space the databases
      currently needs. If you have a big amount of stored data take a
      closer look at the manpage of pg_upgrade for avoidance and/or
      speedup of the upgrade.
    
      The upgrade instructions consider a basic usage and do not match
      complex scenarios like replication, sharding, or similar.
    
      Upgrade instructions:
    
      First stop your PostgreSQL, create PostgreSQL-binaries and backup your data.
      If you have another Version of PostgreSQL installed, for example 11.9, your
      files are named according to this.
    
      # service postgresql stop
      # pkg create postgresql11-server postgresql11-contrib
      # mkdir /tmp/pg-upgrade
      # tar xf postgresql11-server-11.9.txz -C /tmp/pg-upgrade
      # tar xf postgresql11-contrib-11.9.txz -C /tmp/pg-upgrade
      # pkg delete -f databases/postgresql11-server databases/postgresql11-contrib databases/postgresql11-client
    
      Now update PostgreSQL:
    
        pkg user:
        # pkg install databases/postgresql12-server databases/postgresql12-contrib
        # pkg upgrade
    
        Portmaster users:
        # portmaster databases/postgresql12-server databases/postgresql12-contrib
        # portmaster -a
    
        Portupgrade users:
        # portinstall databases/postgresql12-server databases/postgresql12-contrib
        # portupgrade -a
    
      After installing the new PostgreSQL version you need to convert
      all your databases to new version:
    
      # su -l postgres -c "/usr/local/bin/initdb --encoding=utf-8 --lc-collate=C -D /var/db/postgres/data12 -U postgres"
      # su -l postgres -c "pg_upgrade -b /tmp/pg-upgrade/usr/local/bin/ -d /var/db/postgres/data11/ -B /usr/local/bin/ -D /var/db/postgres/data12/ -U postgres "
    
      Now the migration is finished. You can start PostgreSQL again with:
    
      # service postgresql start
    
      ATTENTION:
      1) The default user changed from "pgsql" to "postgres" in 11. The migration steps above now assume
         the "postgres" database user and FreeBSD user.
      2) See the updating entry 20190829 if you are updating from a release prior to 11.
      3) If you use non-default initdb options, you have to adjust the initdb-command accordingly
    
    
  • 2019-08-29
    Affects: users of databases/postgresql* and other software using PostgreSQL to run
    Author: tz@FreeBSD.org
    Reason: 
      The default version of PostgreSQL has been switched from 9.5 to 11.
      The upgrade procedure can use up twice the space the databases
      currently needs. If you have a big amount of stored data take a
      closer look at the manpage of pg_upgrade for avoidance and/or
      speedup of the upgrade.
    
      The upgrade instructions consider a basic usage and do not match
      complex scenarios like replication, sharding, or similar.
    
      Upgrade instructions:
    
      First stop your PostgreSQL, create PostgreSQL-binaries and backup your data.
      If you have another Version of PostgreSQL installed, for example 9.5.19, your
      files are named according to this.
    
      # service postgresql stop
      # pkg create postgresql95-server postgresql95-contrib
      # mkdir /tmp/pg-upgrade
      # tar xf postgresql95-server-9.5.19.txz -C /tmp/pg-upgrade
      # tar xf postgresql95-contrib-9.5.19.txz -C /tmp/pg-upgrade
      # pkg delete -f databases/postgresql95-server databases/postgresql95-contrib databases/postgresql95-client
    
      Now update PostgreSQL:
    
        pkg user:
        # pkg install databases/postgresql11-server databases/postgresql11-contrib
        # pkg upgrade
    
        Portmaster users:
        # portmaster databases/postgresql11-server databases/postgresql11-contrib
        # portmaster -a
    
        Portupgrade users:
        # portinstall databases/postgresql11-server databases/postgresql11-contrib
        # portupgrade -a
    
      After installing the new PostgreSQL version you need to convert
      all your databases to new version:
    
      # su -l postgres -c "/usr/local/bin/initdb --encoding=utf-8 --lc-collate=C -D /var/db/postgres/data11 -U pgsql"
      # chown -R postgres /usr/local/pgsql/data/
      # su -l postgres -c "pg_upgrade -b /tmp/pg-upgrade/usr/local/bin/ -d /usr/local/pgsql/data/ -B /usr/local/bin/ -D /var/db/postgres/data11/ -U pgsql "
    
      Now the migration is finished. You can start PostgreSQL again with:
    
      # service postgresql start
    
      ATTENTION:
      1) The default user changed from "pgsql" to "postgres". The migration steps above preserve
         the "pgsql" database user while the database daemon is now executed as the "postgres" FreeBSD user.
      2) The default data dir changed from "/usr/local/pgsql/data/" to "/var/db/postgres/data11/"
      3) If you use non-default initdb options, you have to adjust the initdb-command accordingly
    
    
  • 2017-06-22
    Affects: users of databases/postgresql* and other software using PostgreSQL to run
    Author: tz@FreeBSD.org
    Reason: 
      The default version of PostgreSQL has been switched from 9.3 to 9.5.
      The upgrade procedure can use up twice the space the databases
      currently needs. If you have a big amount of stored data take a
      closer look at the manpage of pg_upgrade for avoidance and/or
      speedup of the upgrade.
    
      The upgrade instructions consider a basic usage and do not match
      complex scenarios like replication, sharding, or similar.
    
      Upgrade instructions:
    
      First stop your PostgreSQL, create PostgreSQL-binaries and backup your data.
      If you have another Version of PostgreSQL installed, for example 9.3.12, your
      files are named according to this.
    
      # service postgresql stop
      # pkg create postgresql93-server postgresql93-contrib
      # mkdir /tmp/pg-upgrade
      # tar xf postgresql93-server-9.3.17.txz -C /tmp/pg-upgrade
      # tar xf postgresql93-contrib-9.3.17.txz -C /tmp/pg-upgrade
      # mv /usr/local/pgsql/data /usr/local/pgsql/data93
      # pkg delete -f databases/postgresql93-server databases/postgresql93-contrib databases/postgresql93-client
    
      Now update PostgreSQL:
    
        pkg user:
        # pkg install databases/postgresql95-server databases/postgresql95-contrib
        # pkg upgrade
    
        Portmaster users:
        # portmaster databases/postgresql95-server databases/postgresql95-contrib
        # portmaster -a
    
        Portupgrade users:
        # portinstall databases/postgresql95-server databases/postgresql95-contrib
        # portupgrade -a
    
      After installing the new PostgreSQL version you need to convert
      all your databases to new version:
    
      # service postgresql initdb
      # su -l pgsql -c "pg_upgrade -b /tmp/pg-upgrade/usr/local/bin/ -d /usr/local/pgsql/data93/ -B /usr/local/bin/ -D /usr/local/pgsql/data/"
    
      Now the migration is finished. You can start PostgreSQL again with:
    
      # service postgresql start
    
    
  • 2014-02-11
    Affects: users of lang/php* databases/postgresql* databases/mysql* www/apache*
    Author: mat@FreeBSD.org
    Reason: 
      The default versions of lang/php*, databases/postgresql*,
      databases/mysql* and www/apache* have been changed to support the
      new DEFAULT_VERSIONS variable.
    
      DEFAULT_APACHE_VER, DEFAULT_MYSQL_VER, DEFAULT_PGSQL_VER,
      DEFAULT_FPC_VER and DEFAULT_PHP_VER are now deprecated.  You can use
      the new DEFAULT_VERSIONS variable like this:
    
      DEFAULT_VERSIONS=php=5.5 mysql=5.6 apache=2.4
    
    
  • 2012-05-30
    Affects: users of databases/postgresql*-server
    Author: jgh@FreeBSD.org
    Reason: 
      Affected users are those who use the crypt(text, text) function with
      DES encryption in the optional pg_crypto module. Passwords affected
      are those that contain characters that cannot be represented with
      7-bit ASCII. If a password contains a character that has the most
      significant bit set (0x80), and DES encryption is used, that character
      and all characters after it will be ignored.
    
    
  • Collapse this list.

Number of commits found: 74

Commit History - (may be incomplete: for full details, see links to repositories near top of page)
CommitCreditsLog message
10.23_1
15 Nov 2022 15:40:59
commit hash:d512e8cce2abc9375784bc1dc4c91d5353e867a0commit hash:d512e8cce2abc9375784bc1dc4c91d5353e867a0commit hash:d512e8cce2abc9375784bc1dc4c91d5353e867a0commit hash:d512e8cce2abc9375784bc1dc4c91d5353e867a0 files touched by this commit
Dmitry Marakasov (amdmi3) search for other commits by this committer
databases/postgresql*-server: require mountlate in rc.d scripts

PostgreSQL server may use late-mounted filesystems, so require these
in rc.d scripts. Real life example is when /tmp is late-mounted tmpfs
atop of ZFS, and if posgresql-server starts before mountlate, its
socket which resides on /tmp is hidden under tmpfs which is mounted
afterwards.

PR:		267500
Approved by:	maintainer timeout (pgsql, 2 weeks)
10.23
10 Nov 2022 16:23:11
commit hash:792a1db259a1e0b8588727d5a200dc62dac54ae8commit hash:792a1db259a1e0b8588727d5a200dc62dac54ae8commit hash:792a1db259a1e0b8588727d5a200dc62dac54ae8commit hash:792a1db259a1e0b8588727d5a200dc62dac54ae8 files touched by this commit
Palle Girgensohn (girgen) search for other commits by this committer
databases/postgresq??-*: update to latest version

PostgreSQL 15.1, 14.6, 13.9, 12.13, 11.18, and 10.23 Released!

The PostgreSQL Global Development Group has released an update to all
supported versions of PostgreSQL, including 15.1, 14.6, 13.9, 12.13,
11.18, and 10.23. This release fixes 25 bugs reported over the last
several months.

This is the final release of PostgreSQL 10. PostgreSQL 10 will no longer
receive security and bug fixes. If you are running PostgreSQL 10 in a
production environment, we suggest that you make plans to upgrade.

Release notes:	https://www.postgresql.org/docs/release/
10.22_2
19 Oct 2022 08:10:29
commit hash:dfe25d73e7fdd333c59008a4ec1859c7f93dacd6commit hash:dfe25d73e7fdd333c59008a4ec1859c7f93dacd6commit hash:dfe25d73e7fdd333c59008a4ec1859c7f93dacd6commit hash:dfe25d73e7fdd333c59008a4ec1859c7f93dacd6 files touched by this commit
Jan Beich (jbeich) search for other commits by this committer
devel/icu: update to 72.1

Changes:	https://github.com/unicode-org/icu/releases/tag/release-72-1
Reported by:	GitHub (watch releases)
PR:		266582
Exp-run by:	antoine
10.22_1
03 Oct 2022 10:53:40
commit hash:72588c54b875233eb146e244461e8a6bbc35eed3commit hash:72588c54b875233eb146e244461e8a6bbc35eed3commit hash:72588c54b875233eb146e244461e8a6bbc35eed3commit hash:72588c54b875233eb146e244461e8a6bbc35eed3 files touched by this commit
Palle Girgensohn (girgen) search for other commits by this committer
databases/postgresql1[012]-server: fix bad plist (again)

Previous fix was incomplete and plain wrong. Fix properly.

Noted by:	sunpoet@
10.22
03 Oct 2022 08:29:02
commit hash:c54eaee9b25b1e5a82d00277e2dca7ccf67c0a81commit hash:c54eaee9b25b1e5a82d00277e2dca7ccf67c0a81commit hash:c54eaee9b25b1e5a82d00277e2dca7ccf67c0a81commit hash:c54eaee9b25b1e5a82d00277e2dca7ccf67c0a81 files touched by this commit
Palle Girgensohn (girgen) search for other commits by this committer
databases/postgresql??-server: fix bad PLIST substitutions

Noted by:	sunpoet@
10.22
14 Sep 2022 04:10:22
commit hash:d06aa00bb41c25880dd99fef34b5c97704af4a33commit hash:d06aa00bb41c25880dd99fef34b5c97704af4a33commit hash:d06aa00bb41c25880dd99fef34b5c97704af4a33commit hash:d06aa00bb41c25880dd99fef34b5c97704af4a33 files touched by this commit
Alexey Dokuchaev (danfe) search for other commits by this committer
databases/postgresql*-server: fix minor style bugs in maintenance script

Convert to ASCII and trim EOL whitespace.  The scripts are now identical
across all PostgreSQL server versions we have in the ports.

Verified by:	cksum(1)
10.22
10 Sep 2022 17:41:16
commit hash:e79fe1aabc5b83364240652d62b99198a9ccfb32commit hash:e79fe1aabc5b83364240652d62b99198a9ccfb32commit hash:e79fe1aabc5b83364240652d62b99198a9ccfb32commit hash:e79fe1aabc5b83364240652d62b99198a9ccfb32 files touched by this commit
Stefan Eßer (se) search for other commits by this committer
Author: Tobias Kortkamp
Fix WWW in parent/child ports

Many of the WWW are overwritten later which means the wrong value
is used. This did not happen before where the children were either
 a) just using the pkg-descr from the parents
 b) or had their own separate pkg-descr with custom WWW

Use WWW?= in parents when the child's WWW is different.

Children that use the same WWW as the parent can just inherit it,
i.e., the child WWW can be removed.

Approved by:	portmgr (implicit)
07 Sep 2022 21:58:51
commit hash:fb16dfecae4a6efac9f3a78e0b759fb7a3c53de4commit hash:fb16dfecae4a6efac9f3a78e0b759fb7a3c53de4commit hash:fb16dfecae4a6efac9f3a78e0b759fb7a3c53de4commit hash:fb16dfecae4a6efac9f3a78e0b759fb7a3c53de4 files touched by this commit
Stefan Eßer (se) search for other commits by this committer
Remove WWW entries moved into port Makefiles

Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.

This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.

Approved by:		portmgr (tcberner)
10.22
07 Sep 2022 21:10:59
commit hash:b7f05445c00f2625aa19b4154ebcbce5ed2daa52commit hash:b7f05445c00f2625aa19b4154ebcbce5ed2daa52commit hash:b7f05445c00f2625aa19b4154ebcbce5ed2daa52commit hash:b7f05445c00f2625aa19b4154ebcbce5ed2daa52 files touched by this commit
Stefan Eßer (se) search for other commits by this committer
Add WWW entries to port Makefiles

It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.

Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.

There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above View all of this commit message)
10.22
12 Aug 2022 09:05:24
commit hash:2e7e556d443e7ff948d0936ae65ead36825f5544commit hash:2e7e556d443e7ff948d0936ae65ead36825f5544commit hash:2e7e556d443e7ff948d0936ae65ead36825f5544commit hash:2e7e556d443e7ff948d0936ae65ead36825f5544 files touched by this commit
Palle Girgensohn (girgen) search for other commits by this committer
databases/postgresql??-*: Update to latest version

The PostgreSQL Global Development Group has released an update to all
supported versions of PostgreSQL, including 14.5, 13.8, 12.12, 11.17,
and 10.22, as well as the third beta release of PostgreSQL 15. This
release closes one security vulnerability and fixes over 40 bugs
reported over the last three months.

PostgreSQL 10 will stop receiving fixes on November 10, 2022. If you are
running PostgreSQL 10 in a production environment, we strongly advise
that you make plans to upgrade to a newer, supported version of
PostgreSQL so you can continue to receive bug and security fixes.

Security:	CVE-2022-2625
Release
notes:	https://www.postgresql.org/about/news/postgresql-145-138-1212-1117-1022-and-15-beta-3-released-2496/
10.21_1
20 Jul 2022 14:21:07
commit hash:d076ad94e206dda108061fe99ddb860d93cc6d16commit hash:d076ad94e206dda108061fe99ddb860d93cc6d16commit hash:d076ad94e206dda108061fe99ddb860d93cc6d16commit hash:d076ad94e206dda108061fe99ddb860d93cc6d16 files touched by this commit
Tobias C. Berner (tcberner) search for other commits by this committer
databases: remove 'Created by' lines

A big Thank You to the original contributors of these ports:

  *  "Choe, Cheng-Dae" whitekid
  *  "Mahdi Mokhtari <mokhi64@gmail.com>"
  *  "Meikel Brandmeyer" <ocaml-sqlite3-port@kotka.de>
  *  <hvo.pm@xs4all.nl>
  *  <jsmith@resonatingmedia.com>
  *  <ports@c0decafe.net>
  *  Aaron Dalton <aaron@FreeBSD.org>
  *  Adam Weinberger <adamw@FreeBSD.org>
  *  Ade Lovett <ade@FreeBSD.org>
  *  Akinori MUSHA aka knu <knu@idaemons.org>
  *  Alan Snelson <Alan@Wave2.org>
(Only the first 15 lines of the commit message are shown above View all of this commit message)
10.21_1
23 May 2022 10:46:14
commit hash:9230d75a823cc4191f4ad358422762b175e91ccdcommit hash:9230d75a823cc4191f4ad358422762b175e91ccdcommit hash:9230d75a823cc4191f4ad358422762b175e91ccdcommit hash:9230d75a823cc4191f4ad358422762b175e91ccd files touched by this commit
Palle Girgensohn (girgen) search for other commits by this committer
postgresql??-server: fix regression in the rc script

The rc script was converted to use a SUB_LIST variable, but I failed to
introduce the variable correctly in the Makefile. [1]

The plist for postgresql15-server was incorrect. Fixed this as well.

PR:	264097 [1]
10.21
19 May 2022 13:36:48
commit hash:5b11f47f0d59c95f6dcf1ff75badede5ec84e72ecommit hash:5b11f47f0d59c95f6dcf1ff75badede5ec84e72ecommit hash:5b11f47f0d59c95f6dcf1ff75badede5ec84e72ecommit hash:5b11f47f0d59c95f6dcf1ff75badede5ec84e72e files touched by this commit
Palle Girgensohn (girgen) search for other commits by this committer
databases/postgresql??-*: add postgresql-15 to the ports tree

Introduce PostgreSQL-15 to the ports tree.

Make version 15 the master port, and add plist parameter for the
postgresql version.

Release notes:	https://www.postgresql.org/docs/devel/release.html
10.21
12 May 2022 13:41:07
commit hash:6c00f6e30fbd66a5ccc7173c9f4aca3122cd4c63commit hash:6c00f6e30fbd66a5ccc7173c9f4aca3122cd4c63commit hash:6c00f6e30fbd66a5ccc7173c9f4aca3122cd4c63commit hash:6c00f6e30fbd66a5ccc7173c9f4aca3122cd4c63 files touched by this commit
Palle Girgensohn (girgen) search for other commits by this committer
databases/postgresql??-server: update to latest version

The PostgreSQL Global Development Group has released an update to all
supported versions of PostgreSQL, including 14.3, 13.7, 12.11, 11.16,
and 10.21. This release fixes over 50 bugs reported over the last three
months. This release closes one security vulnerability and fixes over 50
bugs reported over the last three months.

We encourage you to install this update at your earliest possible
convenience.

If you have any GiST indexes on columns using the ltree data type, you
will need to reindex them after upgrading.

For the full list of changes, please review the release notes.
(Only the first 15 lines of the commit message are shown above View all of this commit message)
10.20_1
07 Apr 2022 00:39:10
commit hash:268cee3b0227efd217869b43152e8936a05cb850commit hash:268cee3b0227efd217869b43152e8936a05cb850commit hash:268cee3b0227efd217869b43152e8936a05cb850commit hash:268cee3b0227efd217869b43152e8936a05cb850 files touched by this commit This port version is marked as vulnerable.
Jan Beich (jbeich) search for other commits by this committer
devel/icu: update to 71.1

Changes:	https://github.com/unicode-org/icu/releases/tag/release-71-1
Reported by:	GitHub (watch releases)
PR:		262654
Exp-run by:	antoine
Approved by:	fluffy
10.20
10 Feb 2022 14:17:45
commit hash:7acb062c33ea0c0a2124a3b83bbf94c0352eb8eacommit hash:7acb062c33ea0c0a2124a3b83bbf94c0352eb8eacommit hash:7acb062c33ea0c0a2124a3b83bbf94c0352eb8eacommit hash:7acb062c33ea0c0a2124a3b83bbf94c0352eb8ea files touched by this commit This port version is marked as vulnerable.
Palle Girgensohn (girgen) search for other commits by this committer
databases/postgresql??-server: Upgrade to latest version

The PostgreSQL Global Development Group has released an update to all
supported versions of PostgreSQL, including 14.2, 13.6, 12.10, 11.15,
and 10.20. This release fixes over 55 bugs reported over the last three
months.

Announcement:	https://www.postgresql.org/about/news/postgresql-142-136-1210-1115-and-1020-released-2402/
Release notes:	https://www.postgresql.org/docs/release/
10.19
20 Dec 2021 00:19:02
commit hash:cc8444836e07e8a6e2a9f823a4b276c16a56e59ecommit hash:cc8444836e07e8a6e2a9f823a4b276c16a56e59ecommit hash:cc8444836e07e8a6e2a9f823a4b276c16a56e59ecommit hash:cc8444836e07e8a6e2a9f823a4b276c16a56e59e files touched by this commit This port version is marked as vulnerable.
Piotr Kubaj (pkubaj) search for other commits by this committer
databases/postgresql10-server: fix build on riscv64
10.19
11 Nov 2021 14:37:02
commit hash:d3db7630c79762949ca7d0f3cbf1db128ebecca4commit hash:d3db7630c79762949ca7d0f3cbf1db128ebecca4commit hash:d3db7630c79762949ca7d0f3cbf1db128ebecca4commit hash:d3db7630c79762949ca7d0f3cbf1db128ebecca4 files touched by this commit This port version is marked as vulnerable.
Palle Girgensohn (girgen) search for other commits by this committer
databases/postgresql??-*: updated to latest version

This release contains a variety of fixes from the previous version.

A dump/restore is not required for those running the same major version.
However, note that installations using physical replication should
update standby servers before the primary server, as explained in the
release notes.

Also, several bugs have been found that may have resulted in corrupted
indexes, as explained in the next several changelog entries.  If any of
those cases apply to you, it's recommended to reindex possibly-affected
indexes after updating.

This release also mitigates two possible man-in-the-middle attacks.

Security:	2ccd71bd-426b-11ec-87db-6cc21735f730
Release notes:	https://www.postgresql.org/docs/release/14.1/
10.18_1
28 Oct 2021 16:37:30
commit hash:f34ece3aa6a292628ea75c0e4dd2a04d879ab0a3commit hash:f34ece3aa6a292628ea75c0e4dd2a04d879ab0a3commit hash:f34ece3aa6a292628ea75c0e4dd2a04d879ab0a3commit hash:f34ece3aa6a292628ea75c0e4dd2a04d879ab0a3 files touched by this commit This port version is marked as vulnerable.
Jan Beich (jbeich) search for other commits by this committer
devel/icu: update to 70.1

Changes:	https://github.com/unicode-org/icu/releases/tag/release-70-1
Reported by:	GitHub (watch releases)
PR:		258794
Exp-run by:	antoine
10.18
12 Aug 2021 16:23:00
commit hash:a271b9d5b7b2c0eb57d1a09fc44f2ecbbad7bc5acommit hash:a271b9d5b7b2c0eb57d1a09fc44f2ecbbad7bc5acommit hash:a271b9d5b7b2c0eb57d1a09fc44f2ecbbad7bc5acommit hash:a271b9d5b7b2c0eb57d1a09fc44f2ecbbad7bc5a files touched by this commit This port version is marked as vulnerable.
Palle Girgensohn (girgen) search for other commits by this committer
databases/postgresql*: update to latest versions

The PostgreSQL Global Development Group has released an update to all supported
versions of our database system, including 13.4, 12.8, 11.13, 10.18, and
9.6.23, as well as the third beta release of PostgreSQL 14. This release closes
one security vulnerability and fixes over 75 bugs reported over the last three
months.

Turn off parallel builds since we continue to struggle with build problems when
it is activated. [1]

Avoid chasing latest LLVM version. [2]

PR:		256466 [1], 256167 [2]
Release notes:	https://www.postgresql.org/docs/release/
Security:	b471130b-fb86-11eb-87db-6cc21735f730
10.17_2
27 Jul 2021 20:06:33
commit hash:eae54f6c6d796d71a24141534fab318aa70b6705commit hash:eae54f6c6d796d71a24141534fab318aa70b6705commit hash:eae54f6c6d796d71a24141534fab318aa70b6705commit hash:eae54f6c6d796d71a24141534fab318aa70b6705 files touched by this commit This port version is marked as vulnerable.
Li-Wen Hsu (lwhsu) search for other commits by this committer
databases/postgresql10-server: Fix typo in rc script

PR:		257447
Reported by:	Tom Warnke <tom@toromtomtom.com>
MFH:		2021Q3
10.17_1
01 Jun 2021 13:59:35
commit hash:8d831eb43aba59013b948830cbd4b22b45deb223commit hash:8d831eb43aba59013b948830cbd4b22b45deb223commit hash:8d831eb43aba59013b948830cbd4b22b45deb223commit hash:8d831eb43aba59013b948830cbd4b22b45deb223 files touched by this commit This port version is marked as vulnerable.
Palle Girgensohn (girgen) search for other commits by this committer
databases/postgresql??-server: rc-script should require DAEMON

Changeset ab83f2b4bb78 changed the startup order for Postgresql. The cleartmp
rc.d now comes after the Postgresql startup.  Unfortunately, Postgresql likes
to create a socket in /tmp/.s.PGSQL.5432. After cleartmp does its work, that
socket disappears from the filesystem.

Submitted by:	Jeroen Pulles
PR:		256335
10.17
20 May 2021 14:38:55
commit hash:fccc45e5ff4a8aea150005196c0d4f2cbaeed5dbcommit hash:fccc45e5ff4a8aea150005196c0d4f2cbaeed5dbcommit hash:fccc45e5ff4a8aea150005196c0d4f2cbaeed5dbcommit hash:fccc45e5ff4a8aea150005196c0d4f2cbaeed5db files touched by this commit This port version is marked as vulnerable.
Palle Girgensohn (girgen) search for other commits by this committer
databases/postgresql14-*: Add postgresql 14 beta1 the the ports tree.

Release notes:	https://www.postgresql.org/docs/devel/release-14.html

Also reintroduce parallel builds. Some components, namely plperl,
plpython, pltcl and contrib, fail to build properly when using parallel
builds. Something with static linking using `ar` that fails.
MAKE_JOBS_UNSAFE is set for these ports.
10.17
15 May 2021 09:12:17
commit hash:ab83f2b4bb78a718efa5c43247ba1e1d207f99b6commit hash:ab83f2b4bb78a718efa5c43247ba1e1d207f99b6commit hash:ab83f2b4bb78a718efa5c43247ba1e1d207f99b6commit hash:ab83f2b4bb78a718efa5c43247ba1e1d207f99b6 files touched by this commit This port version is marked as vulnerable.
Palle Girgensohn (girgen) search for other commits by this committer
databases/postgresql??-*: Upgrade to latest version

PostgreSQL 13.3, 12.7, 11.12, 10.17, and 9.6.22 Released!

The PostgreSQL Global Development Group has released an update to all supported
versions of our database system, including 13.3, 12.7, 11.12, 10.17, and
9.6.22. This release closes three security vulnerabilities and fixes over 45
bugs reported over the last three months.

Security fixes in this release:

CVE-2021-32027: Buffer overrun from integer overflow in array subscripting
                calculations

CVE-2021-32028: Memory disclosure in INSERT ... ON CONFLICT ... DO UPDATE
(Only the first 15 lines of the commit message are shown above View all of this commit message)
10.16_1
20 Apr 2021 04:56:53
commit hash:b91ca3ff3626dbb917aeb82243d140a50ad148b8commit hash:b91ca3ff3626dbb917aeb82243d140a50ad148b8commit hash:b91ca3ff3626dbb917aeb82243d140a50ad148b8commit hash:b91ca3ff3626dbb917aeb82243d140a50ad148b8 files touched by this commit This port version is marked as vulnerable.
Loïc Bartoletti (lbartoletti) search for other commits by this committer
databases/postgresql*: Fix build on riscv64

Reported by:	tmunro
Reviewed by:	girgen
10.16_1
08 Apr 2021 23:33:31
commit hash:69d24a727d44d398f7357cb844386f3ec4750a4fcommit hash:69d24a727d44d398f7357cb844386f3ec4750a4fcommit hash:69d24a727d44d398f7357cb844386f3ec4750a4fcommit hash:69d24a727d44d398f7357cb844386f3ec4750a4f files touched by this commit This port version is marked as vulnerable.
Jan Beich (jbeich) search for other commits by this committer
devel/icu: update to 69.1

Changes:	https://github.com/unicode-org/icu/releases/tag/release-69-1
Reported by:	GitHub (watch releases)
10.16
06 Apr 2021 14:31:13
commit hash:135fdeebb99c3569e42d8162b265e15d29bd937dcommit hash:135fdeebb99c3569e42d8162b265e15d29bd937dcommit hash:135fdeebb99c3569e42d8162b265e15d29bd937dcommit hash:135fdeebb99c3569e42d8162b265e15d29bd937d files touched by this commit This port version is marked as vulnerable.
Mathieu Arnold (mat) search for other commits by this committer
all: Remove all other $FreeBSD keywords.
10.16
06 Apr 2021 14:31:07
commit hash:305f148f482daf30dcf728039d03d019f88344ebcommit hash:305f148f482daf30dcf728039d03d019f88344ebcommit hash:305f148f482daf30dcf728039d03d019f88344ebcommit hash:305f148f482daf30dcf728039d03d019f88344eb files touched by this commit This port version is marked as vulnerable.
Mathieu Arnold (mat) search for other commits by this committer
Remove # $FreeBSD$ from Makefiles.
10.16
11 Feb 2021 14:34:02
Revision:564956Original commit files touched by this commit This port version is marked as vulnerable.
girgen search for other commits by this committer
PostgreSQL 13.2, 12.6, 11.11, 10.16, 9.6.21, and 9.5.25 released

The PostgreSQL Global Development Group has released an update to all supported
versions of our database system, including 13.2, 12.6, 11.11, 10.16, 9.6.21,
and 9.5.25. This release closes two security vulnerabilities and fixes over 80
bugs reported over the last three months.

Additionally, this is the final release of PostgreSQL 9.5. If you are running
PostgreSQL 9.5 in a production environment, we suggest that you make plans to
upgrade.

Release
notes:	https://www.postgresql.org/about/news/postgresql-132-126-1111-1016-9621-and-9525-released-2165/
Security notes:	https://www.postgresql.org/support/security/
Security:	CVE-2021-3393, CVE-2021-20229
10.15
12 Nov 2020 15:00:40
Revision:554966Original commit files touched by this commit This port version is marked as vulnerable.
girgen search for other commits by this committer
PostgreSQL 13.1, 12.5, 11.10, 10.15, 9.6.20 released!

The PostgreSQL Global Development Group has released an update to all supported
versions of our database system, including 13.1, 12.5, 11.10, 10.15 and 9.6.20.
This release closes three security vulnerabilities and fixes over 65 bugs
reported over the last three months.

Due to the nature of CVE-2020-25695, we advise you to update as soon as
possible.

Additionally, this is the second-to-last release of PostgreSQL 9.5. If you are
running PostgreSQL 9.5 in a production environment, we suggest that you make
plans to upgrade.

For the full list of changes, please review the release notes.

Security:	CVE-2020-25695: Multiple features escape "security restricted
				operation" sandbox

Security:	CVE-2020-25694: Reconnection can downgrade connection security
				settings

Security:	CVE-2020-25696: psql's \gset allows overwriting specially
				treated variables
10.14_1
03 Nov 2020 00:56:27
Revision:553940Original commit files touched by this commit This port version is marked as vulnerable.
jbeich search for other commits by this committer
devel/icu: update to 68.1

Changes:	http://site.icu-project.org/download/68
ABI:		https://abi-laboratory.pro/tracker/timeline/icu4c/
Reported by:	GitHub (watch releases)
10.14
24 Sep 2020 13:33:10
Revision:549921Original commit files touched by this commit This port version is marked as vulnerable.
girgen search for other commits by this committer
Welcome PostgreSQL 13

Release notes:	https://www.postgresql.org/about/news/2077/
10.14
13 Aug 2020 13:45:03
Revision:544810Original commit files touched by this commit This port version is marked as vulnerable.
girgen search for other commits by this committer
The PostgreSQL Global Development Group has released an update to all
supported versions of our database system, including 12.4, 11.9, 10.14,
9.6.19, and 9.5.23.

This release closes two security vulnerabilities and fixes over 50 bugs
reported over the last three months.

Please plan to update at your earliest convenience.

Security Issues
---------------

* CVE-2020-14349: Uncontrolled search path element in logical replication.

Versions Affected: 10 - 12.
(Only the first 15 lines of the commit message are shown above View all of this commit message)
10.13_2
17 May 2020 20:37:04
Revision:535676Original commit files touched by this commit This port version is marked as vulnerable.
girgen search for other commits by this committer
The PostgreSQL Global Development Group has released an update to all
supported versions of our database system, including 12.3, 11.8, 10.13,
9.6.18, and 9.5.22.  This release fixes one security issue found in the
PostgreSQL server and over 75 bugs reported over the last three months.

Please plan to update at your earliest convenience.

Update the backup warning text. [1]

Add plpython and plperl libs for hstore, jsonb and ltree for the versions where
they exist. These libs are added to the postgresql??-plpython and -plperl
ports, inspired by [2].

PR:		237910 [1], 245246 [2]
Submitted by:	Francesco [1], Loic Bartoletti [2]
10.12_2
23 Apr 2020 20:14:49
Revision:532707Original commit files touched by this commit This port version is marked as vulnerable.
jbeich search for other commits by this committer
devel/icu: update to 67.1

Changes:	http://site.icu-project.org/download/67
ABI:		https://abi-laboratory.pro/tracker/timeline/icu4c/
Reported by:	GitHub (watch releases)
10.12_1
13 Mar 2020 09:54:52
Revision:528344Original commit files touched by this commit This port version is marked as vulnerable.
jbeich search for other commits by this committer
Fix up PORTREVISION style after "portedit bump-revision"
10.12_1
13 Mar 2020 09:47:17
Revision:528343Original commit files touched by this commit This port version is marked as vulnerable.
jbeich search for other commits by this committer
devel/icu: update to 66.1

Changes:	http://site.icu-project.org/download/66
ABI:		https://abi-laboratory.pro/tracker/timeline/icu4c/
10.12
13 Feb 2020 19:14:37
Revision:526063Original commit files touched by this commit This port version is marked as vulnerable.
girgen search for other commits by this committer
The PostgreSQL Global Development Group has released an update to all
supported versions of our database system, including 12.2, 11.7, 10.12,
9.6.17, 9.5.21, and 9.4.26. This release fixes one security issue found
in the PostgreSQL server and over 75 bugs reported over the last three
months.

Users should plan to update as soon as possible.

PostgreSQL 9.4 Now EOL

This is the last release for PostgreSQL 9.4, which will no longer
receive security updates and bug fixes. PostgreSQL 9.4 introduced new
features such as JSONB support, the `ALTER SYSTEM` command, the ability
to stream logical changes to an output plugin, and more:
(Only the first 15 lines of the commit message are shown above View all of this commit message)
10.11
30 Dec 2019 18:04:40
Revision:521556Original commit files touched by this commit This port version is marked as vulnerable.
adamw search for other commits by this committer
postgresql{96,10,11}-contrib: Add an XML option

Avoids the libxml/libxslt2 dependency chain for systems that don't need
the XML datatype plugin.

PR:		239638
Approved by:	maintainer timeout (pgsql team, nearly 5 months)
10.11
14 Nov 2019 16:24:45
Revision:517600Original commit files touched by this commit This port version is marked as vulnerable.
girgen search for other commits by this committer
Upgrade PostgreSQL

The PostgreSQL Global Development Group has released an update to all
supported versions of our database system, including 12.1, 11.6, 10.11,
9.6.16, 9.5.20, and 9.4.25. This release fixes over 50 bugs reported
over the last three months.

PostgreSQL 9.4 will stop receiving fixes on February 13, 2020, which is
the next planned cumulative update release. We suggest that you make
plans to upgrade to a newer, supported version of PostgreSQL. Please see
our versioning policy for more information:

This update also fixes over 50 bugs that were reported in the last
several months. Some of these issues affect only version 12, but may
also affect all supported versions.

Specific change to the FreeBSD port:
Starting now, the default for TZDATA has changed to using the underlying OS'
time zone database instead of the one built in to PostgreSQL. This change is
made since PostgreSQL will not release a patch in the event where the time zone
database changes, whereas FreeBSD will.

Release notes:	https://www.postgresql.org/about/news/1994/
URL:		https://www.postgresql.org/support/versioning/
10.10_1
03 Oct 2019 20:35:30
Revision:513733Original commit files touched by this commit This port version is marked as vulnerable.
jbeich search for other commits by this committer
devel/icu: update to 65.1

Changes:	http://site.icu-project.org/download/65
ABI:		https://abi-laboratory.pro/tracker/timeline/icu4c/
10.10
13 Aug 2019 16:01:59
Revision:508835Original commit files touched by this commit Sanity Test Failure This port version is marked as vulnerable.
mat search for other commits by this committer
Convert to UCL & cleanup pkg-message (categories d)
10.10
08 Aug 2019 15:33:03
Revision:508390Original commit files touched by this commit This port version is marked as vulnerable.
girgen search for other commits by this committer
iThe PostgreSQL Global Development Group has released an update to all
supported versions of our database system, including 11.5, 10.10,
9.6.15, 9.5.19, and 9.4.24, as well as the third beta of PostgreSQL 12.
This release fixes two security issues in the PostgreSQL server, two
security issues found in one of the PostgreSQL Windows installers, and
over 40 bugs reported since the previous release.

Users should install these updates as soon as possible.

A Note on the PostgreSQL 12 Beta
================================

In the spirit of the open source PostgreSQL community, we strongly
encourage you to test the new features of PostgreSQL 12 in your database
systems to help us eliminate any bugs or other issues that may exist.
(Only the first 15 lines of the commit message are shown above View all of this commit message)
10.9_1
26 Jul 2019 20:46:57
Revision:507372Original commit files touched by this commit This port version is marked as vulnerable.
gerald search for other commits by this committer
Bump PORTREVISION for ports depending on the canonical version of GCC
as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.

This includes ports
 - with USE_GCC=yes or USE_GCC=any,
 - with USES=fortran,
 - using Mk/bsd.octave.mk which in turn features USES=fortran, and
 - with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
   c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.

PR:		238330
10.9
27 Jun 2019 21:28:00
Revision:505245Original commit files touched by this commit This port version is marked as vulnerable.
girgen search for other commits by this committer
Upgrade PostgreSQL to latest version

The PostgreSQL Global Development Group has released an update to all supported
versions of our database system, including 11.4, 10.9, 9.6.14, 9.5.18, and
9.4.23, as well as the second beta of PostgreSQL 12. This release fixes one
security issue and over 25 bugs since the previous cumulative update in May.

This release is made outside of the normal update release schedule as the
security vulnerability was determined to be critical enough to distribute the
fix as quickly as possible. Users who are running PostgreSQL 10, PostgreSQL 11,
or the PostgreSQL 12 beta should upgrade as soon as possible.

All other users should plan to apply this update at the next scheduled
downtime.

Release notes:	https://www.postgresql.org/about/news/1949/
Security:	245629d4-991e-11e9-82aa-6cc21735f730
10.8
09 May 2019 22:32:11
Revision:501149Original commit files touched by this commit This port version is marked as vulnerable.
girgen search for other commits by this committer
The PostgreSQL Global Development Group has released an update to all
supported versions of our database system, including 11.3, 10.8, 9.6.13,
9.5.17, and 9.4.22. This release fixes two security issues in the
PostgreSQL server, a security issue found in two of the PostgreSQL
Windows installers, and over 60 bugs reported over the last three months.

Security:	CVE-2019-10129: Memory disclosure in partition routing

Prior to this release, a user running PostgreSQL 11 can read arbitrary
bytes of server memory by executing a purpose-crafted INSERT statement
to a partitioned table.

Security:	CVE-2019-10130: Selectivity estimators bypass row security policies

PostgreSQL maintains statistics for tables by sampling data available in
(Only the first 15 lines of the commit message are shown above View all of this commit message)
10.7_2
25 Apr 2019 18:34:42
Revision:500060Original commit files touched by this commit This port version is marked as vulnerable.
crees search for other commits by this committer
Don't overwrite PORTREVISION from the slave, following readline update.

I've had to bump revision for several slaves here, but most will not
be rebuilt, except the -client slaves.  Apologies for anyone having
to rebuild -clients unnecessarily, but it's not a heavy task- better safe
than sorry.

PR:		ports/236156
Reported by:	Andrew Dunstan (PostgreSQL), koobs, Dmitri Goutnik
10.7_1
27 Mar 2019 21:11:09
Revision:496981Original commit files touched by this commit This port version is marked as vulnerable.
jbeich search for other commits by this committer
devel/icu: update to 64.1

Changes:	http://site.icu-project.org/download/64
ABI:		https://abi-laboratory.pro/tracker/timeline/icu4c/
PR:		236325
Exp-run by:	antoine
Differential Revision:	https://reviews.freebsd.org/D19479
10.7_1
15 Feb 2019 15:45:23
Revision:493002Original commit files touched by this commit This port version is marked as vulnerable.
girgen search for other commits by this committer
Fix mistake in previous commit about postgres username
10.7
15 Feb 2019 11:02:22
Revision:492989Original commit files touched by this commit This port version is marked as vulnerable.
girgen search for other commits by this committer
The PostgreSQL Global Development Group has released an update to all
supported versions of our database system, including 11.2, 10.7, 9.6.12,
9.5.16, and 9.4.21. This release changes the behavior in how PostgreSQL
interfaces with `fsync()` and includes fixes for partitioning and over
70 other bugs that were reported over the past three months.

Users should plan to apply this update at the next scheduled downtime.

FreeBSD port adds OPTIONS knob to support LLVM JIT. [1]

Highlight: Change in behavior with fsync()
------------------------------------------

When available in an operating system and enabled in the configuration
file (which it is by default), PostgreSQL uses the kernel function
(Only the first 15 lines of the commit message are shown above View all of this commit message)
10.6_2
12 Dec 2018 01:35:36
Revision:487272Original commit files touched by this commit This port version is marked as vulnerable.
gerald search for other commits by this committer
Bump PORTREVISION for ports depending on the canonical version of GCC
defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t
GCC 8.2 under most circumstances.

This includes ports
 - with USE_GCC=yes or USE_GCC=any,
 - with USES=fortran,
 - using Mk/bsd.octave.mk which in turn features USES=fortran, and
 - with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
   c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, as a double check, everything INDEX-11 showed depending on lang/gcc7.

PR:		231590
10.6_1
12 Nov 2018 15:54:20
Revision:484807Original commit files touched by this commit This port version is marked as vulnerable.
girgen search for other commits by this committer
Fix build problems on i386

Use GCC seems to be proper way to do it. SSE2 would not be available for all
CPU:s.
10.6_1
08 Nov 2018 23:21:19
Revision:484488Original commit files touched by this commit This port version is marked as vulnerable.
girgen search for other commits by this committer
Posted on 2018-11-08 by PostgreSQL Global Development Group The PostgreSQL
Global Development Group has released an update to all supported versions of
our database system, including 11.1, 10.6, 9.6.11, 9.5.15, 9.4.20, and 9.3.25.
This release fixes one security issue as well as bugs reported over the last
three months.

All users using the affected versions of PostgreSQL should update as soon as
possible. Please see the notes on "Updating" below for any post-update steps
that may be required if you are using pg_stat_statements in your installation.

This update is also the final release for PostgreSQL 9.3, which is now
end-of-life and will no longer receive any bug or security fixes. If your
environment still uses PostgreSQL 9.3, please make plans to update to a
community supported version as soon as possible. Please see our versioning
policy for more information.

Releasenotes:	https://www.postgresql.org/about/news/1905/
Security:	1c27a706-e3aa-11e8-b77a-6cc21735f730
Security:	CVE-2018-16850
10.5_1
23 Oct 2018 11:35:04
Revision:482830Original commit files touched by this commit This port version is marked as vulnerable.
jbeich search for other commits by this committer
devel/icu: update to 63.1

Changes:	http://site.icu-project.org/download/63
ABI:		https://abi-laboratory.pro/tracker/timeline/icu4c/
PR:		232300
Exp-run by:	antoine
10.5
10 Sep 2018 13:14:52
Revision:479406Original commit files touched by this commit This port version is marked as vulnerable.
mat search for other commits by this committer
Add DOCS options to ports that should have one.

Also various fixes related to said option.

PR:		230864
Submitted by:	mat
exp-runs by:	antoine
10.5
10 Aug 2018 09:25:20
Revision:476819Original commit files touched by this commit This port version is marked as vulnerable.
girgen search for other commits by this committer
The PostgreSQL Global Development Group has released an update to all supported
versions of our database system, including 10.5, 9.6.10, 9.5.14, 9.4.19,
9.3.24.  This release fixes two security issues as well as bugs reported over
the last three months.

If you have untrusted users accessing your system and you are either running
PostgreSQL 9.5 or a newer version OR have installed the "dblink" or
"postgres_fdw" extensions, you must apply this update as soon as possible. All
other users can upgrade at the next convenient downtime.

Please note that PostgreSQL changed its versioning scheme with the release of
version 10.0, so updating to version 10.5 from any 10.x release is considered a
minor update.

The PostgreSQL Global Development Group also announces that the third beta
(Only the first 15 lines of the commit message are shown above View all of this commit message)
10.4_1
29 Jun 2018 14:22:11
Revision:473551Original commit files touched by this commit This port version is marked as vulnerable.
jbeich search for other commits by this committer
devel/icu: update to 62.1

Changes:	http://site.icu-project.org/download/62
ABI:		https://abi-laboratory.pro/tracker/timeline/icu4c/
PR:		229359
Exp-run by:	antoine (only 10.4)
10.4
11 May 2018 13:10:52
Revision:469638Original commit files touched by this commit This port version is marked as vulnerable.
girgen search for other commits by this committer
Up

The PostgreSQL Global Development Group has released an update to all supported
versions of our database system, including 10.4, 9.6.9, 9.5.13, 9.4.18, 9.3.23.
This release fixes one security issue as well as several bugs reported over the
last three months. Users should plan to update at the next convenient downtime.

Please see the "Updating" section for post-installation steps for the security
fix and the "incorrect volatility and parallel-safety markings" fix.

Releasenotes:	https://www.postgresql.org/about/news/1851/
Security:	CVE-2018-1115 Too-permissive access control list on function
pg_logfile_rotate()

FreeBSD's port of PostgreSQL uses syslog by default, so the above security
problem is only a problem if you changed the logging configuration. Please
visit the releasenotes linked above and take the actions needed.
10.3_1
07 May 2018 19:21:01
Revision:469321Original commit files touched by this commit This port version is marked as vulnerable.
sunpoet search for other commits by this committer
Update WWW

Approved by:	portmgr (blanket)
10.3_1
06 Apr 2018 15:53:17
Revision:466648Original commit files touched by this commit This port version is marked as vulnerable.
jbeich search for other commits by this committer
devel/icu: update to 61.1

Changes:	http://site.icu-project.org/download/61
ABI:		https://abi-laboratory.pro/tracker/timeline/icu4c/
PR:		227042
Exp-run by:	antoine
MFH:		2018Q2 (required by Firefox 61)
10.3
01 Mar 2018 15:10:17
Revision:463327Original commit files touched by this commit This port version is marked as vulnerable.
girgen search for other commits by this committer
2018-03-01 Security Update Release

The PostgreSQL Global Development Group has released an update to all supported
versions of the PostgreSQL database system, including 10.3, 9.6.8, 9.5.12,
9.4.17, and 9.3.22.

The purpose of this release is to address CVE-2018-1058, which describes how a
user can create like-named objects in different schemas that can change the
behavior of other users' queries and cause unexpected or malicious behavior,
also known as a "trojan-horse" attack. Most of this release centers around added
documentation that describes the issue and how to take steps to mitigate the
impact on PostgreSQL databases.

We strongly encourage all of our users to please visit
https://wiki.postgresql.org/wiki/A_Guide_to_CVE-2018-1058:_Protect_Your_Search_Path
for a detailed explanation of CVE-2018-1058 and how to protect your PostgreSQL
installations.

After evaluating the documentation for CVE-2018-1058, a database administrator
may need to take follow up steps on their PostgreSQL installations to ensure
they are protected from exploitation.

Security:	CVE-2018-1058
10.2
15 Feb 2018 14:41:29
Revision:461928Original commit files touched by this commit This port version is marked as vulnerable.
brnrd search for other commits by this committer
security/openssl-devel: Remove BROKEN from some ports

 * databases/freetds: Fixed 2017-02-14
 * databases/postgresql10-server: Fixed 2016-09-15 [1]
 * ftp/lftp: Fixed in 4.8.0
 * ftp/proftpd: Fixed in 1.3.5c
 * ftp/wget: Fixed in 1.19.3 [2]
 * lang/erlang-runtime20: Fixed in 20.0
 * net/socat: Fixed in 1.7.3.2
 * security/libssh2: Fixed in 1.8.0 [3]
 * security/p5-Crypt-OpenSSL-X509: Fixed in 1.8.8
 * sysutils/bacula9-server: Fixed in 9.0.6
 * www/nginx: Fixed in 1.9.14

 * Bulk build OK 10.3/11.1 both i386 and amd64:
    - multimedia/librtmp
    - net/libvncserver
    - www/lynx

PR:		225875 [1], 225872 [2], 225873 [3]
10.2
08 Feb 2018 19:58:22
Revision:461263Original commit files touched by this commit This port version is marked as vulnerable.
antoine search for other commits by this committer
Remove DTRACE from OPTIONS_DEFAULT, causes segmentation fault during build

With hat:	portmgr
10.2
08 Feb 2018 17:38:36
Revision:461251Original commit files touched by this commit This port version is marked as vulnerable.
girgen search for other commits by this committer
Update to latest versions of PostgreSQL

2018-02-08 Security Update Release
==================================

The PostgreSQL Global Development Group has released an update to all supported
versions of our database system, including 10.2, 9.6.7, 9.5.11, 9.4.16, 9.3.21.
This release fixes two security issues. This release also fixes issues with
VACUUM, GIN indexes, and hash indexes that could lead to data corruption, as
well as fixes for using parallel queries and logical replication.

All users using the affected versions of PostgreSQL should update as soon as
possible. Please see the notes on "Updating" below for any post-update steps
that may be required.
(Only the first 15 lines of the commit message are shown above View all of this commit message)
10.1_1
30 Jan 2018 13:45:50
Revision:460386Original commit files touched by this commit This port version is marked as vulnerable.
mat search for other commits by this committer
Fix ICU depend for postgresql10-server.

PR:		225049
Submitted by:	mat
Approved by:	maintainer timeout
Sponsored by:	Absolight
10.1_1
20 Dec 2017 22:09:08
Revision:456862Original commit files touched by this commit This port version is marked as vulnerable.
girgen search for other commits by this committer
Fix problem with logical replication

PR:	224466
10.1
09 Nov 2017 16:11:21
Revision:453847Original commit files touched by this commit This port version is marked as vulnerable.
girgen search for other commits by this committer
Update to latest versions of PostgreSQL

The PostgreSQL Global Development Group has released an update to all supported
versions of our database system, including 10.1, 9.6.6, 9.5.10, 9.4.15, 9.3.20,
and 9.2.24. This release fixes three security issues. This release also fixes
issues found in BRIN indexing, logical replication and other bugs reported over
the past three months.

Please note that the CVE-2017-12172 does not affect the FreeBSD port unless you
decided to not use the contrib/startscript instead of the startscript
distributed with the FreeBSD port/package.

Security:	CVE-2017-12172, CVE-2017-15099, CVE-2017-15098
URL:		https://www.postgresql.org/about/news/1801/
10.0_1
15 Oct 2017 17:53:04
Revision:452158Original commit files touched by this commit This port version is marked as vulnerable.
bapt search for other commits by this committer
Recommand psycopg2 over PyGreSQL

Submitted by:	Christoph Moench-Tegeder <cmt@burggraben.net>
10.0_1
08 Oct 2017 16:39:59
Revision:451550Original commit files touched by this commit This port version is marked as vulnerable.
girgen search for other commits by this committer
PostgreSQL has renamed wal as xlog to avoid human errors.

This has caused some binaries to change names. Fix the port so they will be
installed again with their new names.

Noticed by:	VoidChicken@gmail.com
PR:		222864
10.0
05 Oct 2017 13:39:45
Revision:451310Original commit files touched by this commit This port version is marked as vulnerable.
girgen search for other commits by this committer
PostgreSQL 10 Released!

Some highlights:

Logical Replication - A publish/subscribe framework for distributing data
Declarative Table Partitioning - Convenience in dividing your data
Improved Query Parallelism - Quickly conquer your analysis
Quorum Commit for Synchronous Replication - Distribute data with confidence
SCRAM-SHA-256 authentication - Secure your data access

URL:	https://www.postgresql.org/about/news/1786/
10.r1_1
24 Sep 2017 18:58:59
Revision:450532Original commit files touched by this commit This port version is marked as vulnerable.
girgen search for other commits by this committer
Correct default data directory for postgresql 10

...and make sure not to bump portrevision more than necessary.

POINTED OUT BY: Peter Laursen
10.r1
21 Sep 2017 13:43:01
Revision:450258Original commit files touched by this commit This port version is marked as vulnerable.
girgen search for other commits by this committer
Upgrading to RC 1

PostgreSQL 10 RC 1 requires an upgrade from beta 4, or earlier either
using pg_dump / pg_restore or pg_upgrade.

Any bug fixes applied to 9.6 or earlier that also affected 10 are
included in RC 1, as well issues that were reported with Beta 4.

Changes Since Beta 4

PostgreSQL 10 RC 1 contains fixes for issues discovered by users when
testing Beta 4, including:

* Add psql variables showing server version and psql version.
* Several fixes for partitioning
* Several fixes for logical replication
* Several fixes for transition tables
* Fix for query that could end up in an uninterruptible state

Note that some known issues remain unfixed.  Before reporting a bug in
the release candidate, please check the Open Items page.

URL: https://wiki.postgresql.org/wiki/New_in_postgres_10
URL: https://www.postgresql.org/docs/devel/static/release-10.html
10.b3_1
13 Aug 2017 13:52:53
Revision:447889Original commit files touched by this commit This port version is marked as vulnerable.
girgen search for other commits by this committer
Fix broken postgresql10-contrib
10.b3_1
10 Aug 2017 14:23:31
Revision:447680Original commit files touched by this commit This port version is marked as vulnerable.
girgen search for other commits by this committer
Add PostgreSQL-10 to the ports tree

The PostgreSQL Global Development Group announces today that the
third beta release of PostgreSQL 10 is available for download. This
release contains previews of all of the features which will be
available in the final release of version 10, including fixes to many
of the issues found in the second beta.  Users are encouraged to begin
testing their applications against 10 beta3.

URL:	https://www.postgresql.org/about/news/1771/

Number of commits found: 74