notbugAs an Amazon Associate I earn from qualifying purchases.
Want a good read? Try FreeBSD Mastery: Jails (IT Mastery Book 15)

Why was the website so slow for so long?

The cause of the slowdown was a change to the ZFS dataset. In conjunction with the database server, very little caching was being done. This combination resulted in increased disk I/O as the system churned through the database. Details in the blog post which outlines the various things which changed. Many graphs.

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

Slave ports
  1. databases/postgresql96-client
  2. databases/postgresql96-contrib
  3. databases/postgresql96-docs
  4. databases/postgresql96-plperl
  5. databases/postgresql96-plpython
  6. databases/postgresql96-pltcl

Dependencies
NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
Build dependencies:
  1. gmake : devel/gmake
  2. msgfmt : devel/gettext-tools
  3. autoconf>=2.69 : devel/autoconf
  4. automake>=1.16.1 : devel/automake
Library dependencies:
  1. libicudata.so : devel/icu
  2. libpq.so.5 : databases/postgresql96-client
  3. libintl.so : devel/gettext-runtime
This port is required by:
for Build
  1. databases/postgresql96-plpython
  2. databases/postgresql96-pltcl
for Run
  1. databases/postgresql96-plperl
  2. databases/postgresql96-plpython
  3. databases/postgresql96-pltcl

Configuration Options

USES:

Master Sites:
  1. https://ftp.postgresql.org/pub/source/v9.6.17/
