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

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. msgfmt : devel/gettext-tools
Library dependencies:
  1. libpq.so.5 : databases/postgresql95-client
  2. libintl.so : devel/gettext-runtime
NOTE: dependencies for deleted ports are notoriously suspect
This port is required by:
for Build

Deleted ports which required this port:

Expand this list of 12 deleted ports
  1. databases/glom*
  2. databases/pg_reorg*
  3. databases/pg_rman*
  4. databases/pg_statsinfo*
  5. databases/pgespresso*
  6. databases/postgis20*
  7. databases/postgis21*
  8. databases/postgis22*
  9. databases/postgis23*
  10. databases/postgresql-repmgr2*
  11. databases/postgresql95-plpython*
  12. databases/postgresql95-pltcl*
  13. Collapse this list of deleted ports.
for Run

Deleted ports which required this port:

Expand this list of 13 deleted ports
  1. databases/glom*
  2. databases/pg_reorg*
  3. databases/pg_rman*
  4. databases/pg_statsinfo*
  5. databases/pgespresso*
  6. databases/postgis20*
  7. databases/postgis21*
  8. databases/postgis22*
  9. databases/postgis23*
  10. databases/postgresql-repmgr2*
  11. databases/postgresql95-plperl*
  12. databases/postgresql95-plpython*
  13. databases/postgresql95-pltcl*
  14. Collapse this list of deleted ports.
* - deleted ports are only shown under the This port is required by section. It was harder to do for the Required section. Perhaps later...

Configuration Options:
Options name:

USES:

pkg-message:
If installing:
Master Sites:
Expand this list (1 items)
Collapse this list.
  1. https://ftp.postgresql.org/pub/source/v9.5.25/
Collapse this list.
Port Moves
  • port deleted on 2021-06-13
    REASON: Has expired: PostgreSQL-9.5 has reached end-of-life
  • port moved here from databases/postgresql94-server on 2020-07-24
    REASON: Has expired: PostgreSQL-9.4 has reached end-of-life

Number of commits found: 47

Commit History - (may be incomplete: see SVNWeb link above for full details)
DateByDescription
13 Jun 2021 10:50:22
 files touched by this commit commit hash:a3da90c5e4f183d6a61b55ac6da01974ab575ed1  9.5.25
