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

Two new features

Two two features were added on 2020-05-30:
  1. Repology links - each port now has a link to repology.org. See issue 148 for details.
  2. Ports I maintain report - port maintainers can now subscribe to a daily report of commits to the ports they maintain. See Watch ports I maintain at Report Subscriptions. Details at issue 138
Port details
postgresql94-server PostgreSQL is the most advanced open-source database available anywhere
9.4.26_1 databases on this many watch lists=6 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. 9.4.26Version of this port present on the latest quarterly branch.
Deprecated DEPRECATED: PostgreSQL-9.4 has reached end-of-life
Expiration Date EXPIRATION DATE: 2020-07-24
Maintainer: pgsql@FreeBSD.org search for ports maintained by this maintainer
Port Added: 2014-05-18 14:45:02
Last Update: 2020-05-24 22:16:29
SVN Revision: 536423

People watching this port, also watch: postgresql94-client, postgresql94-contrib, python2, python27, python

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

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

Dependencies
NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
Build dependencies:
  1. gmake>=4.3 : devel/gmake
  2. msgfmt : devel/gettext-tools
Library dependencies:
  1. libpq.so.5 : databases/postgresql94-client
  2. libintl.so : devel/gettext-runtime
This port is required by:
for Build
  1. databases/pg_reorg
  2. databases/postgis23
  3. databases/postgis24
  4. databases/postgresql94-plpython
  5. databases/postgresql94-pltcl

Deleted ports which required this port:

Expand this list of 1 deleted port
  1. databases/pglogical-output*
  2. Collapse this list of deleted ports.
for Run
  1. databases/pg_reorg
  2. databases/postgis23
  3. databases/postgis24
  4. databases/postgresql94-plperl
  5. databases/postgresql94-plpython
  6. databases/postgresql94-pltcl

Deleted ports which required this port:

Expand this list of 1 deleted port
  1. databases/pglogical-output*
  2. 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

USES:

Master Sites:
  1. https://ftp.postgresql.org/pub/source/v9.4.26/
Notes from UPDATING
These upgrade notes are taken from /usr/ports/UPDATING
  • 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.
    
    
Port Moves

Number of commits found: 54

Commit History - (may be incomplete: see SVNWeb link above for full details)
DateByDescription
24 May 2020 21:16:29
Original commit files touched by this commit  9.4.26_1
Revision:536423
girgen search for other commits by this committer
Deprecate PostgreSQL-9.4

Final release was in Fabruary 2020.

WWW:	https://www.postgresql.org/support/versioning/

Also, fix build problems with plperl and plpython  for 9.4
13 Feb 2020 19:14:37
Original commit files touched by this commit  9.4.26
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)
14 Nov 2019 16:24:45
Original commit files touched by this commit  9.4.25
Revision:517600
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  9.4.24
Revision:508835  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  9.4.24
Revision:508390
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.4.23_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.4.23
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.4.22
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.4.21
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
15 Feb 2019 11:02:22
Original commit files touched by this commit  9.4.21
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.4.20_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.4.20_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.4.19
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)
11 May 2018 13:10:52
Original commit files touched by this commit  9.4.18
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.
08 May 2018 19:37:15
Original commit files touched by this commit  9.4.17
Revision:469405 This port version is marked as vulnerable.
sunpoet 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  9.4.17
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.4.16
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.4.15
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/
15 Oct 2017 17:53:04
Original commit files touched by this commit  9.4.14
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>
05 Sep 2017 09:27:11
Original commit files touched by this commit  9.4.14
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.4.13_1
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:15:50
Original commit files touched by this commit  9.4.12_1
Revision:446065 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  9.4.12
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.4.11
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.4.10_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
27 Oct 2016 14:04:56
Original commit files touched by this commit  9.4.10
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.
11 Aug 2016 18:35:31
Original commit files touched by this commit  9.4.9
Revision:420093 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  9.4.9
Revision:420089 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  9.4.8
Revision:417041 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  9.4.8
Revision:415503 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  9.4.8
Revision:415091 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:49:02
Original commit files touched by this commit  9.4.7
Revision:412227 This port version is marked as vulnerable.
girgen search for other commits by this committer
Update PostgreSQL 9.1, 9.2 9.3 and 9.4 to latest versions.

URL:	http://www.postgresql.org/about/news/1656/
13 Feb 2016 22:42:04
Original commit files touched by this commit  9.4.6
Revision:408835 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
08 Oct 2015 21:25:01
Original commit files touched by this commit  9.4.5
Revision:398895 This port version is marked as vulnerable.
girgen search for other commits by this committer
Update PostgreSQL port to latest version.

Two security issues have been fixed in this release which affect users
of specific PostgreSQL features:

CVE-2015-5289: json or jsonb input values constructed from arbitrary
user input can crash the PostgreSQL server and cause a denial of
service.

CVE-2015-5288: The crypt( function included with the optional pgCrypto
extension could be exploited to read a few additional bytes of memory.
No working exploit for this issue has been developed.

This update will also disable SSL renegotiation by default;
previously, it was enabled by default.   SSL renegotiation will be
removed entirely in PostgreSQL versions 9.5 and later.

URL:		http://www.postgresql.org/about/news/1615/
Security:	CVE-2015-5288 CVE-2015-5289
06 Oct 2015 08:47:43
Original commit files touched by this commit  9.4.4_2
Revision:398690 This port version is marked as vulnerable.
girgen search for other commits by this committer
Fix broken XML support.

PR:	ports/202649
22 Jul 2015 22:45:36
Original commit files touched by this commit  9.4.4_1
Revision:392699 This port version is marked as vulnerable.
bapt search for other commits by this committer
Simplify a bit the Makefiles

Use OPTIONS_SUB to automatically PLIST_SUB
Use OPTIONS helpers
22 Jul 2015 21:46:28
Original commit files touched by this commit  9.4.4_1
Revision:392696 This port version is marked as vulnerable.
bapt search for other commits by this committer
Cleanup plist and avoid useless @exec
12 Jun 2015 13:00:50
Original commit files touched by this commit  9.4.4
Revision:389267 This port version is marked as vulnerable.
girgen search for other commits by this committer
Update PostgreSQL to latest versions.

Earlier update releases attempted to fix an issue in PostgreSQL 9.3 and 9.4
with "multixact wraparound", but failed to account for issues doing multixact
cleanup during crash recovery. This could cause servers to be unable to restart
after a crash. As such, all users of 9.3 and 9.4 should apply this update as
soon as possible.

URL:	http://www.postgresql.org/about/news/1592/
05 Jun 2015 14:57:29
Original commit files touched by this commit  9.4.3
Revision:388585 This port version is marked as vulnerable.
girgen search for other commits by this committer
Update PostgreSQL to latest versions.
The update is mostly to fix the file persmission problem described
in the URL below. You might want to wait until next upgrade, depending
on you local configuration.
URL:	http://www.postgresql.org/about/news/1590/
22 May 2015 23:22:20
Original commit files touched by this commit  9.4.2
Revision:387089 This port version is marked as vulnerable.
girgen search for other commits by this committer
Update PostgreSQL ports to latest version.

Data Corruption Fix

For users of PostgreSQL versions 9.3 or 9.4, this release fixes a problem where
the database will fail to protect against "multixact wraparound", resulting in
data corruption or loss. Users with a high transaction rate (1 million or more
per hour) in a database with many foreign keys are especially vulnerable. We
strongly urge all users of 9.4 and 9.3 to update their installations in the
next few days.

Users of versions 9.2 and earlier are not affected by this issue.

Security:	fc38cd83-00b3-11e5-8ebd-0026551a22dc
18 Apr 2015 12:37:23
Original commit files touched by this commit  9.4.1_1
Revision:384223 This port version is marked as vulnerable.
girgen search for other commits by this committer
Chase upcoming update of ICU to 5.5.
05 Apr 2015 09:00:59
Original commit files touched by this commit  9.4.1
Revision:383272 This port version is marked as vulnerable.
girgen search for other commits by this committer
remove redundant cpe markers on the slave ports
03 Apr 2015 12:32:07
Original commit files touched by this commit  9.4.1
Revision:383112 This port version is marked as vulnerable.
robak search for other commits by this committer
databases/postgresql94-server: add CPE information

- Maintainer's timeout (pgsql@FreeBSD.org)

PR:		197489
Submitted by:	Shun <shun.fbsd.pr@dropcut.net>
07 Feb 2015 17:18:49
Original commit files touched by this commit  9.4.1
Revision:378608 This port version is marked as vulnerable.
girgen search for other commits by this committer
In previous commit,
"Revert the change from readline to libedit, and instead make libedit
optional.",
I failed to get the PORTREVISION set correctly. Fixed now.

PR:	ports/197362
05 Feb 2015 22:54:35
Original commit files touched by this commit  9.4.1
Revision:378500 This port version is marked as vulnerable.
girgen search for other commits by this committer
Update PostgreSQL-9.x to latests versions.

This update fixes multiple security issues reported in PostgreSQL over the past
few months. All of these issues require prior authentication, and some require
additional conditions, and as such are not considered generally urgent.
However, users should examine the list of security holes patched below in case
they are particularly vulnerable.

Security:	CVE-2015-0241,CVE-2015-0242,CVE-2015-0243,
		CVE-2015-0244,CVE-2014-8161
18 Dec 2014 15:42:18
Original commit files touched by this commit  9.4.0
Revision:374908 This port version is marked as vulnerable.
girgen search for other commits by this committer
Release PostgreSQL 9.4

Major enhancements in PostgreSQL 9.4 include:

Add jsonb, a more capable and efficient data type for storing JSON data

Add new SQL command ALTER SYSTEM for changing postgresql.conf configuration
file entries

Reduce lock strength for some ALTER TABLE commands

Allow materialized views to be refreshed without blocking concurrent reads

Add support for logical decoding of WAL data, to allow database changes to be
streamed out in a customizable format

Allow background worker processes to be dynamically registered, started and
terminated The above items are explained in more detail in the sections below.

URL:	http://www.postgresql.org/docs/9.4/static/release-9-4.html
19 Nov 2014 16:09:15
Original commit files touched by this commit  9.4.r1
Revision:372796 This port version is marked as vulnerable.
girgen search for other commits by this committer
Update PostgreSQL 9.4 to release candidate 1.
09 Oct 2014 15:20:53
Original commit files touched by this commit  9.4.b3
Revision:370540 This port version is marked as vulnerable.
girgen search for other commits by this committer
Update to PostgreSQL 9.4 beta3
25 Aug 2014 16:44:08
Original commit files touched by this commit  9.4.b1_1
Revision:366094 This port version is marked as vulnerable.
antoine search for other commits by this committer
Remove some duplicate lines from plist (or duplicate plist)

Reported by:	pkg developer mode
02 Aug 2014 07:01:54
Original commit files touched by this commit  9.4.b1_1
Revision:363792 This port version is marked as vulnerable.
mva search for other commits by this committer
- Unbreak builds after the lang/python27 update (r363790)

Exp-run:	192242, 192244
09 Jun 2014 21:57:43
Original commit files touched by this commit  9.4.b1_1
Revision:357209 This port version is marked as vulnerable.
girgen search for other commits by this committer
Prepare for upcoming ICU-5.3 upgrade.
31 May 2014 16:37:58
Original commit files touched by this commit  9.4.b1_1
Revision:355995 This port version is marked as vulnerable.
ak search for other commits by this committer
- Fix various distinfo errors
- Remove unused USE_* knobs
- Convert USE_TWISTED_RUN to USES
- Remove empty lines after .include <bsd.port.mk>

Approved by:	portmgr (antoine)
20 May 2014 21:58:23
Original commit files touched by this commit  9.4.b1_1
Revision:354693 This port version is marked as vulnerable.
girgen search for other commits by this committer
fix broken plist
18 May 2014 14:44:53
Original commit files touched by this commit  9.4.b1
Revision:354425 This port version is marked as vulnerable.
girgen search for other commits by this committer
The PostgreSQL Global Development Group announced that the first beta
release of PostgreSQL 9.4, the latest version of the world's leading
open source database, is available today.  This beta contains previews
of all of the features which will be available in version 9.4, and is
ready for testing by the worldwide PostgreSQL community.  Please
download, test, and report what you find.

Major Features
--------------

The new major features available for testing in this beta include:

* JSONB: 9.4 includes the new JSONB "binary JSON" type. This new
  storage format for document data is higher-performance, and comes with
  indexing, functions and operators for manipulating JSON data.
* Replication: The new Data Change Streaming API allows decoding and
  transformation of the replication stream.  This lays the foundation
  for new replication tools that support high-speed and more flexible
  replication and scale-out solutions.
* Materialized Views with "Refresh Concurrently", which permit
  fast-response background summary reports for complex data.
* ALTER SYSTEM SET, which enables modifications to postgresql.conf
  from the SQL command line and from remote clients, easing
  administration tasks.

Number of commits found: 54

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
unbound*Jul 10
mybbJul 09
sqlite3*Jul 09
rubygem-kramdownJul 08
gitlab-ceJul 07
mbedtlsJul 07
anydeskJul 04
dbusJul 03
py-matrix-synapseJul 03
coturnJul 02
gitlab-ceJul 02
powerdns-recursorJul 02
samba410Jul 02
samba411Jul 02
drupal7Jul 01

18 vulnerabilities affecting 82 ports have been reported in the past 14 days

* - modified, not new

All vulnerabilities

Last updated:
2020-07-10 06:33:27


Ports
Home
Categories
Deleted ports
Sanity Test Failures
Newsfeeds

Statistics
Graphs
NEW Graphs (Javascript)
Traffic

Calculated hourly:
Port count 39941
Broken 79
Deprecated 587
Ignore 310
Forbidden 5
Restricted 146
No CDROM 76
Vulnerable 19
Expired 4
Set to expire 557
Interactive 0
new 24 hours 6
new 48 hours11
new 7 days29
new fortnight58
new month143

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