Notes from UPDATING
These upgrade notes are taken from /usr/ports/UPDATING
  • 2016-09-05
    Affects: users of databases/postgresql96-server
    Author: girgen@FreeBSD.org
    Reason: 
      The default unix user used by the PostgreSQL daemon has changed to
      `postgres' to reflect the long time upstream's convention. Any scripts
      you have using the old `pgsql' unix user should be modified when upgrading to
      PostgreSQL version 9.6. Older versions of PostgreSQL will continue using
      `pgsql' until their end-of-life.
    
      For users with UTF-8 locales in the database: The ICU patch is *activated by
      default* for the PostgreSQL-9.6 server. For previous versions it was optional
      and default off, but this has changed. Please read the entry here below from
      20160811 and understand the consequences of changing between ICU and system
      locale for database collation (short version: don't). pg_upgrade requires the
      collation method to be the same (or a reindex), while pg_dump/restore does not.
    
      Also, the default home directory for the postgres user is now
      /var/db/postgres, and the default data directory for PostgreSQL 9.6 is
      /var/db/postgres/data96.
    
    
  • 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.
    
    

Number of commits found: 42

Commit History - (may be incomplete: see SVNWeb link above for full details)
DateByDescription
13 Mar 2020 09:54:52
Original commit files touched by this commit  9.6.17_1
Revision:528344
jbeich search for other commits by this committer
Fix up PORTREVISION style after "portedit bump-revision"
13 Mar 2020 09:47:17
Original commit files touched by this commit  9.6.17_1
Revision:528343
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/
13 Feb 2020 19:14:37
Original commit files touched by this commit  9.6.17
Revision:526063
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)
30 Dec 2019 18:04:40
Original commit files touched by this commit  9.6.16
Revision:521556 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)
14 Nov 2019 16:24:45
Original commit files touched by this commit  9.6.16
Revision:517600 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/
03 Oct 2019 20:35:30
Original commit files touched by this commit  9.6.15_1
Revision:513733 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/
13 Aug 2019 16:01:59
Original commit files touched by this commit  9.6.15
Revision:508835  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)
08 Aug 2019 15:33:03
Original commit files touched by this commit  9.6.15
Revision:508390 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)
26 Jul 2019 20:46:57
Original commit files touched by this commit  9.6.14_1
Revision:507372 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  9.6.14
Revision:505245 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  9.6.13
Revision:501149 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  9.6.12_1
Revision:500060 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
27 Mar 2019 21:11:09
Original commit files touched by this commit  9.6.12_1
Revision:496981 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
15 Feb 2019 11:02:22
Original commit files touched by this commit  9.6.12
Revision:492989 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  9.6.11_2
Revision:487272 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  9.6.11_1
Revision:484488 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  9.6.10
Revision:476819 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)
29 Jun 2018 14:22:11
Original commit files touched by this commit  9.6.9_1
Revision:473551 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)
11 May 2018 13:10:52
Original commit files touched by this commit  9.6.9
Revision:469638 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.
07 May 2018 19:21:10
Original commit files touched by this commit  9.6.8_1
Revision:469324 This port version is marked as vulnerable.
sunpoet search for other commits by this committer
Update WWW

Approved by:	portmgr (blanket)
06 Apr 2018 15:53:17
Original commit files touched by this commit  9.6.8_1
Revision:466648 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)
01 Mar 2018 15:10:17
Original commit files touched by this commit  9.6.8
Revision:463327 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  9.6.7
Revision:461251 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  9.6.6
Revision:453847 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/
09 Nov 2017 02:31:48
Original commit files touched by this commit  9.6.5_2
Revision:453790 This port version is marked as vulnerable.
jbeich search for other commits by this committer
devel/icu: update to 60.1

Changes:	http://site.icu-project.org/download/60
ABI:		https://abi-laboratory.pro/tracker/timeline/icu4c/
PR:		223373
Exp-run by:	antoine
15 Oct 2017 17:53:04
Original commit files touched by this commit  9.6.5_1
Revision:452158 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>
25 Sep 2017 00:02:36
Original commit files touched by this commit  9.6.5_1
Revision:450556  Sanity Test Failure This port version is marked as vulnerable.
jbeich search for other commits by this committer
devel/icu: update to 59.1

- Temporarily keep C++98 working in consumers for Clang's default -std=

Changes:	http://site.icu-project.org/download/59
PR:		218788
Submitted by:	takefu@airport.fm, dcarmich@dcarmichael.net (early version)
Exp-run by:	antoine
05 Sep 2017 09:27:11
Original commit files touched by this commit  9.6.5
Revision:449278 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  9.6.4_3
Revision:447678 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:14:10
Original commit files touched by this commit  9.6.3_3
Revision:446064 This port version is marked as vulnerable.
amdmi3 search for other commits by this committer
- Add missing file to plist

PR:		217874
Approved by:	maintainer timeout (postgres, 2 weeks)
29 Jun 2017 12:04:18
Original commit files touched by this commit  9.6.3_1
Revision:444644 This port version is marked as vulnerable.
amdmi3 search for other commits by this committer
- Include pg_regress to postgresql96-client, to allow running regression tests
for postgresql extensions

PR:		217874
Approved by:	maintainer timeout (3 months)
11 May 2017 14:28:22
Original commit files touched by this commit  9.6.3
Revision:440628 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  9.6.2
Revision:433738 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  9.6.1_1
Revision:430839 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
05 Jan 2017 16:29:32
Original commit files touched by this commit  9.6.1_1
Revision:430644 This port version is marked as vulnerable.
mat search for other commits by this committer
Long ago, I removed all the : in file names in the ports tree.

One had crept back.

Sponsored by:	Absolight
27 Oct 2016 14:04:56
Original commit files touched by this commit  9.6.1
Revision:424765 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.
29 Sep 2016 13:37:00
Original commit files touched by this commit  9.6.0_1
Revision:422916 This port version is marked as vulnerable.
girgen search for other commits by this committer
PostgreSQL 9.6, the latest version of the world's leading open source
database, was released today by the PostgreSQL Global Development
Group.  This release will allow users to both scale up and scale out
high performance database workloads.  New features include parallel
query, synchronous replication improvements, phrase search, and
improvements to performance and usability, as well as many more
features.
24 Sep 2016 11:06:57
Original commit files touched by this commit  9.6.r1_4
Revision:422711 This port version is marked as vulnerable.
tijl search for other commits by this committer
- Update devel/icu to 57.1.
- Clean up the Makefile.
- Follow some upstream recommendations (--with-data-packaging=archive,
  --disable-renaming, -DICU_NO_USER_DATA_OVERRIDE).
- Patch makefiles to install static libraries with INSTALL_DATA so they
  aren't stripped.
- Patch config/mh-bsd-gcc to sync with config/mh-linux-gcc.
- Fix endianness detection in ICU.  The code wanted to use BYTE_ORDER
  defined in machine/endian.h, but this isn't visible because ICU is
  compiled with _XOPEN_SOURCE.  Patch the code to use _BYTE_ORDER instead.
- Compile ICU with C++11 compiler to enable move constructors.
- Patch ICU to fix a problem with atomics in the case of a C++11 compiler
  without C++11 header <atomic> (like Clang on FreeBSD 9).
- Bump all ports that depend on it due to library version change.
- Add USES=compiler:c++0x to some ports that pick up -std=c++0x from ICU
  pkgconfig files.
- Add USES=compiler:c++11-lib to graphics/libcdr01 because it also needs
  a C++11 runtime library now.  Add this to all ports that depend on it
  so their executables load the right libstdc++.so on FreeBSD 9.

PR:		205120
Exp-run by:	antoine
Approved by:	portmgr (antoine)
21 Sep 2016 09:02:59
Original commit files touched by this commit  9.6.r1_3
Revision:422551 This port version is marked as vulnerable.
girgen search for other commits by this committer
We should tell initdb which user we want as DBA
07 Sep 2016 01:57:44
Original commit files touched by this commit  9.6.r1_2
Revision:421475 This port version is marked as vulnerable.
girgen search for other commits by this committer
Fix plist problem for postgresql-9.6 [1]

Fix spelling while here [2]

Pointed out by:	matthew [1], bcr [2]
Pointy hat to:	girgen
05 Sep 2016 11:59:33
Original commit files touched by this commit  9.6.r1_1
Revision:421361 This port version is marked as vulnerable.
girgen search for other commits by this committer
Fix broken package name for PostgreSQL 9.6 RC1
Fix bad pkg-plist for postgresql 9.6 server
05 Sep 2016 11:15:29
Original commit files touched by this commit  9.6.r1
Revision:421360 This port version is marked as vulnerable.
girgen search for other commits by this committer
Add PostgreSQL-9.6 RC1

Please read the entry from 20160905 in UPDATING:

daemon user has changed to `postgres'
ICU is default on