rene search for other commits by this committer
*/*: Remove expired ports:

2021-06-13 databases/postgresql95-client: PostgreSQL-9.5 has reached end-of-life
2021-06-13 databases/postgresql95-contrib: PostgreSQL-9.5 has reached
end-of-life
2021-06-13 databases/postgresql95-docs: PostgreSQL-9.5 has reached end-of-life
2021-06-13 databases/postgresql95-pgtcl: PostgreSQL-9.5 has reached end-of-life
2021-06-13 databases/postgresql95-plperl: PostgreSQL-9.5 has reached end-of-life
2021-06-13 databases/postgresql95-plpython: PostgreSQL-9.5 has reached
end-of-life
2021-06-13 databases/postgresql95-pltcl: PostgreSQL-9.5 has reached end-of-life
2021-06-13 databases/postgresql95-server: PostgreSQL-9.5 has reached end-of-life
databases/pg_reorg: abandonware only for PostgreSQL 9.5
databases/pgespresso: functionality part of PostgreSQL 9.6 and later
20 May 2021 14:38:55
 files touched by this commit commit hash:fccc45e5ff4a8aea150005196c0d4f2cbaeed5db  9.5.25
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.
15 May 2021 09:12:17
 files touched by this commit commit hash:ab83f2b4bb78a718efa5c43247ba1e1d207f99b6  9.5.25
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)
15 May 2021 09:12:15
 files touched by this commit commit hash:35c1aedccf41dcfad42eec0ef3a86f89c8472500  9.5.25
girgen search for other commits by this committer
databases/postgresql95-*: expire this version

It is end-of-life upstreams. Please update to a later version.
06 Apr 2021 14:31:13
 files touched by this commit commit hash:135fdeebb99c3569e42d8162b265e15d29bd937d  9.5.25
mat search for other commits by this committer
all: Remove all other $FreeBSD keywords.
06 Apr 2021 14:31:07
 files touched by this commit commit hash:305f148f482daf30dcf728039d03d019f88344eb  9.5.25
mat search for other commits by this committer
Remove # $FreeBSD$ from Makefiles.
11 Feb 2021 14:34:02
Original commit files touched by this commit Revision:564956  9.5.25
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
13 Nov 2020 19:27:04
Original commit files touched by this commit Revision:555043  9.5.24
girgen search for other commits by this committer
PostgreSQL 13.1, 12.5, 11.10, 10.15, 9.6.20 and 9.5.24 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, 9.6.20 and
9.5.24.  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
24 Sep 2020 13:33:10
Original commit files touched by this commit Revision:549921  9.5.23
girgen search for other commits by this committer
Welcome PostgreSQL 13

Release notes:	https://www.postgresql.org/about/news/2077/
13 Aug 2020 13:45:03
Original commit files touched by this commit Revision:544810  9.5.23
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)
17 May 2020 20:37:04
Original commit files touched by this commit Revision:535676  9.5.22
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]
13 Feb 2020 19:14:37
Original commit files touched by this commit Revision:526063  9.5.21
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)
14 Nov 2019 16:24:45
Original commit files touched by this commit Revision:517600  9.5.20
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/
13 Aug 2019 16:01:59
Original commit files touched by this commit Revision:508835  9.5.19  Sanity Test Failure
mat search for other commits by this committer
Convert to UCL & cleanup pkg-message (categories d)
08 Aug 2019 15:33:03
Original commit files touched by this commit Revision:508390  9.5.19
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)
26 Jul 2019 20:46:57
Original commit files touched by this commit Revision:507372  9.5.18_1 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
27 Jun 2019 21:28:00
Original commit files touched by this commit Revision:505245  9.5.18 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
09 May 2019 22:32:11
Original commit files touched by this commit Revision:501149  9.5.17 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)
25 Apr 2019 18:34:42
Original commit files touched by this commit Revision:500060  9.5.16 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
15 Feb 2019 11:02:22
Original commit files touched by this commit Revision:492989  9.5.16 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)
12 Dec 2018 01:35:36
Original commit files touched by this commit Revision:487272  9.5.15_2 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
08 Nov 2018 23:21:19
Original commit files touched by this commit Revision:484488  9.5.15_1 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 Aug 2018 09:25:20
Original commit files touched by this commit Revision:476819  9.5.14 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)
11 May 2018 13:10:52
Original commit files touched by this commit Revision:469638  9.5.13 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.
06 May 2018 09:33:58
Original commit files touched by this commit Revision:469186  9.5.12 This port version is marked as vulnerable.
amdmi3 search for other commits by this committer
- Update WWW

Approved by:	portmgr blanket
01 Mar 2018 15:10:17
Original commit files touched by this commit Revision:463327  9.5.12 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
08 Feb 2018 17:38:36
Original commit files touched by this commit Revision:461251  9.5.11 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)
09 Nov 2017 16:11:21
Original commit files touched by this commit Revision:453847  9.5.10 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/
15 Oct 2017 17:53:04
Original commit files touched by this commit Revision:452158  9.5.9 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>
05 Sep 2017 09:27:11
Original commit files touched by this commit Revision:449278  9.5.9 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 9.6.5, 9.5.9,
9.4.14, 9.3.19, and 9.2.23.

This release includes fixes that prevent a crash in pg_restore when
using parallel mode. It also patches over a few other bugs reported
since the last releases in August.

Additionally, in 9.4.14 only, there is a fix to an issue with walsenders
preventing primary-server shutdown unless immediate shutdown mode is used.

Users should plan to update at the next convenient downtime.

Bug Fixes and Improvements
(Only the first 15 lines of the commit message are shown above View all of this commit message)
10 Aug 2017 14:21:21
Original commit files touched by this commit Revision:447678  9.5.8_1 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 9.6.4, 9.5.8,
9.4.13, 9.3.18, and 9.2.22. This release fixes three security issues.
It also patches over 50 other bugs reported over the last three months.
Users who are affected by the below security issues should update as
soon as possible.  Users affected by CVE-2017-7547
(https://access.redhat.com/security/cve/CVE-2017-7547) will need to
perform additional steps after upgrading to resolve the issue.  Other
users should plan to update at the next convenient downtime.

URL:		https://www.postgresql.org/about/news/1772/
Security:	CVE-2017-7546, CVE-2017-7547, CVE-2017-7548
17 Jul 2017 11:15:50
Original commit files touched by this commit Revision:446065  9.5.7_1 This port version is marked as vulnerable.
amdmi3 search for other commits by this committer
- Include pg_regress to all postgresql*-client ports, to allow running
regression tests for postgresql extensions

PR:		217874
Approved by:	maintainer timeout (pgsql, 4 months)
11 May 2017 14:28:22
Original commit files touched by this commit Revision:440628  9.5.7 This port version is marked as vulnerable.
girgen search for other commits by this committer
PostgreSQL security updates

The PostgreSQL Global Development Group has released an update to all supported
versions of our database system, including 9.6.3, 9.5.7, 9.4.12, 9.3.17, and
9.2.21. This release fixes three security issues. It also patches a number of
other bugs reported over the last three months. Users who use the PGREQUIRESSL
environment variable to control connections, and users who rely on security
isolation between database users when using foreign servers, should update as
soon as possible. Other users should plan to update at the next convenient
downtime.

URL:    https://www.postgresql.org/about/news/1746/
Security:       CVE-2017-7484, CVE-2017-7485, CVE-2017-7486

Also modify rcorder and let sshd start before PostgreSQL, so any problems
during startup can be reviewed promplty from an ssh login.
09 Feb 2017 15:22:44
Original commit files touched by this commit Revision:433738  9.5.6 This port version is marked as vulnerable.
girgen search for other commits by this committer
PostgreSQL 9.6.2, 9.5.6, 9.4.11, 9.3.16 and 9.2.20 released!

The PostgreSQL Global Development Group has released an update to all supported
versions of our database system, including 9.6.2, 9.5.6, 9.4.11, 9.3.16, and
9.2.20. This release includes fixes that prevent data corruption issues in
index builds and in certain write-ahead-log replay situations, which are
detailed below. It also patches over 75 other bugs reported over the last three
months.

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

Build corruption with CREATE INDEX CONCURRENTLY

There existed a race condition if CREATE INDEX CONCURRENTLY was called on a
column that had not been indexed before, then rows that were updated by
transactions running at the same time as the CREATE INDEX CONCURRENTLY command
could have been indexed incorrectly.

If you suspect this may have happened, the most reliable solution is to rebuild
affected indexes after installing this update.

This issue is present in the 9.2, 9.3, 9.4, 9.5, and 9.6 series of PostgreSQL.

URL	https://www.postgresql.org/about/news/1733/
07 Jan 2017 21:42:28
Original commit files touched by this commit Revision:430839  9.5.5_1 This port version is marked as vulnerable.
sunpoet search for other commits by this committer
Add more PLIST_SUB to Mk/Uses/python.mk

- Add PYTHON_PYOEXTENSION and PYTHON_SUFFIX
- Add PYTHON2 and PYTHON3
- Respect PYTHON_VERSION
- Rename PYOEXTENSION to PYTHON_PYOEXTENSION

This change would help:
- Build databases/postgresql*-plpython with Python 3
  (It has PLIST issue since bsd.python.mk to Uses/python.mk transition)
- Simplify Makefile

PR:		205807
Differential Revision:	https://reviews.FreeBSD.org/D4758
Exp-run by:	antoine
27 Oct 2016 14:04:56
Original commit files touched by this commit Revision:424765  9.5.5 This port version is marked as vulnerable.
girgen search for other commits by this committer
Update PostgreSQL to latest versions.

The PostgreSQL Global Development Group has released an update to all supported
versions of our database system, including 9.6.1, 9.5.5, 9.4.10, 9.3.15,
9.2.19, and 9.1.24.

This release fixes two issues that can cause data corruption, which are
described in more detail below. It also patches a number of other bugs reported
over the last three months. The project urges users to apply this update at the
next possible downtime.
11 Aug 2016 18:35:31
Original commit files touched by this commit Revision:420093  9.5.4 This port version is marked as vulnerable.
ohauer search for other commits by this committer
- fix sizes
- s/USE_OPENSSL/USES=ssl/

assumed OK for commit ~1h after first notify about wrong sizes in distinfo
11 Aug 2016 16:39:40
Original commit files touched by this commit Revision:420089  9.5.4 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 9.5.4, 9.4.9, 9.3.14, 9.2.18 and
9.1.23. This release fixes two security issues. It also patches a number of
other bugs reported over the last three months. Users who rely on security
isolation between database users should update as soon as possible. Other users
should plan to update at the next convenient downtime.

If you are using the ICU patch, please consult UPDATING.

Improve periodic cleanup, suggested by claudius (at) ambtec.de. [1]

PR:		210941 [1]
Security:	CVE-2016-5423, CVE-2016-5424
17 Jun 2016 23:28:05
Original commit files touched by this commit Revision:417041  9.5.3 This port version is marked as vulnerable.
mat search for other commits by this committer
Rename all files containing a : in their filename.

While there, run make makepatch on affected ports, and rename patches
accordingly.

Sponsored by:	Absolight
19 May 2016 11:09:14
Original commit files touched by this commit Revision:415503  9.5.3 This port version is marked as vulnerable.
amdmi3 search for other commits by this committer
- Fix trailing whitespace in pkg-messages

Approved by:	portmgr blanket
12 May 2016 22:36:10
Original commit files touched by this commit Revision:415091  9.5.3 This port version is marked as vulnerable.
girgen search for other commits by this committer
Update PostgreSQL to latest versions

URL:	http://www.postgresql.org/docs/9.5/static/release-9-5-3.html
31 Mar 2016 14:46:39
Original commit files touched by this commit Revision:412226  9.5.2 This port version is marked as vulnerable.
girgen search for other commits by this committer
Update PostgreSQL 9.5 to latest version

Security Fixes for RLS, BRIN
----------------------------

This release closes security hole CVE-2016-2193
(https://access.redhat.com/security/cve/CVE-2016-2193), where a query plan
might get reused for more than one ROLE in the same session.  This could cause
the wrong set of Row Level Security (RLS) policies to be used for the query.

The update also fixes CVE-2016-3065
(https://access.redhat.com/security/cve/CVE-2016-3065), a server crash bug
triggered by using `pageinspect` with BRIN index pages.  Since an attacker
might be able to expose a few bytes of server memory, this crash is being
treated as a security issue.
(Only the first 15 lines of the commit message are shown above View all of this commit message)
13 Feb 2016 22:42:04
Original commit files touched by this commit Revision:408835  9.5.1 This port version is marked as vulnerable.
girgen search for other commits by this committer
Update PostgreSQL to latest versions.

Security Fixes for Regular Expressions, PL/Java

This release closes security hole CVE-2016-0773, an issue with regular
expression (regex) parsing. Prior code allowed users to pass in expressions
which included out-of-range Unicode characters, triggering a backend crash.
This issue is critical for PostgreSQL systems with untrusted users or which
generate regexes based on user input.

The update also fixes CVE-2016-0766, a privilege escalation issue for users of
PL/Java.  Certain custom configuration settings (GUCS) for PL/Java will now be
modifiable only by the database superuser

URL:		http://www.postgresql.org/about/news/1644/
Security:	CVE-2016-0773, CVE-2016-0766
30 Jan 2016 10:40:33
Original commit files touched by this commit Revision:407518  9.5.0_2 This port version is marked as vulnerable.
girgen search for other commits by this committer
Add missing pg_rewind

Pointed out by:	Nat Howard
PR:		206750
13 Jan 2016 10:36:22
Original commit files touched by this commit Revision:406034  9.5.0_1 This port version is marked as vulnerable.
girgen search for other commits by this committer
Some binaries where moved from contrib to base in 9.5, like pgbench and
pg_upgrade. Other where added in 9.5, but the port failed to install them.
Make sure they are properly installed by the correct port (-client or -server)
[1]

Remove unused and hence confusing OSSP_UUID parameters from Makefile [2]

Add options to allow user to be set for the backup script in periodic.
Add this option only to 9.5 for now. It will be updated to other servers at
next regular patch release. [3]

The path to perl in hard coded into pgxs/src/Makefile.global which is
then installed. Hence, we must depend on perl when that file is installed.

Noticed by:	Paul Guyot [1]
PR:		192387 [2]
PR:		172110 [3]
PR:		206046 [4]
07 Jan 2016 21:37:58
Original commit files touched by this commit Revision:405487  9.5.0 This port version is marked as vulnerable.
antoine search for other commits by this committer
Fix probable typo (and PKGNAME collision)
While here, fix plist
07 Jan 2016 19:58:47
Original commit files touched by this commit Revision:405482  9.5.0 This port version is marked as vulnerable.
girgen search for other commits by this committer
The PostgreSQL Global Development Group announces the
release of PostgreSQL 9.5.

This release adds UPSERT capability, Row Level Security,
and multiple Big Data features, which will broaden the
user base for the world's most advanced database.
With these new capabilities, PostgreSQL will be
the best choice for even more applications for startups,
large corporations, and government agencies.

Release Notes:
http://www.postgresql.org/docs/current/static/release-9-5.html

What's New in 9.5:
https://wiki.postgresql.org/wiki/What%27s_new_in_PostgreSQL_9.5

Number of commits found: 47