Number of commits found: 42

Login
User Login
Create account

Servers and bandwidth provided by
New York Internet, iXsystems, and RootBSD

This site
What is FreshPorts?
About the authors
Issues
FAQ
How big is it?
The latest upgrade!
Privacy
Blog
Contact

Search
Enter Keywords:
 
more...

Latest Vulnerabilities
apache24Apr 02
cactiApr 02
chromiumApr 02
haproxyApr 02
haproxy18Apr 02
haproxy19Apr 02
haproxy21Apr 02
rubygem-json*Apr 02
gnutlsMar 31
postgresql10-serverMar 29
postgresql11-serverMar 29
postgresql12-serverMar 29
postgresql96-serverMar 29
gitlab-ceMar 26
jenkinsMar 25

12 vulnerabilities affecting 110 ports have been reported in the past 14 days

* - modified, not new

All vulnerabilities

Last updated:
2020-04-02 20:42:28


Ports
Home
Categories
Deleted ports
Sanity Test Failures
Newsfeeds

Statistics
Graphs
NEW Graphs (Javascript)
Traffic

Calculated hourly:
Port count 39073
Broken 588
Deprecated 1065
Ignore 859
Forbidden 5
Restricted 151
No CDROM 72
Vulnerable 22
Expired 2
Set to expire 1033
Interactive 0
new 24 hours 6
new 48 hours15
new 7 days59
new fortnight113
new month184

Servers and bandwidth provided by
New York Internet, iXsystems, and RootBSD
Valid HTML, CSS, and RSS.
Copyright © 2000-2020 Dan Langille. All rights reserved.