PostgreSQL wiki - User contributions [en]

PDXPUG Agenda

2013-05-23T22:51:09Z

Gabrielle:

We'll try keeping our agenda here for a little while...

= Standard Agenda =

== Welcome to the space ==
* thanks to Iovation for hosting us
* wireless login
* restrooms
* after meeting social hour TBD, probably Huber's

== Announcements/wisecracks ==
* pdxpug twitter feed
* past events
** PgCon - how was it?
* upcoming events
** OSB (ticket raffle + discount code)
** OSCON
*** booth signup is out
*** beering venue will be...
*** we will have t-shirts for booth volunteers, but you have to sign up in advance so we can order them.
** PgOpen
* other business
** PDXPUG + PgUS
** patches reviewed/accepted
** jobs!
*** who has a new one? Share your excitement!
*** have an opening?
*** looking for something new to do?
** books

== Intros ==
* silly question + your name

PDXPUG Agenda

2013-05-23T22:49:18Z

Gabrielle: /* Announcements/wisecracks */

We'll try keeping our agenda here for a little while...

= Standard Agenda =

== Welcome to the space ==
* thanks to Iovation for hosting us
* wireless login
* restrooms
* after meeting social hour TBD, probably Huber's

== Announcements/wisecracks ==
* pdxpug twitter feed
* past events
* upcoming events
** PgCon
** OSB (ticket raffle + discount code)
** OSCON (more about that later)
** PgOpen
* other business
** PDXPUG + PgUS
** patches reviewed/accepted
** jobs!
*** who has a new one? Share your excitement!
*** have an opening?
*** looking for something new to do?
** books

=== OSCON ===
* booth
* BOF/beering

== Intros ==
* silly question + your name

PDXPUG Agenda

2013-05-15T17:59:55Z

Gabrielle: /* Announcements/wisecracks */

We'll try keeping our agenda here for a little while...

= Standard Agenda =

== Welcome to the space ==
* thanks to Iovation for hosting us
* wireless login
* restrooms
* after meeting social hour TBD, probably Huber's

== Announcements/wisecracks ==
* pdxpug twitter feed
* past events
* upcoming events
** PgCon
** OSB (ticket raffle + discount code)
** OSCON (more about that later)
** PgOpen
* other business
** patches reviewed/accepted
** jobs!
*** who has a new one? Share your excitement!
*** have an opening?
*** looking for something new to do?
** books

=== OSCON ===
* booth
* BOF/beering

== Intros ==
* silly question + your name

PDXPUG Agenda

2013-05-14T03:26:25Z

Gabrielle: /* Announcements/wisecracks */

PDXPUG Agenda

2013-05-03T02:28:14Z

Gabrielle:

PDXPUG Agenda

2013-05-03T02:27:24Z

Gabrielle: Add the PDXPUG standard agenda

Pdxpug

2013-05-03T02:21:09Z

Gabrielle: add link to our agenda

Page to hold PDXPUG-specific files & such.

== Logo ==
Small version; not sure where the large one is

[[Image:pdxpug_logo.jpg|100|JPG]]

[[Media:pdxpug_logo.gif|or grab the GIF version]]

== Poster ==
[[Media:pdxpug_poster.pdf|PDF]]

== Flyers ==

* PGXPUG PgDay after-party flier (2011): Front [[Media:Party_invite_front.odt‎|ODT]] | Back [[Media:Party_invite_back.odt‎|ODT]]. You'll need the following fonts: Strait, monofur.

== Agenda ==
[[PDXPUG Agenda]]

== Speaker Info ==

[[File:PDXPUGSpeakerInfo.odt]]

== Talks ==
[[PDXPUG Talks]]

[[Category:Users group]]

Events

2013-03-28T00:48:57Z

Gabrielle: /* PostgreSQL Events */

== PostgreSQL Events ==

Most PostgreSQL-specific events are tracked on the [http://www.postgresql.org/about/eventarchive PostgreSQL Events] page. This is a listing of events at which we expect, or would like to have, a PostgreSQL presence. Please keep the events in order by starting date and follow the existing examples. Please also tag the events with the MediaWiki "PostgreSQL Events" category. If you are going to be organizing a PostgreSQL booth, please adhere to [[BoothPolicies]]. PostgreSQL Europe conference coordination [[PGUG EU Conference Coordination|is here]]. Conference for China user group [[Pg_envent_cn| is here]].

{| border="1"
|+
|- style="background:Khaki;"
'''Upcoming PostgreSQL Events Listing'''
| '''Event''' || '''Web Page''' || '''Date''' || '''Country''' || '''City''' || '''Activities'''
|-
| [[PGDay_FOSDEM_2013|PGDay FOSDEM 2013]] || [http://fosdem2013.pgconf.eu FOSDEM PGDay 2013 ] || Feb 01, 2013 || Belgium || Brussels || Talks
|-
| [[PGDay_Argentina_2012|PgDay Argentina 2012]] || [http://www.pgday.com.ar/buenosaires2012 3rd National PostgreSQL Mini-Conference 2012] || November 13, 2012 || Argentina || Buenos Aires || Training, Talks
|-
| PyCon Argentina 2012 || [http://ar.pycon.org/2012 4th National Python Conference 2012] || November 12-17, 2012 || Argentina || Buenos Aires || Training, Talks, Booth
|-
| PgDay Ecuador 2012 || [https://wiki.postgresql.org/wiki/PGDay_Ecuador_2012 PgDay Ecuador 2012] || November 17, 2012 || Ecuador || Quito || Talks
|-
| Campus Party Brasil 2013 || [http://www.campus-party.com.br Campus Party Brasil 2013 ] || January 28th - February 03rd, 2013 || Brazil || São Paulo || Talks, Workshops
|-
| FOSDEM PGDay 2013 || [http://fosdem2013.pgconf.eu/ FOSDEM PGDay 2013 ] || February 1st - February 3rd, 2013 || Belgium || Brussels || Talks, Booth
|-
| ConFoo 2013: Web Techno Conference || [http://confoo.ca/en ConFoo 2013: Web Techno Conference] || February 25th - March 1st, 2013 || Canada || Montreal || Training, Talks, Booth
|-
| PGDay NYC 2013 || [http://pgday.nycpug.org PGDay NYC 2013] || March 22nd, 2013 || USA || New York || Talks
|-
| PostgresOpen 2013 || [http://postgresopen.org PostgresOpen 2013] || Sept 16-18, 2013 || USA || Chicago || Training, Talks
|}

{| border="1"
|+
|- style="background:Khaki;"
'''Previous PostgreSQL Events Listing'''
| '''Event''' || '''Web Page''' || '''Date''' || '''Country''' || '''City''' || '''Activities'''
|-
| [[FOSDEM 2013]] || [http://www.fosdem.org/2013/ FOSDEM '13] || February 02-03, 2013 || Belgium || Brussels || Booth, Devroom
|-
| PGDay Sao Paulo 2012 || [http://www.postgresql.org.br/node/16949 PGDay Sao Paulo 2012] || November 9, 2012 || Brazil || Sao Paulo, SP || Talks
|-
| PGDay Ouro Preto do Oeste 2012 || [http://www.postgresql.org.br/node/17041 PGDay Ouro Preto do Oeste 2012] || October 26, 2012 || Brazil || Ouro Preto do Oeste, RO || Talks
|-
| PGDay Rolim de Moura 2012 || [http://www.postgresql.org.br/node/17035 PGDay Rolim de Moura 2012] || October 25, 2012 || Brazil || Rolim de Moura, RO || Talks
|-
| PGDay Cacoal 2012 || [http://www.postgresql.org.br/node/17033 PGDay Cacoal 2012] || October 24, 2012 || Brazil || Cacoal, RO || Talks
|-
| PG Conference Europe 2012 || [http://2012.pgconf.eu PostgreSQL Conference 2012] || October 23-26, 2012 || Czech Rep. || Prague || Training, [[PostgreSQL Conference Europe Talks 2012|Talks]]
|-
| Latinoware 2012 || [http://2012.latinoware.org/?lang=en Latinoware 2012] || October 17-19, 2012 || Brazil || Foz do Iguaçu, PR || Talks
|-
| PGDay Campinas 2012 || [http://www.dextra.com.br/eventos/pgday-campinas-2012/ PGDay Campinas 2012] || October 03, 2012 || Brazil || Campinas, SP || Talks
|-
| PGOpen 2012 || [http://postgresopen.org Postgres Open 2012] || September 16-19, 2012 || USA || Chicago, IL || Training, Talks
|-
| FrOSCon || [http://www.froscon.org/ FrOSCon 2012]|| August 25-26, 2012 || Germany || St. Augustin || Talks, Booth
|-
| PG Day PR 2012 || [http://postgresql.org.br/eventos/2012/pgday/pr/ PGDay Paraná 2012] || August 16, 2012 || Brazil || Cascavel - PR || Talks, Workshops, Boths
|-
| FISL 13 || [http://softwarelivre.org/fisl13?lang=en FISL 13] || July 25-28, 2012 || Brazil || Porto Alegre - RS || Hackathon, booth
|-
| PG Conference China 2012 || [http://wiki.postgresql.org/wiki/Pgconfchina2012 PG Conference China 2012] || June 14-17, 2012 || China || Beijing || Training, Talks
|-
| PG Day France 2012 || [http://www.pgday.fr/ PG Day France 2012] || June 7, 2012 || France || Lyon || Talks
|-
| PGDay RO 2012 || [http://postgresql.org.br/eventos/2012/pgday/ro/ PGDay IFRO Porto Velho - Rondônia 2012] || May 19, 2012 || Brazil || Porto Velho, RO || Talks, Workshop
|-
| PGCon 2012 || [http://www.pgcon.org/2012/ PGCon 2012] || May 15-18, 2012 || Canada || Ottawa, ON || Training, Talks
|-
| PostgresSQL Conference 2012 Japan || [http://www.postgresql.jp/events/pgcon2012/top PostgreSQL Conference 2012 Japan] || February 24, 2012 || Japan || Tokyo || Talks
|-
| PGDay Austin 2012 || [http://pgday.austinpug.org PGDay Austin 2012] || March 28, 2012 || USA || Austin, TX || Talks
|-
| PGDay DC 2012 || [http://pgday.bwpug.org PGDay DC 2012] || March 30, 2012 || USA || Reston, VA || Talks
|-
| PGDay NYC 2012 || [http://pgday.nycpug.org PGDay NYC 2012] || April 2, 2012 || USA || New York, NY || Talks
|-
| [[FOSDEM 2012]] || [http://www.fosdem.org/2012/ FOSDEM '12] || February 04-05, 2012 || Belgium || Brussels || Booth, Devroom
|-
| PG Session #3 || [http://www.postgresql-sessions.org/3/ PG Session #3] || February 02 2012 || France || Paris || Talks
|-
| PGDay Roraima 2011 || [http://postgresql.org.br/eventos/2011/pgday/rr/ PGDay Roraima 2011] || December 03, 2011 || Brazil || Boa Vista - RR || Talks, Training
|-
| PostgreSQL Conference Germany 2011 || [http://2011.pgconf.de/ PGConf.DE 2011]|| Nov 11, 2011 || Germany || Oberhausen || [[German-Speaking PostgreSQL Conference 2011|Talks]]
|-
| PGBR2011 || [http://pgbr.postgresql.org.br/ PGBR2011] || Nov 3-4, 2011 || Brazil || São Paulo || Tutorials, Talks, Booth
|-
| PGDay RO || [http://postgresql.org.br/eventos/2011/pgday/ro/ PGDay RONDÔNIA 2011] || October 26-28, 2011 || Brazil || Porto Velho, Rolim de Moura, Ji Parana - RO || Talks, workshops
|-
| PostgreSQL Conference Europe 2011 || [http://2011.pgconf.eu/ PGConf.EU 2011] || October 18-21, 2011 || The Netherlands || Amsterdam || Training, [[PostgreSQL Conference Europe Talks 2011|Talks]]
|-
| PostgreSQL Conference West 2011 || [http://www.postgresqlconference.org/ #PgWest 2011] || September 27-30, 2011 || San Jose || California || Training, Talks, Booth
|-
| Postgres Open || [http://postgresopen.org/2011/home/ Postgres Open 2011] || Sep 14-16, 2011 || USA || Chicago || [[Postgres Open Talks 2011]]
|-
| PGDay Porto Alegre || [http://www.postgresql.org.br/eventos/2011/pgday/rs PGDay Porto Alegre] || August 19, 2011 || Brazil || Porto Alegre || Talks, Booths
|-
| FrOSCon || [http://www.froscon.de/ FrOSCon 2011]|| August 20-21, 2011 || Germany || St. Augustin || Talks, Booth
|-
| Pg Conf Colombia || [http://www.pgconf.org Pg Conf Colombia 2011]|| August 4-5, 2011 || Colombia || Bucaramanga ||
|-
| PgDay at OSCON 2011 || [http://pugs.postgresql.org/node/1663 PgDay at OSCON 2011] || July 24, 2011 || USA || Portland, OR || Talks, party
|-
| 2011 China PostgreSQL User conference ||[http://wiki.postgresql.org/wiki/Pgconchina2011 2011 China PostgreSQL User conference] || July 16-17, 2011 || China || GUANGZHOU ||Talks,Tutorial
|-
| PGCon 2011 || [http://www.pgcon.org/2011/ PGCon 2011] || May 17-20, 2011 || Canada || Ottawa || Talks, Training
|-
| PGEast 2011 || [https://www.postgresqlconference.org/ PGWest] || March 22-25, 2011 || USA || New York, NY || Talks, Training
|-
| PostgresSQL Conference 2011 Japan || || February 25-26, 2011 || Tokyo || Japan ||
|-
| [[FOSDEM, Brussels 2011]] || [http://www.fosdem.org/2011/ FOSDEM '11] || February 05-06, 2011 || Belgium || Brussels || Booth, Devroom
|-
| [[PGDAY-Latino, La Habana 2011]] || [http://postgresql.uci.cu/news/19 PGDAY-Latino '11] || February 01-05, 2011 || Cuba || La Habana || Talks, Workshop
|-
| colspan="6" | [[Events/2010 | 2010 events]]
|-
| colspan="6" | [[Events/2009 | 2009 events]]
|-
| colspan="6" | [[Events/2008 | 2008 events]]
|-
| colspan="6" | [[Events/2007 | 2007 events]]
|}

== External Links ==

* [http://conferences.oreillynet.com/ O'Reilly conferences]
* [http://opencheese.com/2007/10/14/open-source-events-2008/ "Open Source and Linux events in 2008"]

[[Category:PostgreSQL Events]]
[[Category:Advocacy]]

PDXPUG Talks

2013-03-27T00:52:15Z

Gabrielle: /* 2013 */

QA Platform hosted at Command Prompt

2013-03-03T04:30:59Z

Gabrielle: /* List of servers */

== General information ==

The following servers are hosted by Command Prompt (Portland, Oregon, USA) for performance testing.

Feel free to ask for access to these servers if you are a well known community member (contact: markwkm at gmail dot com).

== List of servers ==

{| border="1" cellpadding="1" cellspacing="0" style="font-size: 85%; border: gray solid 1px; border-collapse: collapse; width: 100%; table-layout: fixed;"
|- style="background: #ececec"
! style="width:20em" | Server
! style="width:12em" | Donated by
! Hardware specs
! Usage
|-
! bgcolor="#ececec" | community6.commandprompt.com
| style="text-align:center" | HP
| DL-380 G5 - 2 x Quad-Core Xeon 2.0 GHz - 32 GB - 8 x 15K RPM 72 GB SAS
| bgcolor="#ffc586" | Performance Guide
|-
! bgcolor="#ececec" | community7.commandprompt.com
| style="text-align:center" | Wikipedia
| Dell PowerEdge 2950 - 2 x Dual-Core 1.86GHz - 16GB - storage unknown at this time
| bgcolor="#ffc586" | benchmarking/demos
|-
! bgcolor="#ececec" | community8.commandprompt.com
| style="text-align:center" | Wikipedia
| Dell PowerEdge 2950 - 2 x Dual-Core 1.86GHz - 16GB - storage unknown at this time
| bgcolor="#ffc586" | parts vehicle
|-
! bgcolor="#ececec" | community9.commandprompt.com
| style="text-align:center" | IBM
| 2 x Dual-Core G5 (PPC970MP) 2.5 GHz - 4 GB - 250 GB SATA
| bgcolor="#ffc586" | Performance Guide, pg_top development
|-
! bgcolor="#ececec" | community10.commandprompt.com
| style="text-align:center" | HP
| DL-380 G5 - 2 x Quad-Core Xeon 2.0 GHz - 32 GB - 8 x 15K RPM 72 GB SAS
| bgcolor="#ffc586" | Performance Guide
|-
| ! style="text-align:center" | storage
| style="text-align:center" | Hi5.com
| 4 x Dell Powervaults with 14 drives each
| bgcolor="#ffc586" |
|-
| ! style="text-align:center" | storage
| style="text-align:center" | HP
| MSA70 with 25 72GB 15K RPM SAS Drives
| bgcolor="#ffc586" |
|-
! bgcolor="#ececec" | <strike>community7.commandprompt.com</strike>
| style="text-align:center" | Sun Microsystems
| Sun Fire T2000 - 8 core UltraSPARC T1 1.2 GHz - 32 GB - 2 x 10K RPM 72 GB SAS
| bgcolor="#ffc586" | pg_top development
|-
! bgcolor="#ececec" | <strike>community8.commandprompt.com</strike>
| style="text-align:center" | IBM
| 2 x Dual-Core G5 (PPC970MP) 2.5 GHz - 4 GB - 250 GB SATA
| bgcolor="#ddffdd" | Web Server (personal stuff goes in ~/Sites)
|}

== Technical Details ==

=== community 6 ===

''' HP DL-380 G5 '''

* 2 x Quad-Core Intel(R) Xeon(R) E5405 processors
* 32GB Fully Buffered DIMM PC2-5300 8x4GB DR LP Memory
* HP Smart Array P800 Controller
* 8 x 72GB Hot Plug 2.5 SAS 15,000 rpm Hard Drive (Internal)
* Gentoo Base System release 1.12.13

=== community7 ===

''' Dell PowerEdge 2950 '''

* 2 x Dual-Core 1.86 GHz processors
* 16GB Memory
* 4MB L2 cache
* ? Hard Drive (Internal)
* Ubuntu12

=== community8 ===

''' Dell PowerEdge 2950 '''

* 2 x Dual-Core 1.86 GHz processors
* 16GB Memory
* 4MB L2 cache
* ? Hard Drive (Internal)
* Ubuntu12

=== community 9 ===

''' Apple Mac Pro G5 '''

* Model M9592LL/A
* 2 x Dual-Core 2.5 GHz G5 (PPC970MP) processors
* 4GB Memory
* 250GB SATA Hard Drive (Internal)
* Yellow Dog Linux 6.0

=== community 10 ===

''' HP DL-380 G5 '''

* 2 x Quad-Core Xeon 2.0 GHz
* 32GB Fully Buffered DIMM PC2-5300 8x4GB DR LP Memory
* HP Smart Array P800 Controller
* 8 x 72GB Hot Plug 2.5 SAS 15,000 rpm Hard Drive (Internal)
* Gentoo Base System release 1.12.13

=== <strike>community 7</strike> ===

''' Sun Fire T2000 '''

* 8 core 1.2 GHz UltraSPARC T1 processor
* 32GB Memory
* 8 x 73GB 2.5 SAS 10,000 rpm Hard Drive (Internal)
* Solaris 10 8/7

=== <strike>community 8</strike>===

''' Apple Mac Pro G5 '''

* Model M9592LL/A
* 2 x Dual-Core 2.5 GHz G5 (PPC970MP) processors
* 4GB Memory
* 250GB SATA Hard Drive (Internal)
* Yellow Dog Linux 6.0

[[Category:Community]]

QA Platform hosted at Command Prompt

2013-03-03T04:28:26Z

Gabrielle: /* Technical Details */

== General information ==

The following servers are hosted by Command Prompt (Portland, Oregon, USA) for performance testing.

Feel free to ask for access to these servers if you are a well known community member (contact: markwkm at gmail dot com).

== List of servers ==

{| border="1" cellpadding="1" cellspacing="0" style="font-size: 85%; border: gray solid 1px; border-collapse: collapse; width: 100%; table-layout: fixed;"
|- style="background: #ececec"
! style="width:20em" | Server
! style="width:12em" | Donated by
! Hardware specs
! Usage
|-
! bgcolor="#ececec" | community6.commandprompt.com
| style="text-align:center" | HP
| DL-380 G5 - 2 x Quad-Core Xeon 2.0 GHz - 32 GB - 8 x 15K RPM 72 GB SAS
| bgcolor="#ffc586" | Performance Guide
|-
! bgcolor="#ececec" | <strike>community7.commandprompt.com</strike>
| style="text-align:center" | Sun Microsystems
| Sun Fire T2000 - 8 core UltraSPARC T1 1.2 GHz - 32 GB - 2 x 10K RPM 72 GB SAS
| bgcolor="#ffc586" | pg_top development
|-
! bgcolor="#ececec" | <strike>community8.commandprompt.com</strike>
| style="text-align:center" | IBM
| 2 x Dual-Core G5 (PPC970MP) 2.5 GHz - 4 GB - 250 GB SATA
| bgcolor="#ddffdd" | Web Server (personal stuff goes in ~/Sites)
|-
! bgcolor="#ececec" | community9.commandprompt.com
| style="text-align:center" | IBM
| 2 x Dual-Core G5 (PPC970MP) 2.5 GHz - 4 GB - 250 GB SATA
| bgcolor="#ffc586" | Performance Guide, pg_top development
|-
! bgcolor="#ececec" | community10.commandprompt.com
| style="text-align:center" | HP
| DL-380 G5 - 2 x Quad-Core Xeon 2.0 GHz - 32 GB - 8 x 15K RPM 72 GB SAS
| bgcolor="#ffc586" | Performance Guide
|-
! bgcolor="#ececec" | community7.commandprompt.com
| style="text-align:center" | Wikipedia
| Dell PowerEdge 2950 - 2 x Dual-Core 1.86GHz - 16GB - storage unknown at this time
| bgcolor="#ffc586" | benchmarking/demos
|-
! bgcolor="#ececec" | community8.commandprompt.com
| style="text-align:center" | Wikipedia
| Dell PowerEdge 2950 - 2 x Dual-Core 1.86GHz - 16GB - storage unknown at this time
| bgcolor="#ffc586" | parts vehicle
|-
| ! style="text-align:center" | storage
| style="text-align:center" | Hi5.com
| 4 x Dell Powervaults with 14 drives each
| bgcolor="#ffc586" |
|-
| ! style="text-align:center" | storage
| style="text-align:center" | HP
| MSA70 with 25 72GB 15K RPM SAS Drives
| bgcolor="#ffc586" |
|}

== Technical Details ==

=== community 6 ===

''' HP DL-380 G5 '''

* 2 x Quad-Core Intel(R) Xeon(R) E5405 processors
* 32GB Fully Buffered DIMM PC2-5300 8x4GB DR LP Memory
* HP Smart Array P800 Controller
* 8 x 72GB Hot Plug 2.5 SAS 15,000 rpm Hard Drive (Internal)
* Gentoo Base System release 1.12.13

=== community7 ===

''' Dell PowerEdge 2950 '''

* 2 x Dual-Core 1.86 GHz processors
* 16GB Memory
* 4MB L2 cache
* ? Hard Drive (Internal)
* Ubuntu12

=== community8 ===

''' Dell PowerEdge 2950 '''

* 2 x Dual-Core 1.86 GHz processors
* 16GB Memory
* 4MB L2 cache
* ? Hard Drive (Internal)
* Ubuntu12

=== community 9 ===

''' Apple Mac Pro G5 '''

* Model M9592LL/A
* 2 x Dual-Core 2.5 GHz G5 (PPC970MP) processors
* 4GB Memory
* 250GB SATA Hard Drive (Internal)
* Yellow Dog Linux 6.0

=== community 10 ===

''' HP DL-380 G5 '''

* 2 x Quad-Core Xeon 2.0 GHz
* 32GB Fully Buffered DIMM PC2-5300 8x4GB DR LP Memory
* HP Smart Array P800 Controller
* 8 x 72GB Hot Plug 2.5 SAS 15,000 rpm Hard Drive (Internal)
* Gentoo Base System release 1.12.13

=== <strike>community 7</strike> ===

''' Sun Fire T2000 '''

* 8 core 1.2 GHz UltraSPARC T1 processor
* 32GB Memory
* 8 x 73GB 2.5 SAS 10,000 rpm Hard Drive (Internal)
* Solaris 10 8/7

=== <strike>community 8</strike>===

''' Apple Mac Pro G5 '''

* Model M9592LL/A
* 2 x Dual-Core 2.5 GHz G5 (PPC970MP) processors
* 4GB Memory
* 250GB SATA Hard Drive (Internal)
* Yellow Dog Linux 6.0

[[Category:Community]]

QA Platform hosted at Command Prompt

2013-03-03T04:24:23Z

Gabrielle: /* List of servers */

== General information ==

The following servers are hosted by Command Prompt (Portland, Oregon, USA) for performance testing.

Feel free to ask for access to these servers if you are a well known community member (contact: markwkm at gmail dot com).

== List of servers ==

{| border="1" cellpadding="1" cellspacing="0" style="font-size: 85%; border: gray solid 1px; border-collapse: collapse; width: 100%; table-layout: fixed;"
|- style="background: #ececec"
! style="width:20em" | Server
! style="width:12em" | Donated by
! Hardware specs
! Usage
|-
! bgcolor="#ececec" | community6.commandprompt.com
| style="text-align:center" | HP
| DL-380 G5 - 2 x Quad-Core Xeon 2.0 GHz - 32 GB - 8 x 15K RPM 72 GB SAS
| bgcolor="#ffc586" | Performance Guide
|-
! bgcolor="#ececec" | <strike>community7.commandprompt.com</strike>
| style="text-align:center" | Sun Microsystems
| Sun Fire T2000 - 8 core UltraSPARC T1 1.2 GHz - 32 GB - 2 x 10K RPM 72 GB SAS
| bgcolor="#ffc586" | pg_top development
|-
! bgcolor="#ececec" | <strike>community8.commandprompt.com</strike>
| style="text-align:center" | IBM
| 2 x Dual-Core G5 (PPC970MP) 2.5 GHz - 4 GB - 250 GB SATA
| bgcolor="#ddffdd" | Web Server (personal stuff goes in ~/Sites)
|-
! bgcolor="#ececec" | community9.commandprompt.com
| style="text-align:center" | IBM
| 2 x Dual-Core G5 (PPC970MP) 2.5 GHz - 4 GB - 250 GB SATA
| bgcolor="#ffc586" | Performance Guide, pg_top development
|-
! bgcolor="#ececec" | community10.commandprompt.com
| style="text-align:center" | HP
| DL-380 G5 - 2 x Quad-Core Xeon 2.0 GHz - 32 GB - 8 x 15K RPM 72 GB SAS
| bgcolor="#ffc586" | Performance Guide
|-
! bgcolor="#ececec" | community7.commandprompt.com
| style="text-align:center" | Wikipedia
| Dell PowerEdge 2950 - 2 x Dual-Core 1.86GHz - 16GB - storage unknown at this time
| bgcolor="#ffc586" | benchmarking/demos
|-
! bgcolor="#ececec" | community8.commandprompt.com
| style="text-align:center" | Wikipedia
| Dell PowerEdge 2950 - 2 x Dual-Core 1.86GHz - 16GB - storage unknown at this time
| bgcolor="#ffc586" | parts vehicle
|-
| ! style="text-align:center" | storage
| style="text-align:center" | Hi5.com
| 4 x Dell Powervaults with 14 drives each
| bgcolor="#ffc586" |
|-
| ! style="text-align:center" | storage
| style="text-align:center" | HP
| MSA70 with 25 72GB 15K RPM SAS Drives
| bgcolor="#ffc586" |
|}

== Technical Details ==

=== community 6 ===

''' HP DL-380 G5 '''

* 2 x Quad-Core Intel(R) Xeon(R) E5405 processors
* 32GB Fully Buffered DIMM PC2-5300 8x4GB DR LP Memory
* HP Smart Array P800 Controller
* 8 x 72GB Hot Plug 2.5 SAS 15,000 rpm Hard Drive (Internal)
* Gentoo Base System release 1.12.13

=== community 7 ===

''' Sun Fire T2000 '''

* 8 core 1.2 GHz UltraSPARC T1 processor
* 32GB Memory
* 8 x 73GB 2.5 SAS 10,000 rpm Hard Drive (Internal)
* Solaris 10 8/7

=== community 8 ===

''' Apple Mac Pro G5 '''

* Model M9592LL/A
* 2 x Dual-Core 2.5 GHz G5 (PPC970MP) processors
* 4GB Memory
* 250GB SATA Hard Drive (Internal)
* Yellow Dog Linux 6.0

=== community 9 ===

''' Apple Mac Pro G5 '''

* Model M9592LL/A
* 2 x Dual-Core 2.5 GHz G5 (PPC970MP) processors
* 4GB Memory
* 250GB SATA Hard Drive (Internal)
* Yellow Dog Linux 6.0

=== community 10 ===

''' HP DL-380 G5 '''

* 2 x Quad-Core Xeon 2.0 GHz
* 32GB Fully Buffered DIMM PC2-5300 8x4GB DR LP Memory
* HP Smart Array P800 Controller
* 8 x 72GB Hot Plug 2.5 SAS 15,000 rpm Hard Drive (Internal)
* Gentoo Base System release 1.12.13

[[Category:Community]]

PDXPUG Talks

2013-02-07T00:43:16Z

Gabrielle: started 2013 list!

QA Platform hosted at Command Prompt

2013-02-06T22:35:46Z

Gabrielle: /* List of servers */ - prelim info about new servers from Wikipedia

== General information ==

The following servers are hosted by Command Prompt (Portland, Oregon, USA) for performance testing.

Feel free to ask for access to these servers if you are a well known community member (contact: markwkm at gmail dot com).

== List of servers ==

{| border="1" cellpadding="1" cellspacing="0" style="font-size: 85%; border: gray solid 1px; border-collapse: collapse; width: 100%; table-layout: fixed;"
|- style="background: #ececec"
! style="width:20em" | Server
! style="width:12em" | Donated by
! Hardware specs
! Usage
|-
! bgcolor="#ececec" | community6.commandprompt.com
| style="text-align:center" | HP
| DL-380 G5 - 2 x Quad-Core Xeon 2.0 GHz - 32 GB - 8 x 15K RPM 72 GB SAS
| bgcolor="#ffc586" | Performance Guide
|-
! bgcolor="#ececec" | community7.commandprompt.com
| style="text-align:center" | Sun Microsystems
| Sun Fire T2000 - 8 core UltraSPARC T1 1.2 GHz - 32 GB - 2 x 10K RPM 72 GB SAS
| bgcolor="#ffc586" | pg_top development
|-
! bgcolor="#ececec" | community8.commandprompt.com
| style="text-align:center" | IBM
| 2 x Dual-Core G5 (PPC970MP) 2.5 GHz - 4 GB - 250 GB SATA
| bgcolor="#ddffdd" | Web Server (personal stuff goes in ~/Sites)
|-
! bgcolor="#ececec" | community9.commandprompt.com
| style="text-align:center" | IBM
| 2 x Dual-Core G5 (PPC970MP) 2.5 GHz - 4 GB - 250 GB SATA
| bgcolor="#ffc586" | Performance Guide, pg_top development
|-
! bgcolor="#ececec" | community10.commandprompt.com
| style="text-align:center" | HP
| DL-380 G5 - 2 x Quad-Core Xeon 2.0 GHz - 32 GB - 8 x 15K RPM 72 GB SAS
| bgcolor="#ffc586" | Performance Guide
|-
| ! style="text-align:center" | NA
| style="text-align:center" | Wikipedia
| Dell PowerEdge 2950 - 2 x Dual-Core 1.86GHz - 16GB - storage unknown at this time
| bgcolor="#ffc586" | benchmarking
|-
| ! style="text-align:center" | NA
| style="text-align:center" | Wikipedia
| Dell PowerEdge 2950 - 2 x Dual-Core 1.86GHz - 16GB - storage unknown at this time
| bgcolor="#ffc586" | benchmarking
|-
| ! style="text-align:center" | storage
| style="text-align:center" | Hi5.com
| 4 x Dell Powervaults with 14 drives each
| bgcolor="#ffc586" |
|-
| ! style="text-align:center" | storage
| style="text-align:center" | HP
| MSA70 with 25 72GB 15K RPM SAS Drives
| bgcolor="#ffc586" |
|}

== Technical Details ==

=== community 6 ===

''' HP DL-380 G5 '''

* 2 x Quad-Core Intel(R) Xeon(R) E5405 processors
* 32GB Fully Buffered DIMM PC2-5300 8x4GB DR LP Memory
* HP Smart Array P800 Controller
* 8 x 72GB Hot Plug 2.5 SAS 15,000 rpm Hard Drive (Internal)
* Gentoo Base System release 1.12.13

=== community 7 ===

''' Sun Fire T2000 '''

* 8 core 1.2 GHz UltraSPARC T1 processor
* 32GB Memory
* 8 x 73GB 2.5 SAS 10,000 rpm Hard Drive (Internal)
* Solaris 10 8/7

=== community 8 ===

''' Apple Mac Pro G5 '''

* Model M9592LL/A
* 2 x Dual-Core 2.5 GHz G5 (PPC970MP) processors
* 4GB Memory
* 250GB SATA Hard Drive (Internal)
* Yellow Dog Linux 6.0

=== community 9 ===

''' Apple Mac Pro G5 '''

* Model M9592LL/A
* 2 x Dual-Core 2.5 GHz G5 (PPC970MP) processors
* 4GB Memory
* 250GB SATA Hard Drive (Internal)
* Yellow Dog Linux 6.0

=== community 10 ===

''' HP DL-380 G5 '''

* 2 x Quad-Core Xeon 2.0 GHz
* 32GB Fully Buffered DIMM PC2-5300 8x4GB DR LP Memory
* HP Smart Array P800 Controller
* 8 x 72GB Hot Plug 2.5 SAS 15,000 rpm Hard Drive (Internal)
* Gentoo Base System release 1.12.13

[[Category:Community]]

PDXPUG Talks

2012-11-17T23:29:39Z

Gabrielle: /* 2012 */

PDXPUG Talks

2012-11-17T23:29:29Z

Gabrielle: /* 2012 */

File:PDXPUGSpeakerInfo.odt

2012-11-13T02:13:00Z

Gabrielle: uploaded a new version of "File:PDXPUGSpeakerInfo.odt"

Form letter we send out to new speakers. Be sure to FITB :)

Tuning Your PostgreSQL Server

2012-10-24T01:43:28Z

Gabrielle: fixed some typos, made formatting of bulleted lists consistent, added link to pgbadger

__NOTOC__
''by Greg Smith, Robert Treat, and Christopher Browne''

{{Languages}}

PostgreSQL ships with a basic configuration tuned for wide compatibility rather than performance. Odds are good the default parameters are very undersized for your system. Rather than get dragged into the details of everything you should eventually know (which you can find if you want it at the [http://www.pgcon.org/2008/schedule/events/104.en.html GUC Three Hour Tour]), here we're going to sprint through a simplified view of the basics, with a look at the most common things people new to PostgreSQL aren't aware of. You should click on the name of the parameter in each section to jump to the relevant documentation in the PostgreSQL manual for more details after reading the quick intro here. There is also additional information available about many of these parameters, as well as a list of parameters you shouldn't adjust, at [https://www.packtpub.com/article/server-configuration-tuning-postgresql Server Configuration Tuning].

== Background Information on Configuration Settings ==

PostgreSQL settings can be manipulated a number of different ways, but generally you will want to update them in your postgresql.conf file. The specific options available change from release to release, the definitive list is in the source code at src/backend/utils/misc/guc.c for your version of PostgreSQL (but the pg_settings view works well enough for most purposes).

=== The types of settings ===

There are several different types of configuration settings, divided up based on the possible inputs they take

* Boolean: true, false, on, off
* Integer: Whole numbers (2112)
* Float: Decimal values (21.12)
* Memory / Disk: Integers (2112) or "computer units" (512MB, 2112GB). Avoid integers--you need to know the underlying unit to figure out what they mean. Computer units are only available starting in version 8.2.
* Time: "Time units" aka d,m,s (30s). Sometimes the unit is left out; don't do that
* Strings: Single quoted text ('pg_log')
* ENUMs: Strings, but from a specific list ('WARNING', 'ERROR')
* Lists: A comma separated list of strings ('"$user",public,tsearch2)

=== When they take effect ===

PostgreSQL settings have different levels of flexibility for when they can be changed, usually related to internal code restrictions. The complete list of levels is:

* Postmaster: requires restart of server
* Sighup: requires a HUP of the server, either by kill -HUP (usually -1), pg_ctl reload, or select pg_reload_conf();
* User: can be set within individual sessions, take effect only within that session
* Internal: set at compile time, can't be changed, mainly for reference
* Backend: settings which must be set before session start
* Superuser: can be set at runtime for the server by superusers

Most of the time you'll only use the first of these, but the second can be useful if you have a server you don't want to take down, while the user session settings can be helpful for some special situations. You can tell which type of parameter a setting is by looking at the "context" field in the pg_settings view.

=== Important notes about postgresql.conf ===

* You should be able to find it at $PGDATA/postgresql.conf; watch out for symbolic links and other trickiness
* You can figure out the file location with ''SHOW config_file''
* Lines with # are comments and have no effect. For a new database, this will mean the setting is using the default, but on running systems this may not hold true! '''In versions before 8.3, commenting out a setting does not restore it to the default.''' Even in versions after that, changes to the postgresql.conf do not take effect without a reload/restart, so it's possible for the system to be running something different than what is in the file.
* If the same setting is listed multiple times, the last one wins

=== Viewing the current settings ===

* Look in postgresql.conf. This works if you follow good practice, but it's not definitive!
* ''show all'', ''show <setting>'' will show you the current value of the setting. Watch out for session specific changes
* ''select * from pg_settings'' will label session specific changes as locally modified

==[http://www.postgresql.org/docs/current/static/runtime-config-connection.html#GUC-LISTEN-ADDRESSES listen_addresses] ==

By default, PostgreSQL only responds to connections from the local host. If you want your server to be accessible from other systems via standard TCP/IP networking, you need to change listen_addresses from its default. The usual approach is to set it to listen to all addresses like this:

<code><pre>
listen_addresses = '*'
</pre></code>

And then control who can and can't connect via the [http://www.postgresql.org/docs/current/static/auth-pg-hba-conf.html pg_hba.conf] file.

==[http://www.postgresql.org/docs/current/static/runtime-config-connection.html#GUC-MAX-CONNECTIONS max_connections]==

max_connections sets exactly that: the maximum number of client connections allowed. This is very important to some of the below parameters (particularly work_mem) because there are some memory resources that are or can be allocated on a per-client basis, so the maximum number of clients suggests the maximum possible memory use. Generally, PostgreSQL on good hardware can support a few hundred connections. If you want to have thousands instead, you should consider using [[Replication, Clustering, and Connection Pooling|connection pooling software]] to reduce the connection overhead.

==[http://www.postgresql.org/docs/current/static/runtime-config-resource.html#GUC-SHARED-BUFFERS shared_buffers]==

The shared_buffers configuration parameter determines how much memory is dedicated to PostgreSQL to use for caching data. One reason the defaults are low is because on some platforms (like older Solaris versions and SGI), having large values requires invasive action like recompiling the kernel. Even on a modern Linux system, the stock kernel will likely not allow setting shared_buffers to over 32MB without adjusting kernel settings first.

If you have a system with 1GB or more of RAM, a reasonable starting value for shared_buffers is 1/4 of the memory in your system. If you have less RAM you'll have to account more carefully for how much RAM the OS is taking up; closer to 15% is more typical there. There are some workloads where even larger settings for shared_buffers are effective, but given the way PostgreSQL also relies on the operating system cache, it's unlikely you'll find using more than 40% of RAM to work better than a smaller amount.

Note that on Windows (and on PostgreSQL versions before 8.1), large values for shared_buffers aren't as effective, and you may find better results keeping it relatively low and using the OS cache more instead. On Windows the useful range is 64MB to 512MB, and for earlier than 8.1 versions the effective upper limit is near shared_buffers=50000 (just under 400MB--older versions before 8.2 don't allow using MB values for their settings, you specify this parameter in 8K blocks).

It's likely you will have to increase the amount of memory your operating system allows you to allocate at once to set the value for shared_buffers this high. On UNIX-like systems, if you set it above what's supported, you'll get a message like this:

<code><pre>
IpcMemoryCreate: shmget(key=5432001, size=415776768, 03600) failed: Invalid argument

This error usually means that PostgreSQL's request for a shared memory
segment exceeded your kernel's SHMMAX parameter. You can either
reduce the request size or reconfigure the kernel with larger SHMMAX.
To reduce the request size (currently 415776768 bytes), reduce
PostgreSQL's shared_buffers parameter (currently 50000) and/or
its max_connections parameter (currently 12).
</pre></code>

See [http://www.postgresql.org/docs/current/static/kernel-resources.html Managing Kernel Resources] for details on how to correct this.

Changing this setting requires restarting the database. Also, this is a hard allocation of memory; the whole thing gets allocated out of virtual memory when the database starts.

==[http://www.postgresql.org/docs/current/static/runtime-config-query.html#GUC-EFFECTIVE-CACHE-SIZE effective_cache_size]==

effective_cache_size should be set to an estimate of how much memory is available for disk caching by the operating system and within the database itself, after taking into account what's used by the OS itself and other applications. This is a guideline for how much memory you expect to be available in the OS and PostgreSQL buffer caches, not an allocation! This value is used only by the PostgreSQL query planner to figure out whether plans it's considering would be expected to fit in RAM or not. If it's set too low, indexes may not be used for executing queries the way you'd expect. The setting for shared_buffers is not taken into account here--only the effective cache_size_value is, so it should include memory dedicated to the database too.

Setting effective_cache_size to 1/2 of total memory would be a normal conservative setting, and 3/4 of memory is a more aggressive but still reasonable amount. You might find a better estimate by looking at your operating system's statistics. On UNIX-like systems, add the free+cached numbers from free or top to get an estimate. On Windows see the "System Cache" size in the Windows Task Manager's Performance tab. Changing this setting does not require restarting the database (HUP is enough).

==[http://www.postgresql.org/docs/current/static/runtime-config-wal.html#RUNTIME-CONFIG-WAL-CHECKPOINTS checkpoint_segments checkpoint_completion_target]==

PostgreSQL writes new transactions to the database in files called WAL segments that are 16MB in size. Every time checkpoint_segments worth of these files have been written, by default 3, a checkpoint occurs. Checkpoints can be resource intensive, and on a modern system doing one every 48MB will be a serious performance bottleneck. Setting checkpoint_segments to a much larger value improves that. Unless you're running on a very small configuration, you'll almost certainly be better setting this to at least 10, which also allows usefully increasing the completion target.

For more write-heavy systems, values from 32 (checkpoint every 512MB) to 256 (every 4GB) are popular nowadays. Very large settings use a lot more disk and will cause your database to take longer to recover, so make sure you're comfortable with both those things before large increases. Normally the large settings (>64/1GB) are only used for bulk loading. Note that whatever you choose for the segments, you'll still get a checkpoint at least every 5 minutes unless you also increase checkpoint_timeout (which isn't necessary on most systems).

;PostgreSQL 8.3 and newer

Starting with PostgreSQL 8.3, the checkpoint writes are spread out a bit while the system starts working toward the next checkpoint. You can spread those writes out further, lowering the average write overhead, by increasing the checkpoint_completion_target parameter to its useful maximum of 0.9 (aim to finish by the time 90% of the next checkpoint is here) rather than the default of 0.5 (aim to finish when the next one is 50% done). A setting of 0 gives something similar to the behavior of the earlier versions. The main reason the default isn't just 0.9 is that you need a larger checkpoint_segments value than the default for broader spreading to work well. For lots more information on checkpoint tuning, see [http://www.westnet.com/~gsmith/content/postgresql/chkp-bgw-83.htm Checkpoints and the Background Writer] (where you'll also learn why tuning the background writer parameters, particularly those in 8.2 and below, is challenging to do usefully).

==[http://www.postgresql.org/docs/current/static/routine-vacuuming.html#AUTOVACUUM autovacuum] [http://www.postgresql.org/docs/8.3/static/runtime-config-resource.html#GUC-MAX-FSM-PAGES max_fsm_pages, max_fsm_relations]==

The autovacuum process takes care of several maintenance chores inside your database that you really need. Generally, if you think you need to turn regular vacuuming off because it's taking too much time or resources, that means you're doing it wrong. The answer to almost all vacuuming problems is to vacuum more often, not less, so that each individual vacuum operation has less to clean up.

However, it's acceptable to disable autovacuum for short periods of time, for instance when bulk loading large amounts of data.

;PostgreSQL 8.4 and newer

The FSM was rewritten for PostgreSQL 8.4, so earlier advice is no longer applicable. The <tt>max_fsm_pages</tt> and <tt>max_fsm_relations</tt> settings are gone, as the new FSM is self-adapting ([http://www.depesz.com/index.php/2008/10/04/waiting-for-84-new-fsm-free-space-map/ more info]). <tt>autovacuum</tt> is enabled by default and should remain so, as vacuum much less invasive in 8.4 than before thanks to [http://www.depesz.com/index.php/2008/12/08/waiting-for-84-visibility-maps/ visibility maps].

;PostgreSQL 8.3 and earlier

As of 8.3, autovacuum is turned on by default, and you should keep it that way. In 8.1 and 8.2 you will have to turn it on yourself. Note that in those earlier versions, you may need to tweak its settings a bit to make it aggressive enough; it may not do enough work by default if you have a larger database or do lots of updates.

You may also need to increase the value of max_fsm_pages and max_fsm_relations as needed. The Free Space Map is used to track where there are dead tuples (rows) that may be reclaimed. You will only get effective nonblocking VACUUM queries if the dead tuples can be listed in the Free Space Map. As a result, if you do not plan to run VACUUM frequently, and if you expect a lot of updates, you should ensure these values are usefully large (and remember, these values are cluster wide, not database wide). It should be easy enough to set max_fsm_relations high enough; the problem that will more typically occur is when max_fsm_pages is not set high enough. Once the Free Space Map is full, VACUUM will be unable to track further dead pages. In a busy database, this needs to be set much higher than 1000... also, remember that changing these settings requires a restart of the database, so it is wise to to err on the side of setting comfortable margins for these settings.

If you run VACUUM VERBOSE on your database, it'll tell you how many pages and relations are in use (and, under 8.3, what the current limits are). For example,

<pre>
INFO: free space map contains 5293 pages in 214 relations
DETAIL: A total of 8528 page slots are in use (including overhead).
8528 page slots are required to track all free space.
Current limits are: 204800 page slots, 1000 relations, using 1265 kB.
</pre>

If you find that your settings are already too low, you will likely need to do aggressive vacuuming of your system, and possibly reindexing and vacuum full maybe needed as well. If you're getting close to the limits for page slots, typical practice is to just double the current values, with perhaps a smaller percentage increase once you've gotten much higher (in the millions range). For the max relations settings, note that this setting includes all the databases in your cluster.

One other situation to be aware of is that of a database approaching autovacuum_freeze_max_age. When a database approaches this point, it will begin to vacuum every table in the database that has not been vacuumed before. On some systems this may not result in much activity, but for systems where there are a lot of tables that are not modified often, this can be a more common occurrence (especially if the system has gone through a dump/restore, say for upgrading). The significance of all of this is that, even on a system with well set fsm settings, once your system begins vacuuming all of the additional tables, your old fsm setting may no longer be appropriate.

==[http://www.postgresql.org/docs/current/static/runtime-config-logging.html logging]==
There are many things you can log that may or may not be important to you. You should investigate the documentation on all of the options, but here are some tips & tricks to get you started:

*pgFouine is a tool used to analyze postgresql logs for performance tuning. If you plan to use this tool, it has specific logging requirements. Please check http://pgfouine.projects.postgresql.org/

*a newer alternative to pgFouine is pgbadger: http://dalibo.github.com/pgbadger/

*log_destination & log_directory (& log_filename): What you set these options to is not as important as knowing they can give you hints to determine where your database server is logging to. Best practice would be to try and make this as similar as possible across your servers. Note that in some cases, the init script starting your database may be customizing the log destination in the command line used to start the database, overriding what's in the postgresql.conf (and making it so you'll get different behavior if you run pg_ctl manually instead of using the init script).

*log_min_error_statement: You should probably make sure this is at least on error, so that you will see any SQL commands which cause an error. should be the default on recent versions.

*log_min_duration_statement: Not necessary for everyday use, but this can generate [[Logging Difficult Queries|logs of "slow queries"]] on your system.

*log_line_prefix: Appends information to the start of each line. A good generic recommendation is '%t:%r:%u@%d:[%p]: ' : %t=timestamp, %u=db user name, %r=host connecting from, %d=database connecting to, %p=PID of connection. It may not be obvious what the PID is useful at first, but it can be vital for trying to troubleshoot problems in the future so better to put in the logs from the start.

*log_statement: Choices of none, ddl, mod, all. Using all in production leads to severe performance penalties. DDL can sometime be helpful to discover rogue changes made outside of your recommend processes, by "cowboy DBAs" for example.

==[http://www.postgresql.org/docs/current/static/runtime-config-query.html#GUC-DEFAULT-STATISTICS-TARGET default_statistics_target]==

The database software collects statistics about each of the tables in your database to decide how to execute queries against it. In earlier versions of PostgreSQL, the default setting of 10 doesn't collect very much information, and if you're not getting good execution query plans particularly on larger (or more varied) tables you should increase default_statistics_target then ANALYZE the database again (or wait for autovacuum to do it for you).

;PostgreSQL 8.4 and later

The starting default_statistics_target value was raised from 10 to 100 in PostgreSQL 8.4. Increases beyond 100 may still be useful, but this increase makes for greatly improved statistics estimation in the default configuration. The maximum value for the parameter was also increased from 1000 to 10,000 in 8.4.

==[http://www.postgresql.org/docs/current/static/runtime-config-resource.html#GUC-WORK-MEM work_mem maintainance_work_mem]==

If you do a lot of complex sorts, and have a lot of memory, then increasing the work_mem parameter allows PostgreSQL to do larger in-memory sorts which, unsurprisingly, will be faster than disk-based equivalents.

This size is applied to each and every sort done by each user, and complex queries can use multiple working memory sort buffers. Set it to 50MB, and have 30 users submitting queries, and you are soon using 1.5GB of real memory. Furthermore, if a query involves doing merge sorts of 8 tables, that requires 8 times work_mem. You need to consider what you set max_connections to in order to size this parameter correctly. This is a setting where data warehouse systems, where users are submitting very large queries, can readily make use of many gigabytes of memory.

maintenance_work_mem is used for operations like vacuum. Using extremely large values here doesn't help very much, and because you essentially need to reserve that memory for when vacuum kicks in, takes it away from more useful purposes. Something in the 256MB range has anecdotally been a reasonably large setting here.

;PostgreSQL 8.3 and later

In 8.3 you can use log_temp_files to figure out if sorts are using disk instead of fitting in memory. In earlier versions, you might instead just monitor the size of them by looking at how much space is being used in the various ''$PGDATA/base/<db oid>/pgsql_tmp'' files. You can see sorts to disk happen in EXPLAIN ANALYZE plans as well. For example, if you see a line like "Sort Method: external merge Disk: 7526kB" in there, you'd know a work_mem of at least 8MB would really improve how fast that query executed, by sorting in RAM instead of swapping to disk.

==[http://www.postgresql.org/docs/current/static/runtime-config-wal.html#GUC-WAL-SYNC-METHOD wal_sync_method wal_buffers]==

After every transaction, PostgreSQL forces a commit to disk out to its write-ahead log. This can be done a couple of ways, and on some platforms the other options are considerably faster than the conservative default. open_sync is the most common non-default setting switched to, on platforms that support it but default to one of the fsync methods. See [http://www.westnet.com/~gsmith/content/postgresql/TuningPGWAL.htm Tuning PostgreSQL WAL Synchronization] for a lot of background on this topic. Note that open_sync writing is buggy on some platforms (such as [http://lwn.net/Articles/350219/ Linux]), and you should (as always) do plenty of tests under a heavy write load to make sure that you haven't made your system less stable with this change. [[Reliable Writes]] contains more information on this topic.

Linux kernels starting with version 2.6.33 will cause earlier versions of PostgreSQL to default to wal_sync_method=open_datasync; before that kernel release the default picked was always fdatasync. This can cause a significant performance decrease when combined with small writes and/or small values for wal_buffers.

Increasing wal_buffers from its tiny default of a small number of kilobytes is helpful for write-heavy systems. Benchmarking generally suggests that just increasing to 1MB is enough for some large systems, and given the amount of RAM in modern servers allocating a full WAL segment (16MB, the useful upper-limit here) is reasonable. Changing wal_buffers requires a database restart.

;PostgreSQL 9.1 and later

Starting with PostgreSQL 9.1 wal_buffers defaults to being 1/32 of the size of shared_buffers, with an upper limit of 16MB (reached when shared_buffers=512MB).

PostgreSQL 9.1 also changes the logic for selecting the default wal_sync_method such that on newer Linux kernels, it will still select fdatasync as its method--the same as on older Linux versions.

==[http://www.postgresql.org/docs/current/static/runtime-config-query.html#GUC-CONSTRAINT-EXCLUSION constraint_exclusion]==

;PostgreSQL 8.4 and later
In 8.4, <tt>constraint_exclusion</tt> now defaults to a new choice: <tt>partition</tt>. This will only enable constraint exclusion for partitioned tables which is the right thing to do in nearly all cases.

;PostgreSQL 8.3 and earlier
If you plan to use table partitioning, you need to turn on constraint exclusion. Since it does add overhead to query planning, it is recommended you leave this off outside of this scenario.

==[http://www.postgresql.org/docs/current/static/runtime-config-resource.html#GUC-MAX-PREPARED-TRANSACTIONS max_prepared_transactions]==

This setting is used for managing 2 phase commit. If you do not use two phase commit (and if you don't know what it is, you don't use it), then you can set this value to 0. That will save a little bit of shared memory. For database systems with a large number (at least hundreds) of concurrent connections, be aware that this setting also affects the number of available lock-slots in pg_locks, so you may want to leave it at the default setting. There is a formula for how much memory gets allocated [http://www.postgresql.org/docs/current/static/kernel-resources.html#SHARED-MEMORY-PARAMETERS in the docs] and in the default postgresql.conf.

Changing max_prepared_transactions requires a server restart.

==[http://www.postgresql.org/docs/current/static/runtime-config-wal.html#GUC-SYNCHRONOUS-COMMIT synchronous_commit]==
PostgreSQL can only safely use a write cache if it has a battery backup. See [http://www.postgresql.org/docs/current/static/wal-reliability.html WAL reliability] for an essential introduction to this topic. No, really; go read that right now, it's vital to understand that if you want your database to work right.

You may be limited to approximately 100 transaction commits per second per client in situations where you don't have such a durable write cache (and perhaps only 500/second even with lots of clients).

;PostgreSQL 8.3 and later

Asynchronous commit was introduced in PostgreSQL 8.3. For situations where a small amount of data loss is acceptable in return for a large boost in how many updates you can do to the database per second, consider switching synchronous commit off. This is particularly useful in the situation where you do not have a battery-backed write cache on your disk controller, because you could potentially get thousands of commits per second instead of just a few hundred.

For earlier versions of PostgreSQL, you may find people recommending that you set ''fsync=off'' to speed up writes on busy systems. This is dangerous--a power loss could result in your database getting corrupted and not able to start again. Synchronous commit doesn't introduce the risk of ''corruption'', which is really bad, just some risk of data ''loss''.

==[http://www.postgresql.org/docs/current/static/runtime-config-query.html#GUC-RANDOM-PAGE-COST random_page_cost]==
This setting suggests to the optimizer how long it will take your disks to seek to a random disk page, as a multiple of how long a sequential read (with a cost of 1.0) takes. If you have particularly fast disks, as commonly found with RAID arrays of SCSI disks, it may be appropriate to lower random_page_cost, which will encourage the query optimizer to use random access index scans. Some feel that 4.0 is always too large on current hardware; it's not unusual for administrators to standardize on always setting this between 2.0 and 3.0 instead. In some cases that behavior is a holdover from earlier PostgreSQL versions where having random_page_cost too high was more likely to screw up plan optimization than it is now (and setting at or below 2.0 was regularlly necessary). Since these cost estimates are just that--estimates--it shouldn't hurt to try lower values.

But this not where you should start to search for plan problems. Note that random_page_cost is pretty far down this list (at the end in fact). If you are getting bad plans, this shouldn't be the first thing you look at, even though lowering this value may be effective. Instead, you should start by making sure autovacuum is working properly, that you are collecting enough statistics, and that you have correctly sized the memory parameters for your server--all the things gone over above. After you've done all those much more important things, if you're still getting bad plans ''then'' you should see if lowering random_page_cost is still useful.

[[Category:Administration]] [[Category:Performance]]

PDXPUG Talks

2012-10-23T01:36:39Z

Gabrielle: /* 2012 */

Pgbenchtesting

2012-10-09T00:18:27Z

Gabrielle: /* Prepared vs. Ah-hoc Queries */ fix typo

= Testing for Performance Regression with pgBench 9.0 =

This page will eventually be merged into [[Regression Testing with pgbench]]

* [http://developer.postgresql.org/pgdocs/postgres/pgbench.html pgBench 9.0 Docs]

In order to test for performance regressions (or improvements) it's necessary to install two versions of PostgreSQL on the same machine. Otherwise, you have no comparable statistics. For example, you might install 8.4.3 and 9.0alpha5, or you might install 9.0alpha4 and 9.0alpha5. You also might run against the same test version in two modes: with HS/SR and without, for example.

Since pgbench is such a simple test, you'll need to run several different runs to see different aspects of performance. It's also a good idea to run each at least 3 times, since pgbench has some randomness to it.

Always run the same version of pgBench against both databases, probably the newer version.

Some factors:

* '''Where to run pgBench''': Ideally, you want to run it from a separate machine from the one holding the database. That way, you don't have pgBench taking CPU away from the database.
* '''Number of Threads and Clients to Use''': This depends on the number of cores on the machine(s) you're testing. For each core available to the database, I suggest 1 thread and 2 clients. Note: do not use multi-threaded pgBench on non-threadsafe systems; you will get unreliable results.
* '''PostgreSQL Configuration''': use what you'd consider a normal performance configuration for the machine being tested. Use (as much as possible) the same configuration for both.
* '''Time vs. Transactions''': results which run pgbench for a specific amount of time are easier to compare. You also know how long they'll take you.
* '''Initializing Databases''': if you are going to use the same database for several test runs in a row, it's important that you "prime" it by running pgbench against it for at least 20 minutes first, or the first couple of tests will be misleadingly fast. Alternately, you can initialize a new database for each test run.
* '''Time to Run''' Ideally, you'd do each pgbench run for at least an hour for useful results. However, this interferes with running a lot of different tests for people who don't do this full-time or have a dedicated testing server. Make sure to run it for at least 10 minutes, though, to get results you can even measure. Possibly run the most interesting results in a 1-hour test. All tests below run for 10 minutes.

What follows are some examples of tests. The command line given would be appropriate for a machine with 2 cores available to the database and thread-safe.

== Memory vs. Disk Performance ==

You want to test pgbench at the 3 levels of performance related to disk: in buffer, mostly in cache, and all on disk. You manipulate this by changing the scale factor, following these two formulas, assuming a dedicated database server.

''scale / 75 = 1GB database''

* In Buffer Test: 0.1 X RAM
* Mostly Cached: 0.9 X RAM
* Mostly on Disk: 4.0 X RAM

Note that the mostly-on-disk test may require you to have a considerable amount of disk space available for your database.

Examples: the following assume a 2-core machine with 2GB of RAM, running for 10 minutes:

Buffer test:
* pgbench -i -s 15 bench1
* pgbench -c 4 -j 2 -T 600 bench1

Mostly Cache Test:
* pgbench -i -s 70 bench2
* pgbench -c 4 -j 2 -T 600 bench2

On-Disk Test:
* pgbench -i -s 600 bench3
* pgbench -c 4 -j 2 -T 600 bench3

Measuring the amount of time required to initialize the three databases will also provide interesting results.

== Read vs. Write Performance ==

It is also interesting to test relative speed of different write patterns. For this set of tests, use either the Mostly Cache or On-Disk size database, or something in-between.

The tests below assume the same machine above. All start with:

* pgbench -i -s 70 bench2

Read-Write Test
* pgbench -c 4 -j 2 -T 600 bench2

Read-Only Test
* pgbench -c 4 -j 2 -T 600 -S bench2

Simple Write Test
* pgbench -c 4 -j 2 -T 600 -N bench2

== Connections and Contention ==

For this series of tests, we want to test how PostgreSQL behaves with different levels of connection activity. In this case, it's very relative to how many cores you have. Again, we're assuming the same 2-core, 2GB machine.

Unfortunately, you can only do this test effectively from another machine which has at least as many cores as the database server.

All tests start with:
* pgbench -i -s 30 bench

Single-Threaded
* pgbench -c 1 -T 600 bench

Normal Load
* pgbench -c 8 -j 2 -T 600 bench

Heavy Contention
* pgbench -c 64 -j 4 -T 600 bench

Heavy Connections without Contention
* pgbench -c 64 -j 4 -T 600 -N bench

Heavy Re-connection (simulates no connection pooling)
* pgbench -c 8 -j 2 -T 600 -C bench

== Prepared vs. Ah-hoc Queries ==

pgBench 9.0 also allows you to test the effect of prepared queries on performance. Assumes the same database server as above.

Initialize with:
* pgbench -i -s 70 bench

Unprepared, Read-Write:
* pgbench -c 4 -j 2 -T 600 bench

Prepared, Read-Write:
* pgbench -c 4 -j 2 -T 600 -m prepared bench

Unprepared, Read-Only:
* pgbench -c 4 -j 2 -T 600 -S bench

Prepared, Read-Only:
* pgbench -c 4 -j 2 -T 600 -m prepared -S bench

[[Category:Benchmarking]]

Postgres Open 2012

2012-09-24T23:09:34Z

Gabrielle: /* Tuesday September 18 */

Slides for talks will be linked here!

== Monday September 17 ==

* [https://wiki.postgresql.org/wiki/File:Pg_security_20120917.odp PostgreSQL AuthN / AuthZ]

== Tuesday September 18 ==

* [https://wiki.postgresql.org/images/7/73/Range-types-pgopen-2012.pdf Range Types in PostgreSQL 9.2 - Your Life Will Never Be the Same]
* Scaling out by distributing and replicating data in Postgres-XC
* PostgreSQL When It's Not Your Job

* [http://tapoueh.org/images/fotolog.pdf Large Scale MySQL Migration to PostgreSQL]
* Choosing a logical replication system: Slony vs Bucardo
* Temporal Database Demo

* [http://www.setspace.com/~jmscott/pgopen-2012-ams-talk.pdf 12 Calm Years of PostgreSQL in Critical Messaging]
* [https://speakerdeck.com/u/jacobian/p/the-first-postsql-database PostgreSQL in the cloud: Theory and Practice]
* [http://www.hagander.net/talks/Backup%20strategies.pdf PostgreSQL Backup Strategies]

* This Is PostGIS
* [http://plv8-pgopen.herokuapp.com Embracing the Web with JSON and PLV8]
* How Akiban Implemented a New Database Compatible with the PostgreSQL Protocol

* [[Media:Ha_postgres.pdf|High Availability with PostgreSQL and Pacemaker]]
* [[Media:Logging_pgopen_withnotes.pdf|Logging: Not Just for Lumberjacks]]
* [http://stuff.coffeecode.net/2012/pgopen_fulltext/pgsql-fulltext-intro.html Full-text search - seek and ye shall find]

=== Lightning Talks ===

[http://keithf4.com/sites/keithf4.com/files/pgjobmon_pgopen2012.pdf I wonder if my function works? (pg_jobmon)]

== Wednesday September 19 ==

* [http://pgexperts.com/document.html?id=54 Super Jumbo Deluxe], plus [http://pgexperts.com/presentations.html more presentations here]
* [[Media:OO_approach.pdf|An object oriented approach to data driven software development]]
* TransLattice Elastic Database Architecture Deep Dive

* [http://www.pateldenish.com/2012/04/deploying-maximum-ha-architecture-with-postgresql.html Deploying maximum HA architecture with Postgres] , for pg_reorg [http://static.slidesharecdn.com/swf/ssplayer2.swf?doc=p90xyourdatabase-13010796913746-phpapp02&stripped_title=p90-x-your-database p90x talk]
* Scaling Postgres with some help from Redis
* Retail DDL

* Query Logging and Workload Analysis
* A Shared-nothing cluster system: Postgres-XC
* [http://jkshah.blogspot.com/2012/09/pgopen-2012-dvdstore-benchmark-and.html DVDStore Benchmark and PostgreSQL]

* Performance Improvements in PostgreSQL 9.2
* A Batch of Commit Batching
* [http://momjian.us/main/presentations/features.html#cte Programming the SQL Way with Common Table Expressions]

* Postgres is the new default – how we transitioned our platform at Engine Yard and why you should too
* Leveraging PLV8 in Javascript-heavy Web Applications
* [http://keithf4.com/sites/keithf4.com/files/pgextractor_pgopen2012.pdf PG Extractor - A smarter pg_dump]

File:Logging pgopen withnotes.pdf

2012-09-24T23:05:43Z

Gabrielle:

PDXPUG Talks

2012-08-21T01:31:51Z

Gabrielle: put the recent 2012 talks in the correct field order :/

PDXPUG Talks

2012-08-21T01:30:10Z

Gabrielle: added more 2012 talks

Oscon 2012 signup

2012-06-29T03:09:28Z

Gabrielle: add dates

* Sign up and email markwkm@postgresql with a t-shirt size by July 1 and we will try to have one waiting for you at the booth. Time slots are intended to allow people to have enough time to go to a session before it starts and to come to the booth after a session ends for people attending the conference.

== Tue July 17 (17:00-18:00) (5pm - 6pm) - Opening Reception ==

* Mark Wong

== Wed July 18 (10:00-16:30) (10am-4:30pm) ==

=== 10:00 - 11:15 ===
Ed Snajder
David Throckmorton

=== 11:15 - 12:50 LUNCH ===

=== 12:50 - 14:25 LUNCH ===
Jesse Hallett <hallettj@gmail.com>

=== 14:25 - 15:15 ===

=== 15:15 - 16:30 ===

== Thurs July 19 10:00 - 17:00 (10am-5pm) ==

=== 10:00 - 11:25 ===
Ed Snajder

=== 11:25 - 12:50 LUNCH ===

=== 12:50 - 14:25 LUNCH ===

=== 14:25 - 16:00 ===

=== 16:00 - 17:00 ===

----

Thanks for participating!

[[Category:PostgreSQL Events]]

PDXPUG Talks

2012-06-22T23:45:52Z

Gabrielle: update with more talks from 2012

Running & Installing PostgreSQL On Native Windows

2012-06-21T23:29:10Z

Gabrielle: /* Can I install PostgreSQL on a FAT partition? */

{{Languages}}

== Supported Platforms ==
=== What versions of Windows does PostgreSQL run on?===

PostgreSQL is supported on Windows XP and above, at least as of version 9.0. It will run on 32 and 64 bit systems.

Versions of the server are not tested on new operating system versions that are released after a newer major version of the server was released. For example, Windows 7 was released after PostgreSQL 8.4, so PostgreSQL 8.3 will not be supported on it. Similarly, when the upcoming RHEL 6 is released, only PostgreSQL 9.0.x will be supported on it. We aim to support new versions of Windows in the PostgreSQL major version following their release at the latest.

For information about platforms supported by the One-click installer, please see the installer download page, off the main [http://www.postgresql.org/download/windows download page for windows].

For information on non-Windows platforms see the [[FAQ|main FAQ]] and the [http://www.postgresql.org/download/ main download page].

=== What Windows platforms are NOT supported? ===

The PostgreSQL installers are not tested or supported on:

* Windows XP Embedded
* Windows 2000
* Windows NT 4
* Windows NT 3.5.x
* Windows 95/98/ME/3.x
* Windows CE
* Windows Mobile

These platforms are not supported. Please do not ask the mailing list for help with any of these platforms.

Please read the troubleshooting notes on [[Troubleshooting Installation#Installation fails on windows embedded|installation on embedded versions of windows]] for some more information about embedded windows.

=== I heard that NT4 and Windows 2000 are supported. Is that true? ===
Although not officially supported, PostgreSQL may run on Windows NT4 and Windows 2000
with a few minor issues including:
* The installer may not work correctly, thus you will need to install PostgreSQL manually from the binary .zip release, or compile it yourself.
* PostgreSQL uses a feature in the NTFS filesystem called 'reparse points' to implement tablespaces. Reparse points are not available in NT4, hence tablespaces cannot be used on NT4.
* There is no 'runas.exe' included in Windows NT4 as standard, making it difficult to start PostgreSQL from an administrative account.
It should also be noted that very little testing has been done on NT4.
* No testing is done on Windows NT 4 or Windows 2000, so newer versions may not work on these platforms.

Please do not ask for help with these obsolete platforms on the mailing list. Some of the [http://www.postgresql.org/support/professional_support professional support] companies may be able to assist you, though.

=== What about Windows 95/98/ME? ===

PostgreSQL requires functionality that is not available on these
platforms and will not run on them. If you need to run PostgreSQL
on these platforms, you can look at the
[http://www.postgresql.org/files/documentation/faqs/text/FAQ_CYGWIN Cygwin]
port, which has basic support for 9x platforms.

=== Is there a 64-bit build of PostgreSQL for Windows? ===

Yes. A [[64bit Windows port]] was released for [[PostgreSQL 9.0]].

32-bit builds of previous versions of PostgreSQL generally run fine on 64-bit Windows. Though they cannot practically use more than about 1GB of shared_buffers directly, they can still benefit from more than 4GB of memory because the Windows kernel will use that memory to cache disk reads.

=== What about 64-bit ODBC drivers? ===

At time of writing there was 64-bit support in the [http://psqlodbc.projects.postgresql.org/ psqlODBC] source code, but no official binary releases of 64-bit ODBC drivers. Check the psqlODBC website for details.

== Installation ==

=== What do I need to install PostgreSQL on Windows? ===

See [http://www.postgresql.org/download/windows the PostgreSQL for Windows download page] for various ways to download and install PostgreSQL on Windows.

The easiest way to install PostgreSQL on Windows is with the
One Click installer package maintained by EnterpriseDB, which you can get from the page linked to above. This will install PostgreSQL along with
pgAdmin (a graphical administration and management program), a selection of 'contrib' modules to provide additional specialised functionality, and a choice of procedural languages. A program called StackBuilder will be installed to help you download and install any additional components, like ODBC or JDBC drivers, that you may need.

=== What do I need to compile PostgreSQL from source code? ===

See the [http://www.postgresql.org/docs/current/static/install-windows.html documentation]
for instructions on how to compile PostgreSQL for windows, including details about supported compilers and tools.

=== Why do I need a non-administrator account to run PostgreSQL under? ===

When a hacker gains entry to a computer using a software bug in a
package, she gains the permissions of the user account under which the
service is run. Whilst we do not know of any such bugs in PostgreSQL,
we enforce the use of a non-administrative service account to minimise
the possible damage that a hacker could do should they find and utilise
a bug in PostgreSQL to hack the system.

This has long been common practice in the Unix world, and is starting to
become standard practice in the Windows world as well as Microsoft and
other vendors work to improve the security of their systems.

Note, that with the release of PostgreSQL 8.2, it is possible to run under
a administrative account. PostgreSQL 8.2 and above are able to irrevocably
give up administrative rights at startup, thus ensuring the rest of the
system remains secure in the extremely unlikely event that PostgreSQL
becomes compromised.

=== Can I install PostgreSQL on a FAT partition? ===

Use of PostgreSQL on FAT32 file systems is not supported or tested, because
FAT32 is a terrible file system on which to run ''any'' database.

PostgreSQL's number one priority is the integrity of your data. FAT and
FAT32 filesystems simply do not offer the reliability or crash-safety required.
In addition, the lack of security features offered by FAT make it
impossible to secure the raw data files from unauthorised modification.
Finally, PostgreSQL utilises a feature called 'reparse points' to
implement tablespaces. This feature is not available on FAT partitions.

The NTFS file system is a journalled filesystem offering much better
reliability and crash recovery. In addition, it has a comprehensive
access control system and offers the reparse point functionality used
by PostgreSQL.

For this reason, the PostgreSQL installer package will not initialise
a database cluster on anything but an NTFS partition. The server and
utilities may be installed on any partition type.

It is recognised however, that in rare cases FAT partitions may be the only choice.
In such cases, you can simply install PostgreSQL as normal, but without initialising the
database cluster. When the installation has finished, manually run
the 'initdb.exe' program on the FAT partition. Security and
reliability will be compromised however, and any attempts to create
tablespaces will fail. Do not use PostgreSQL on FAT32 in production.

=== What filesystem permissions does PostgreSQL require? ===
The PostgreSQL service account needs ''read'' permissions on
all directories leading up to the service directory. It needs ''write'' permissions ''only''
on the data directory. Specifically, it should ''not'' be granted anything other than ''read''
permissions on the directories containing binary files. (All directories below the installation
directory are set by the installer, so unless you change something, there should be no problem with this).

PostgreSQL also needs ''read'' permissions on system DLL files like kernel32.dll and user32.dll
(among others), which is normally granted by default, and on the CMD.EXE binary, which may in some
scenarios be locked down and need opening.

If you are running PostgreSQL on a multi-user system, you should remove the permissions from all
non-administrative users from the PostgreSQL directories. No user ''ever'' needs permissions on the
PostgreSQL files - all communication is done through the libpq connection. Direct access to data files
can lead to information disclosure or system instability!

=== Why can't I select Unicode as an encoding? ===

Starting with PostgreSQL 8.1, the UTF-8 unicode encoding is fully supported on Windows. The Unicode ODBC driver supports UTF-16, and the JDBC driver also has full unicode support.

The PostgreSQL server does not support the 2-byte UTF-16 or 4-byte UTF-32 Unicode encodings for internal data storage or on-the-wire communication. Beause UTF-16 is the default encoding on Windows, and what people on Windows usually mean when they say "Unicode", you might expect this to be a problem, but in practice it's fine, as the ODBC and JDBC drivers take care of this. Programs using libpq directly need to be aware of this, but not much else does.

=== I installed in a non-english language, but all messages show up in english! ===
The language choice made during the installation only selects which language is used by the installer. To
change the language of the messages of the installed product, make sure you have installed the ''National language
support'' feature. Then edit your postgresql.conf file and change the value of the ''lc_messages'' parameter
to the language you want.

== Common installation errors ==

=== PostgreSQL and/or the installer crashes at startup, fails to start or hangs on start ===

By far most common reasons for installation and runtime problems with PostgreSQL on Windows are Windows Scripting Host issues, antivirus software problems and 3rd-party (non-Microsoft) software firewalls. People also sometimes have trouble with the postgres service account password.

The following articles cover these issues. Please read them and follow their instructions before asking for help with installer problems.

==== Antivirus software ====

If you have any antivirus software installed, you '''must''' exclude the data directories that are to be used by PostgreSQL and '''must''' exclude postgresql.exe process. If that still does not help, it may be required to completely uninstall the antivirus software from the machine.

Antivirus software can interfere with PostgreSQL's operation, because PostgreSQL requires file access commands in Windows to behave exactly as documented by Microsoft, and many antivirus programs contain errors or accidental behavior changes that cause these commands to misbehave subtly. Most programs do not care because they access files in fairly simple ways. Because PostgreSQL is continuously reading from and writing to the same set of files from multiple processes, it tends to trigger programming and design mistakes in antivirus software, particularly problems related to concurrency. Such problems can cause random and unpredictable errors, or even data corruption.

Antivirus software is also likely to dramatically slow down PostgreSQL's operation. For that reason, you should at least exclude postgres.exe and the data directories so the scanner ignores them.

===== What Anti-Virus software is compatible? =====

The systems used to build the Windows installers all run either Sophos AV or AVG Free Edition, and
those systems pass a full set of PostgreSQL regression tests running those programs.
Microsoft Security Essentials is also known to work.

Specific issues have been reported with the ''nod32'' antivirus
product. If you are using this product, add "postmaster.exe" to the list
of excluded processes (available under advanced options). This has been
reported to fix the problem.

Specific issues have also been reported with McAfee and Panda anti-virus
software and NetLimiter network monitoring software. While some people do have
PostgreSQL working with these software packages, there is no specific or even
recommend solutions that have not worked in some cases, so the issues would appear
to be installation specific, sometimes even requiring uninstallation.

==== Software firewalls ====

If you have any 3rd-party firewall software installed on your machine, try either disabling it or uninstalling it. There's really no need for 3rd party firewalls on Windows XP and above, as the built-in firewall provided by Microsoft does an excellent job already. Some badly-written 3rd party firewalls do not uninstall correctly, so after uninstallation you might have to [http://support.microsoft.com/kb/299357 tell Windows to repair its network settings].

If you had a 3rd-party firewall and have now uninstalled it, make sure to turn Windows Firewall back on, as many products turn it off during installation and fail to turn it back on during uninstallation.

==== The installer exits with a runtime installation error? ====

The installer may exit with an error like: ''An error occured executing the Microsoft VC++ runtime installer''. This can only happen on Windows.

There are two main reasons why this may occur:

1) The Windows Scripting Host is unable to execute VBscripts. This can occur if the scripting host is disabled (which is unusual), or if the installation is broken. A sign of this problem is a message like ''CScript Error: Can't find script engine "VBScript" for script "C:\...''. It can often be resolved by re-registering the VBscript interpreter - click ''Start'' -> ''Run'' and enter the following and click ''OK'':

regsvr32 %systemroot%\system32\vbscript.dll

If that fails, on older versions of Windows you can try [http://www.microsoft.com/downloads/en/results.aspx?freetext=windows+script+host&displaylang=en&stype=s_basic updating the scripting host].

2) The installer is unable to properly read and write files to the system ''TEMP'' directory. This can occur if the ''TEMP'' or ''TMP'' environment variables are set to non-standard values, and can be recognised by errors in the logfile indicating that scripts could not be executed or found. To resolve this issue, ensure the ''TEMP'' and ''TMP'' variables are set to their correct values.

==== Trouble with passwords for the postgres user ====

Dave Page wrote a [http://pgsnake.blogspot.com/2010/07/postgresql-passwords-and-installers.html blog post] explaining what the different passwords are used for, and how to overcome common problems such as resetting them.

==== PATH environment variable ====

There is also an issue if you have installed ''cygwin'', and the cygwin\bin directory is present
in the system PATH variable. There are DLL files in the cygwin directory related to interpreted languages (TCL,
perl, python) that contain bugs that can cause the installer or the installed version of PostgreSQL to either hang
or crash. Remove the cygwin\bin directory from your path before running the installer!

Problems have also been observed when the PATH environment variable contains directories containing versions of libssl and/or libintl.

==== I'm getting permissions errors when installing/running initdb ====

Make sure the PostgreSQL service account has permissions on the directories leading up to the one
you have installed into. The installer will set permissions on the install directory but not on
parent directories of it.

You may also see related errors show up as The database Cluster initialisation failed during the One Click installer. Check your install-postgresql log
but it is usually related to permission errors. The following thread may help,

http://forums.enterprisedb.com/posts/list/2044.page#7503

Or alternatively, you can fix up the directory permissions and then manually restart the initcluster.vbs script like this for v9,

cscript //NoLogo "<install_path>/installer/server/initcluster.vbs" "postgres" "postgres" "<password>" "<install_path>" "<data_path>" 5432 "DEFAULT"

==== The installer claims the specified account is an administrator, but it isn't! ====

Most likely, the specified account is an administrator or power user,
even though you aren't aware of it. The check used by the installer
specifically checks for membership in the Administrators or
Power Users group. Work your way backwards using Local Users and Groups -
open the Administrators group, see who's a member. Then check any
groups (domain or local) that are a member of the Administrators group,
and any groups members of that group etc. PostgreSQL checks any level
of nested groups.

==== I'm getting an error message that says PostgreSQL cannot be installed from a Terminal Services session ====

This is unfortunately so. The PostgreSQL backend won't run from a TS session, and in order to do initdb the installer
has to start a standalone backend. Therefore, installation has to be performed from the console. Note that if you are
using Windows Server 2003, you can get remote access to the actual console and not just an administrative session.
To do this, start the Remote Desktop Connection by executing mstsc /console, and then connect as usual.
This will lock the local console of the server and give you control over that session. In this scenario,
PostgreSQL should install just fine.

==== I get the error "the user has not been granted the requested logon type at this computer" or similar ====

Make sure the specified PostgreSQL account has the "Log on as a service"
and "Log on locally" rights. The "Log on locally" is only required for
the install part, and can be removed once the installation is completed
if security policies require it. (Rights are granted and revoked using
the "Local Security Policy" MMC snapin. "Log on locally" is default,
and "Log on as a service" will normally be granted automatically by
the installer).

If you still have this problem, enable auditing (also using
the "Local Security Policy" snapin) and let us know what other rights
were required in your setup.

Note that if your computer is a member of a domain, the settings of
the security policies may be controlled at the domain level using
Group Policy.

==== How do I delete the service account - it's not listed under users! ====

Windows sometimes hide some accounts from the GUI tools, so they cannot be removed from there. This includes
the auto-created service account for PostgreSQL (that may be left over from a previous installation). To delete this
account, use the NET command on the commandline:
NET USER <username> /DELETE
Where <username> is the windows login name of the user, for example ''postgres''.

== Common runtime issues ==

=== I'm getting "dynamic load error" when installing a procedural language ===

Most commonly this means that the actual language DLL for the procedural language is missing. The PostgreSQL
DLLs only contains the language bindings, and require the language distribution DLLs to be present
in the system PATH. For a list of the current required DLLs for the different procedural languages,
please see [http://pginstaller.projects.postgresql.org the installation instructions].

To find out exactly which DLL files are missing, you can use the ''depends'' tool from Microsoft.
It is available in the Windows Support Tools, that are on the Windows CD as a separate install. Just run
''depends plpython.dll'' (for PL/python) to show which imports are missing.

=== I'm seeing a lot of postgres.exe processes even though I only started the server once ===

This is normal. PostgreSQL uses a multi-process architecture. In an empty system you will see anything from two to
five processes. Once clients start to connect, the number of processes will increase.

=== How do I set an environment variable? ===

PostgreSQL uses environment variables for several settings. To change an environment variable in most
Windows versions, go into Properties for My Computer, then into Advanced. Note that there are two sets of
environment variables - one for the system which applies to all users and one for the current user. If you
want an environment variable to affect the PostgreSQL service, you must change the system variable. After
changing a system variable, you must restart the service.

=== I cannot run with more than about 125 connections at once, despite having capable hardware ===

When running as a service, you may experience failures with more than approximately 125 simultaneous connections.
This can happen because some of the libraries that PostgreSQL is dependent on are dependent on user32.dll which allocates
memory from an area known as the Desktop Heap. The desktop heap is assigned to each logon session, with non-interactive
sessions typically being assigned 512KB. Each postgres process that runs typically consumes approximately 3.2KB of desktop
heap, which coupled with other overhead can exhaust the allocated heap at somewhere around 125 connections. This doesn't
happen when running from the command line (or more precisely, happens with much higher numbers of connections) because the
interactive logon session is typically allocated 3MB of Desktop Heap.

You can increase the non-interactive Desktop Heap by modifying the third SharedSection value in the registry as described
in this [http://support.microsoft.com/kb/184802 Microsoft Knowledgebase article]. Note that this should be done
with great care as specifying a value that is excessively high may prevent your system from booting.

[[Category:FAQ]] [[Category:Windows]]

== Windows version-specific issues ==

==== Can I install a 32-bit PostgreSQL on 64-bit Windows? ====

Recent 32-bit versions of PostgreSQL (8.3 and newer) can be installed and used on 64-bit Windows XP and above,
though they retain the 32-bit limits on maximum process address space (and thus shared memory).

You can connect to the 32-bit postgresql server from 64-bit programs on the computer the server is running on
or other computers if a 64-bit libpq or psqlODBC driver is installed where the program is running.

Because 32-bit versions of the PostgreSQL server only install a 32-bit libpq and pgsqlODBC, only 32-bit programs
on the computer the server was installed on can use the database unless a 64-bit ODBC driver or libpq
is installed as an add-on.

==== Where is the PostgreSQL ODBC driver? I'm running 32-bit PostgreSQL on 64-bit Windows ====

You need to use the 32-bit ODBC administrator to set up data sources for 32-bit
applications using 32-bit drivers.

Unless you've also installed a [[#What about 64-bit ODBC drivers?|64-bit version]] of
[http://psqlodbc.projects.postgresql.org psqlODBC], a 32-bit install of PostgreSQL will
only have a 32-bit ODBC driver. The 32-bit ODBC driver may only be used by 32-bit programs,
and ''will not show up in the 64-bit ODBC administrator''.

This gets confusing because on 64-bit windows <code>c:\windows\system32\odbcad32</code> is the ''64-bit''
ODBC driver administrator, despite the name. This is a historical artifact of Windows development.
Apparently many apps and installers depend on odbcad32.exe having that name and path,
so Microsoft landed up being stuck with it despite the now-stupid name, which made sense back
in the 16- to 32-bit transition but makes none now. It's the same reason the
"system32" directory is still called that on 64-bit Windows. PostgreSQL can't do anything about this.

See: [http://support.microsoft.com/kb/942976 http://support.microsoft.com/kb/942976]

You'll see in that article that the 32-bit ODBC administrator on 64-bit Windows is:

<pre>
%systemdrive%\Windows\SysWoW64\odbcad32.exe
</pre>

You can launch this from "Start->Run" using the path above. You will see the PostgreSQL ODBC drivers in the
32-bit ODBC administrator.

You 'can not' use a 32-bit ODBC driver in a 64-bit application. That means that you'll still only be
able to use the PostgreSQL ODBC driver with 32-bit applications unless you install a 64-bit ODBC driver
as well.

==== Can I use a 64-bit ODBC program with a 32-bit PostgreSQL server? ====

Only if you have a 64-bit [http://psqlodbc.projects.postgresql.org|psqlODBC] driver installed. See the installation section.

Running & Installing PostgreSQL On Native Windows

2012-06-21T23:28:50Z

Gabrielle: /* Can I install PostgreSQL on a FAT partition? */

{{Languages}}

== Supported Platforms ==
=== What versions of Windows does PostgreSQL run on?===

PostgreSQL is supported on Windows XP and above, at least as of version 9.0. It will run on 32 and 64 bit systems.

Versions of the server are not tested on new operating system versions that are released after a newer major version of the server was released. For example, Windows 7 was released after PostgreSQL 8.4, so PostgreSQL 8.3 will not be supported on it. Similarly, when the upcoming RHEL 6 is released, only PostgreSQL 9.0.x will be supported on it. We aim to support new versions of Windows in the PostgreSQL major version following their release at the latest.

For information about platforms supported by the One-click installer, please see the installer download page, off the main [http://www.postgresql.org/download/windows download page for windows].

For information on non-Windows platforms see the [[FAQ|main FAQ]] and the [http://www.postgresql.org/download/ main download page].

=== What Windows platforms are NOT supported? ===

The PostgreSQL installers are not tested or supported on:

* Windows XP Embedded
* Windows 2000
* Windows NT 4
* Windows NT 3.5.x
* Windows 95/98/ME/3.x
* Windows CE
* Windows Mobile

These platforms are not supported. Please do not ask the mailing list for help with any of these platforms.

Please read the troubleshooting notes on [[Troubleshooting Installation#Installation fails on windows embedded|installation on embedded versions of windows]] for some more information about embedded windows.

=== I heard that NT4 and Windows 2000 are supported. Is that true? ===
Although not officially supported, PostgreSQL may run on Windows NT4 and Windows 2000
with a few minor issues including:
* The installer may not work correctly, thus you will need to install PostgreSQL manually from the binary .zip release, or compile it yourself.
* PostgreSQL uses a feature in the NTFS filesystem called 'reparse points' to implement tablespaces. Reparse points are not available in NT4, hence tablespaces cannot be used on NT4.
* There is no 'runas.exe' included in Windows NT4 as standard, making it difficult to start PostgreSQL from an administrative account.
It should also be noted that very little testing has been done on NT4.
* No testing is done on Windows NT 4 or Windows 2000, so newer versions may not work on these platforms.

Please do not ask for help with these obsolete platforms on the mailing list. Some of the [http://www.postgresql.org/support/professional_support professional support] companies may be able to assist you, though.

=== What about Windows 95/98/ME? ===

PostgreSQL requires functionality that is not available on these
platforms and will not run on them. If you need to run PostgreSQL
on these platforms, you can look at the
[http://www.postgresql.org/files/documentation/faqs/text/FAQ_CYGWIN Cygwin]
port, which has basic support for 9x platforms.

=== Is there a 64-bit build of PostgreSQL for Windows? ===

Yes. A [[64bit Windows port]] was released for [[PostgreSQL 9.0]].

32-bit builds of previous versions of PostgreSQL generally run fine on 64-bit Windows. Though they cannot practically use more than about 1GB of shared_buffers directly, they can still benefit from more than 4GB of memory because the Windows kernel will use that memory to cache disk reads.

=== What about 64-bit ODBC drivers? ===

At time of writing there was 64-bit support in the [http://psqlodbc.projects.postgresql.org/ psqlODBC] source code, but no official binary releases of 64-bit ODBC drivers. Check the psqlODBC website for details.

== Installation ==

=== What do I need to install PostgreSQL on Windows? ===

See [http://www.postgresql.org/download/windows the PostgreSQL for Windows download page] for various ways to download and install PostgreSQL on Windows.

The easiest way to install PostgreSQL on Windows is with the
One Click installer package maintained by EnterpriseDB, which you can get from the page linked to above. This will install PostgreSQL along with
pgAdmin (a graphical administration and management program), a selection of 'contrib' modules to provide additional specialised functionality, and a choice of procedural languages. A program called StackBuilder will be installed to help you download and install any additional components, like ODBC or JDBC drivers, that you may need.

=== What do I need to compile PostgreSQL from source code? ===

See the [http://www.postgresql.org/docs/current/static/install-windows.html documentation]
for instructions on how to compile PostgreSQL for windows, including details about supported compilers and tools.

=== Why do I need a non-administrator account to run PostgreSQL under? ===

When a hacker gains entry to a computer using a software bug in a
package, she gains the permissions of the user account under which the
service is run. Whilst we do not know of any such bugs in PostgreSQL,
we enforce the use of a non-administrative service account to minimise
the possible damage that a hacker could do should they find and utilise
a bug in PostgreSQL to hack the system.

This has long been common practice in the Unix world, and is starting to
become standard practice in the Windows world as well as Microsoft and
other vendors work to improve the security of their systems.

Note, that with the release of PostgreSQL 8.2, it is possible to run under
a administrative account. PostgreSQL 8.2 and above are able to irrevocably
give up administrative rights at startup, thus ensuring the rest of the
system remains secure in the extremely unlikely event that PostgreSQL
becomes compromised.

=== Can I install PostgreSQL on a FAT partition? ===

Use of PostgreSQL on FAT32 file systems is not supported or tested, because
FAT32 is a terrible file system on which to run any database.

PostgreSQL's number one priority is the integrity of your data. FAT and
FAT32 filesystems simply do not offer the reliability or crash-safety required.
In addition, the lack of security features offered by FAT make it
impossible to secure the raw data files from unauthorised modification.
Finally, PostgreSQL utilises a feature called 'reparse points' to
implement tablespaces. This feature is not available on FAT partitions.

The NTFS file system is a journalled filesystem offering much better
reliability and crash recovery. In addition, it has a comprehensive
access control system and offers the reparse point functionality used
by PostgreSQL.

For this reason, the PostgreSQL installer package will not initialise
a database cluster on anything but an NTFS partition. The server and
utilities may be installed on any partition type.

It is recognised however, that in rare cases FAT partitions may be the only choice.
In such cases, you can simply install PostgreSQL as normal, but without initialising the
database cluster. When the installation has finished, manually run
the 'initdb.exe' program on the FAT partition. Security and
reliability will be compromised however, and any attempts to create
tablespaces will fail. Do not use PostgreSQL on FAT32 in production.

=== What filesystem permissions does PostgreSQL require? ===
The PostgreSQL service account needs ''read'' permissions on
all directories leading up to the service directory. It needs ''write'' permissions ''only''
on the data directory. Specifically, it should ''not'' be granted anything other than ''read''
permissions on the directories containing binary files. (All directories below the installation
directory are set by the installer, so unless you change something, there should be no problem with this).

PostgreSQL also needs ''read'' permissions on system DLL files like kernel32.dll and user32.dll
(among others), which is normally granted by default, and on the CMD.EXE binary, which may in some
scenarios be locked down and need opening.

If you are running PostgreSQL on a multi-user system, you should remove the permissions from all
non-administrative users from the PostgreSQL directories. No user ''ever'' needs permissions on the
PostgreSQL files - all communication is done through the libpq connection. Direct access to data files
can lead to information disclosure or system instability!

=== Why can't I select Unicode as an encoding? ===

Starting with PostgreSQL 8.1, the UTF-8 unicode encoding is fully supported on Windows. The Unicode ODBC driver supports UTF-16, and the JDBC driver also has full unicode support.

The PostgreSQL server does not support the 2-byte UTF-16 or 4-byte UTF-32 Unicode encodings for internal data storage or on-the-wire communication. Beause UTF-16 is the default encoding on Windows, and what people on Windows usually mean when they say "Unicode", you might expect this to be a problem, but in practice it's fine, as the ODBC and JDBC drivers take care of this. Programs using libpq directly need to be aware of this, but not much else does.

=== I installed in a non-english language, but all messages show up in english! ===
The language choice made during the installation only selects which language is used by the installer. To
change the language of the messages of the installed product, make sure you have installed the ''National language
support'' feature. Then edit your postgresql.conf file and change the value of the ''lc_messages'' parameter
to the language you want.

== Common installation errors ==

=== PostgreSQL and/or the installer crashes at startup, fails to start or hangs on start ===

By far most common reasons for installation and runtime problems with PostgreSQL on Windows are Windows Scripting Host issues, antivirus software problems and 3rd-party (non-Microsoft) software firewalls. People also sometimes have trouble with the postgres service account password.

The following articles cover these issues. Please read them and follow their instructions before asking for help with installer problems.

==== Antivirus software ====

If you have any antivirus software installed, you '''must''' exclude the data directories that are to be used by PostgreSQL and '''must''' exclude postgresql.exe process. If that still does not help, it may be required to completely uninstall the antivirus software from the machine.

Antivirus software can interfere with PostgreSQL's operation, because PostgreSQL requires file access commands in Windows to behave exactly as documented by Microsoft, and many antivirus programs contain errors or accidental behavior changes that cause these commands to misbehave subtly. Most programs do not care because they access files in fairly simple ways. Because PostgreSQL is continuously reading from and writing to the same set of files from multiple processes, it tends to trigger programming and design mistakes in antivirus software, particularly problems related to concurrency. Such problems can cause random and unpredictable errors, or even data corruption.

Antivirus software is also likely to dramatically slow down PostgreSQL's operation. For that reason, you should at least exclude postgres.exe and the data directories so the scanner ignores them.

===== What Anti-Virus software is compatible? =====

The systems used to build the Windows installers all run either Sophos AV or AVG Free Edition, and
those systems pass a full set of PostgreSQL regression tests running those programs.
Microsoft Security Essentials is also known to work.

Specific issues have been reported with the ''nod32'' antivirus
product. If you are using this product, add "postmaster.exe" to the list
of excluded processes (available under advanced options). This has been
reported to fix the problem.

Specific issues have also been reported with McAfee and Panda anti-virus
software and NetLimiter network monitoring software. While some people do have
PostgreSQL working with these software packages, there is no specific or even
recommend solutions that have not worked in some cases, so the issues would appear
to be installation specific, sometimes even requiring uninstallation.

==== Software firewalls ====

If you have any 3rd-party firewall software installed on your machine, try either disabling it or uninstalling it. There's really no need for 3rd party firewalls on Windows XP and above, as the built-in firewall provided by Microsoft does an excellent job already. Some badly-written 3rd party firewalls do not uninstall correctly, so after uninstallation you might have to [http://support.microsoft.com/kb/299357 tell Windows to repair its network settings].

If you had a 3rd-party firewall and have now uninstalled it, make sure to turn Windows Firewall back on, as many products turn it off during installation and fail to turn it back on during uninstallation.

==== The installer exits with a runtime installation error? ====

The installer may exit with an error like: ''An error occured executing the Microsoft VC++ runtime installer''. This can only happen on Windows.

There are two main reasons why this may occur:

1) The Windows Scripting Host is unable to execute VBscripts. This can occur if the scripting host is disabled (which is unusual), or if the installation is broken. A sign of this problem is a message like ''CScript Error: Can't find script engine "VBScript" for script "C:\...''. It can often be resolved by re-registering the VBscript interpreter - click ''Start'' -> ''Run'' and enter the following and click ''OK'':

regsvr32 %systemroot%\system32\vbscript.dll

If that fails, on older versions of Windows you can try [http://www.microsoft.com/downloads/en/results.aspx?freetext=windows+script+host&displaylang=en&stype=s_basic updating the scripting host].

2) The installer is unable to properly read and write files to the system ''TEMP'' directory. This can occur if the ''TEMP'' or ''TMP'' environment variables are set to non-standard values, and can be recognised by errors in the logfile indicating that scripts could not be executed or found. To resolve this issue, ensure the ''TEMP'' and ''TMP'' variables are set to their correct values.

==== Trouble with passwords for the postgres user ====

Dave Page wrote a [http://pgsnake.blogspot.com/2010/07/postgresql-passwords-and-installers.html blog post] explaining what the different passwords are used for, and how to overcome common problems such as resetting them.

==== PATH environment variable ====

There is also an issue if you have installed ''cygwin'', and the cygwin\bin directory is present
in the system PATH variable. There are DLL files in the cygwin directory related to interpreted languages (TCL,
perl, python) that contain bugs that can cause the installer or the installed version of PostgreSQL to either hang
or crash. Remove the cygwin\bin directory from your path before running the installer!

Problems have also been observed when the PATH environment variable contains directories containing versions of libssl and/or libintl.

==== I'm getting permissions errors when installing/running initdb ====

Make sure the PostgreSQL service account has permissions on the directories leading up to the one
you have installed into. The installer will set permissions on the install directory but not on
parent directories of it.

You may also see related errors show up as The database Cluster initialisation failed during the One Click installer. Check your install-postgresql log
but it is usually related to permission errors. The following thread may help,

http://forums.enterprisedb.com/posts/list/2044.page#7503

Or alternatively, you can fix up the directory permissions and then manually restart the initcluster.vbs script like this for v9,

cscript //NoLogo "<install_path>/installer/server/initcluster.vbs" "postgres" "postgres" "<password>" "<install_path>" "<data_path>" 5432 "DEFAULT"

==== The installer claims the specified account is an administrator, but it isn't! ====

Most likely, the specified account is an administrator or power user,
even though you aren't aware of it. The check used by the installer
specifically checks for membership in the Administrators or
Power Users group. Work your way backwards using Local Users and Groups -
open the Administrators group, see who's a member. Then check any
groups (domain or local) that are a member of the Administrators group,
and any groups members of that group etc. PostgreSQL checks any level
of nested groups.

==== I'm getting an error message that says PostgreSQL cannot be installed from a Terminal Services session ====

This is unfortunately so. The PostgreSQL backend won't run from a TS session, and in order to do initdb the installer
has to start a standalone backend. Therefore, installation has to be performed from the console. Note that if you are
using Windows Server 2003, you can get remote access to the actual console and not just an administrative session.
To do this, start the Remote Desktop Connection by executing mstsc /console, and then connect as usual.
This will lock the local console of the server and give you control over that session. In this scenario,
PostgreSQL should install just fine.

==== I get the error "the user has not been granted the requested logon type at this computer" or similar ====

Make sure the specified PostgreSQL account has the "Log on as a service"
and "Log on locally" rights. The "Log on locally" is only required for
the install part, and can be removed once the installation is completed
if security policies require it. (Rights are granted and revoked using
the "Local Security Policy" MMC snapin. "Log on locally" is default,
and "Log on as a service" will normally be granted automatically by
the installer).

If you still have this problem, enable auditing (also using
the "Local Security Policy" snapin) and let us know what other rights
were required in your setup.

Note that if your computer is a member of a domain, the settings of
the security policies may be controlled at the domain level using
Group Policy.

==== How do I delete the service account - it's not listed under users! ====

Windows sometimes hide some accounts from the GUI tools, so they cannot be removed from there. This includes
the auto-created service account for PostgreSQL (that may be left over from a previous installation). To delete this
account, use the NET command on the commandline:
NET USER <username> /DELETE
Where <username> is the windows login name of the user, for example ''postgres''.

== Common runtime issues ==

=== I'm getting "dynamic load error" when installing a procedural language ===

Most commonly this means that the actual language DLL for the procedural language is missing. The PostgreSQL
DLLs only contains the language bindings, and require the language distribution DLLs to be present
in the system PATH. For a list of the current required DLLs for the different procedural languages,
please see [http://pginstaller.projects.postgresql.org the installation instructions].

To find out exactly which DLL files are missing, you can use the ''depends'' tool from Microsoft.
It is available in the Windows Support Tools, that are on the Windows CD as a separate install. Just run
''depends plpython.dll'' (for PL/python) to show which imports are missing.

=== I'm seeing a lot of postgres.exe processes even though I only started the server once ===

This is normal. PostgreSQL uses a multi-process architecture. In an empty system you will see anything from two to
five processes. Once clients start to connect, the number of processes will increase.

=== How do I set an environment variable? ===

PostgreSQL uses environment variables for several settings. To change an environment variable in most
Windows versions, go into Properties for My Computer, then into Advanced. Note that there are two sets of
environment variables - one for the system which applies to all users and one for the current user. If you
want an environment variable to affect the PostgreSQL service, you must change the system variable. After
changing a system variable, you must restart the service.

=== I cannot run with more than about 125 connections at once, despite having capable hardware ===

When running as a service, you may experience failures with more than approximately 125 simultaneous connections.
This can happen because some of the libraries that PostgreSQL is dependent on are dependent on user32.dll which allocates
memory from an area known as the Desktop Heap. The desktop heap is assigned to each logon session, with non-interactive
sessions typically being assigned 512KB. Each postgres process that runs typically consumes approximately 3.2KB of desktop
heap, which coupled with other overhead can exhaust the allocated heap at somewhere around 125 connections. This doesn't
happen when running from the command line (or more precisely, happens with much higher numbers of connections) because the
interactive logon session is typically allocated 3MB of Desktop Heap.

You can increase the non-interactive Desktop Heap by modifying the third SharedSection value in the registry as described
in this [http://support.microsoft.com/kb/184802 Microsoft Knowledgebase article]. Note that this should be done
with great care as specifying a value that is excessively high may prevent your system from booting.

[[Category:FAQ]] [[Category:Windows]]

== Windows version-specific issues ==

==== Can I install a 32-bit PostgreSQL on 64-bit Windows? ====

Recent 32-bit versions of PostgreSQL (8.3 and newer) can be installed and used on 64-bit Windows XP and above,
though they retain the 32-bit limits on maximum process address space (and thus shared memory).

You can connect to the 32-bit postgresql server from 64-bit programs on the computer the server is running on
or other computers if a 64-bit libpq or psqlODBC driver is installed where the program is running.

Because 32-bit versions of the PostgreSQL server only install a 32-bit libpq and pgsqlODBC, only 32-bit programs
on the computer the server was installed on can use the database unless a 64-bit ODBC driver or libpq
is installed as an add-on.

==== Where is the PostgreSQL ODBC driver? I'm running 32-bit PostgreSQL on 64-bit Windows ====

You need to use the 32-bit ODBC administrator to set up data sources for 32-bit
applications using 32-bit drivers.

Unless you've also installed a [[#What about 64-bit ODBC drivers?|64-bit version]] of
[http://psqlodbc.projects.postgresql.org psqlODBC], a 32-bit install of PostgreSQL will
only have a 32-bit ODBC driver. The 32-bit ODBC driver may only be used by 32-bit programs,
and ''will not show up in the 64-bit ODBC administrator''.

This gets confusing because on 64-bit windows <code>c:\windows\system32\odbcad32</code> is the ''64-bit''
ODBC driver administrator, despite the name. This is a historical artifact of Windows development.
Apparently many apps and installers depend on odbcad32.exe having that name and path,
so Microsoft landed up being stuck with it despite the now-stupid name, which made sense back
in the 16- to 32-bit transition but makes none now. It's the same reason the
"system32" directory is still called that on 64-bit Windows. PostgreSQL can't do anything about this.

See: [http://support.microsoft.com/kb/942976 http://support.microsoft.com/kb/942976]

You'll see in that article that the 32-bit ODBC administrator on 64-bit Windows is:

<pre>
%systemdrive%\Windows\SysWoW64\odbcad32.exe
</pre>

You can launch this from "Start->Run" using the path above. You will see the PostgreSQL ODBC drivers in the
32-bit ODBC administrator.

You 'can not' use a 32-bit ODBC driver in a 64-bit application. That means that you'll still only be
able to use the PostgreSQL ODBC driver with 32-bit applications unless you install a 64-bit ODBC driver
as well.

==== Can I use a 64-bit ODBC program with a 32-bit PostgreSQL server? ====

Only if you have a 64-bit [http://psqlodbc.projects.postgresql.org|psqlODBC] driver installed. See the installation section.

Running & Installing PostgreSQL On Native Windows

2012-06-21T23:27:16Z

Gabrielle: /* Why do I need a non-administrator account to run PostgreSQL under? */ move some commas around

{{Languages}}

== Supported Platforms ==
=== What versions of Windows does PostgreSQL run on?===

PostgreSQL is supported on Windows XP and above, at least as of version 9.0. It will run on 32 and 64 bit systems.

Versions of the server are not tested on new operating system versions that are released after a newer major version of the server was released. For example, Windows 7 was released after PostgreSQL 8.4, so PostgreSQL 8.3 will not be supported on it. Similarly, when the upcoming RHEL 6 is released, only PostgreSQL 9.0.x will be supported on it. We aim to support new versions of Windows in the PostgreSQL major version following their release at the latest.

For information about platforms supported by the One-click installer, please see the installer download page, off the main [http://www.postgresql.org/download/windows download page for windows].

For information on non-Windows platforms see the [[FAQ|main FAQ]] and the [http://www.postgresql.org/download/ main download page].

=== What Windows platforms are NOT supported? ===

The PostgreSQL installers are not tested or supported on:

* Windows XP Embedded
* Windows 2000
* Windows NT 4
* Windows NT 3.5.x
* Windows 95/98/ME/3.x
* Windows CE
* Windows Mobile

These platforms are not supported. Please do not ask the mailing list for help with any of these platforms.

Please read the troubleshooting notes on [[Troubleshooting Installation#Installation fails on windows embedded|installation on embedded versions of windows]] for some more information about embedded windows.

=== I heard that NT4 and Windows 2000 are supported. Is that true? ===
Although not officially supported, PostgreSQL may run on Windows NT4 and Windows 2000
with a few minor issues including:
* The installer may not work correctly, thus you will need to install PostgreSQL manually from the binary .zip release, or compile it yourself.
* PostgreSQL uses a feature in the NTFS filesystem called 'reparse points' to implement tablespaces. Reparse points are not available in NT4, hence tablespaces cannot be used on NT4.
* There is no 'runas.exe' included in Windows NT4 as standard, making it difficult to start PostgreSQL from an administrative account.
It should also be noted that very little testing has been done on NT4.
* No testing is done on Windows NT 4 or Windows 2000, so newer versions may not work on these platforms.

Please do not ask for help with these obsolete platforms on the mailing list. Some of the [http://www.postgresql.org/support/professional_support professional support] companies may be able to assist you, though.

=== What about Windows 95/98/ME? ===

PostgreSQL requires functionality that is not available on these
platforms and will not run on them. If you need to run PostgreSQL
on these platforms, you can look at the
[http://www.postgresql.org/files/documentation/faqs/text/FAQ_CYGWIN Cygwin]
port, which has basic support for 9x platforms.

=== Is there a 64-bit build of PostgreSQL for Windows? ===

Yes. A [[64bit Windows port]] was released for [[PostgreSQL 9.0]].

32-bit builds of previous versions of PostgreSQL generally run fine on 64-bit Windows. Though they cannot practically use more than about 1GB of shared_buffers directly, they can still benefit from more than 4GB of memory because the Windows kernel will use that memory to cache disk reads.

=== What about 64-bit ODBC drivers? ===

At time of writing there was 64-bit support in the [http://psqlodbc.projects.postgresql.org/ psqlODBC] source code, but no official binary releases of 64-bit ODBC drivers. Check the psqlODBC website for details.

== Installation ==

=== What do I need to install PostgreSQL on Windows? ===

See [http://www.postgresql.org/download/windows the PostgreSQL for Windows download page] for various ways to download and install PostgreSQL on Windows.

The easiest way to install PostgreSQL on Windows is with the
One Click installer package maintained by EnterpriseDB, which you can get from the page linked to above. This will install PostgreSQL along with
pgAdmin (a graphical administration and management program), a selection of 'contrib' modules to provide additional specialised functionality, and a choice of procedural languages. A program called StackBuilder will be installed to help you download and install any additional components, like ODBC or JDBC drivers, that you may need.

=== What do I need to compile PostgreSQL from source code? ===

See the [http://www.postgresql.org/docs/current/static/install-windows.html documentation]
for instructions on how to compile PostgreSQL for windows, including details about supported compilers and tools.

=== Why do I need a non-administrator account to run PostgreSQL under? ===

When a hacker gains entry to a computer using a software bug in a
package, she gains the permissions of the user account under which the
service is run. Whilst we do not know of any such bugs in PostgreSQL,
we enforce the use of a non-administrative service account to minimise
the possible damage that a hacker could do should they find and utilise
a bug in PostgreSQL to hack the system.

This has long been common practice in the Unix world, and is starting to
become standard practice in the Windows world as well as Microsoft and
other vendors work to improve the security of their systems.

Note, that with the release of PostgreSQL 8.2, it is possible to run under
a administrative account. PostgreSQL 8.2 and above are able to irrevocably
give up administrative rights at startup, thus ensuring the rest of the
system remains secure in the extremely unlikely event that PostgreSQL
becomes compromised.

=== Can I install PostgreSQL on a FAT partition? ===

Use of PostgreSQL on FAT32 file systems is not supported or tested, because
FAT32 is a terrible file system to run any database on.

PostgreSQL's number one priority is the integrity of your data. FAT and
FAT32 filesystems simply do not offer the reliability or crash-safety required.
In addition, the lack of security features offered by FAT make it
impossible to secure the raw data files from unauthorised modification.
Finally, PostgreSQL utilises a feature called 'reparse points' to
implement tablespaces. This feature is not available on FAT partitions.

The NTFS file system is a journalled filesystem offering much better
reliability and crash recovery. In addition, it has a comprehensive
access control system and offers the reparse point functionality used
by PostgreSQL.

For this reason, the PostgreSQL installer package will not initialise
a database cluster on anything but an NTFS partition. The server and
utilities may be installed on any partition type.

It is recognised however, that in rare cases FAT partitions may be the only choice.
In such cases, you can simply install PostgreSQL as normal, but without initialising the
database cluster. When the installation has finished, manually run
the 'initdb.exe' program on the FAT partition. Security and
reliability will be compromised however, and any attempts to create
tablespaces will fail. Do not use PostgreSQL on FAT32 in production.

=== What filesystem permissions does PostgreSQL require? ===
The PostgreSQL service account needs ''read'' permissions on
all directories leading up to the service directory. It needs ''write'' permissions ''only''
on the data directory. Specifically, it should ''not'' be granted anything other than ''read''
permissions on the directories containing binary files. (All directories below the installation
directory are set by the installer, so unless you change something, there should be no problem with this).

PostgreSQL also needs ''read'' permissions on system DLL files like kernel32.dll and user32.dll
(among others), which is normally granted by default, and on the CMD.EXE binary, which may in some
scenarios be locked down and need opening.

If you are running PostgreSQL on a multi-user system, you should remove the permissions from all
non-administrative users from the PostgreSQL directories. No user ''ever'' needs permissions on the
PostgreSQL files - all communication is done through the libpq connection. Direct access to data files
can lead to information disclosure or system instability!

=== Why can't I select Unicode as an encoding? ===

Starting with PostgreSQL 8.1, the UTF-8 unicode encoding is fully supported on Windows. The Unicode ODBC driver supports UTF-16, and the JDBC driver also has full unicode support.

The PostgreSQL server does not support the 2-byte UTF-16 or 4-byte UTF-32 Unicode encodings for internal data storage or on-the-wire communication. Beause UTF-16 is the default encoding on Windows, and what people on Windows usually mean when they say "Unicode", you might expect this to be a problem, but in practice it's fine, as the ODBC and JDBC drivers take care of this. Programs using libpq directly need to be aware of this, but not much else does.

=== I installed in a non-english language, but all messages show up in english! ===
The language choice made during the installation only selects which language is used by the installer. To
change the language of the messages of the installed product, make sure you have installed the ''National language
support'' feature. Then edit your postgresql.conf file and change the value of the ''lc_messages'' parameter
to the language you want.

== Common installation errors ==

=== PostgreSQL and/or the installer crashes at startup, fails to start or hangs on start ===

By far most common reasons for installation and runtime problems with PostgreSQL on Windows are Windows Scripting Host issues, antivirus software problems and 3rd-party (non-Microsoft) software firewalls. People also sometimes have trouble with the postgres service account password.

The following articles cover these issues. Please read them and follow their instructions before asking for help with installer problems.

==== Antivirus software ====

If you have any antivirus software installed, you '''must''' exclude the data directories that are to be used by PostgreSQL and '''must''' exclude postgresql.exe process. If that still does not help, it may be required to completely uninstall the antivirus software from the machine.

Antivirus software can interfere with PostgreSQL's operation, because PostgreSQL requires file access commands in Windows to behave exactly as documented by Microsoft, and many antivirus programs contain errors or accidental behavior changes that cause these commands to misbehave subtly. Most programs do not care because they access files in fairly simple ways. Because PostgreSQL is continuously reading from and writing to the same set of files from multiple processes, it tends to trigger programming and design mistakes in antivirus software, particularly problems related to concurrency. Such problems can cause random and unpredictable errors, or even data corruption.

Antivirus software is also likely to dramatically slow down PostgreSQL's operation. For that reason, you should at least exclude postgres.exe and the data directories so the scanner ignores them.

===== What Anti-Virus software is compatible? =====

The systems used to build the Windows installers all run either Sophos AV or AVG Free Edition, and
those systems pass a full set of PostgreSQL regression tests running those programs.
Microsoft Security Essentials is also known to work.

Specific issues have been reported with the ''nod32'' antivirus
product. If you are using this product, add "postmaster.exe" to the list
of excluded processes (available under advanced options). This has been
reported to fix the problem.

Specific issues have also been reported with McAfee and Panda anti-virus
software and NetLimiter network monitoring software. While some people do have
PostgreSQL working with these software packages, there is no specific or even
recommend solutions that have not worked in some cases, so the issues would appear
to be installation specific, sometimes even requiring uninstallation.

==== Software firewalls ====

If you have any 3rd-party firewall software installed on your machine, try either disabling it or uninstalling it. There's really no need for 3rd party firewalls on Windows XP and above, as the built-in firewall provided by Microsoft does an excellent job already. Some badly-written 3rd party firewalls do not uninstall correctly, so after uninstallation you might have to [http://support.microsoft.com/kb/299357 tell Windows to repair its network settings].

If you had a 3rd-party firewall and have now uninstalled it, make sure to turn Windows Firewall back on, as many products turn it off during installation and fail to turn it back on during uninstallation.

==== The installer exits with a runtime installation error? ====

The installer may exit with an error like: ''An error occured executing the Microsoft VC++ runtime installer''. This can only happen on Windows.

There are two main reasons why this may occur:

1) The Windows Scripting Host is unable to execute VBscripts. This can occur if the scripting host is disabled (which is unusual), or if the installation is broken. A sign of this problem is a message like ''CScript Error: Can't find script engine "VBScript" for script "C:\...''. It can often be resolved by re-registering the VBscript interpreter - click ''Start'' -> ''Run'' and enter the following and click ''OK'':

regsvr32 %systemroot%\system32\vbscript.dll

If that fails, on older versions of Windows you can try [http://www.microsoft.com/downloads/en/results.aspx?freetext=windows+script+host&displaylang=en&stype=s_basic updating the scripting host].

2) The installer is unable to properly read and write files to the system ''TEMP'' directory. This can occur if the ''TEMP'' or ''TMP'' environment variables are set to non-standard values, and can be recognised by errors in the logfile indicating that scripts could not be executed or found. To resolve this issue, ensure the ''TEMP'' and ''TMP'' variables are set to their correct values.

==== Trouble with passwords for the postgres user ====

Dave Page wrote a [http://pgsnake.blogspot.com/2010/07/postgresql-passwords-and-installers.html blog post] explaining what the different passwords are used for, and how to overcome common problems such as resetting them.

==== PATH environment variable ====

There is also an issue if you have installed ''cygwin'', and the cygwin\bin directory is present
in the system PATH variable. There are DLL files in the cygwin directory related to interpreted languages (TCL,
perl, python) that contain bugs that can cause the installer or the installed version of PostgreSQL to either hang
or crash. Remove the cygwin\bin directory from your path before running the installer!

Problems have also been observed when the PATH environment variable contains directories containing versions of libssl and/or libintl.

==== I'm getting permissions errors when installing/running initdb ====

Make sure the PostgreSQL service account has permissions on the directories leading up to the one
you have installed into. The installer will set permissions on the install directory but not on
parent directories of it.

You may also see related errors show up as The database Cluster initialisation failed during the One Click installer. Check your install-postgresql log
but it is usually related to permission errors. The following thread may help,

http://forums.enterprisedb.com/posts/list/2044.page#7503

Or alternatively, you can fix up the directory permissions and then manually restart the initcluster.vbs script like this for v9,

cscript //NoLogo "<install_path>/installer/server/initcluster.vbs" "postgres" "postgres" "<password>" "<install_path>" "<data_path>" 5432 "DEFAULT"

==== The installer claims the specified account is an administrator, but it isn't! ====

Most likely, the specified account is an administrator or power user,
even though you aren't aware of it. The check used by the installer
specifically checks for membership in the Administrators or
Power Users group. Work your way backwards using Local Users and Groups -
open the Administrators group, see who's a member. Then check any
groups (domain or local) that are a member of the Administrators group,
and any groups members of that group etc. PostgreSQL checks any level
of nested groups.

==== I'm getting an error message that says PostgreSQL cannot be installed from a Terminal Services session ====

This is unfortunately so. The PostgreSQL backend won't run from a TS session, and in order to do initdb the installer
has to start a standalone backend. Therefore, installation has to be performed from the console. Note that if you are
using Windows Server 2003, you can get remote access to the actual console and not just an administrative session.
To do this, start the Remote Desktop Connection by executing mstsc /console, and then connect as usual.
This will lock the local console of the server and give you control over that session. In this scenario,
PostgreSQL should install just fine.

==== I get the error "the user has not been granted the requested logon type at this computer" or similar ====

Make sure the specified PostgreSQL account has the "Log on as a service"
and "Log on locally" rights. The "Log on locally" is only required for
the install part, and can be removed once the installation is completed
if security policies require it. (Rights are granted and revoked using
the "Local Security Policy" MMC snapin. "Log on locally" is default,
and "Log on as a service" will normally be granted automatically by
the installer).

If you still have this problem, enable auditing (also using
the "Local Security Policy" snapin) and let us know what other rights
were required in your setup.

Note that if your computer is a member of a domain, the settings of
the security policies may be controlled at the domain level using
Group Policy.

==== How do I delete the service account - it's not listed under users! ====

Windows sometimes hide some accounts from the GUI tools, so they cannot be removed from there. This includes
the auto-created service account for PostgreSQL (that may be left over from a previous installation). To delete this
account, use the NET command on the commandline:
NET USER <username> /DELETE
Where <username> is the windows login name of the user, for example ''postgres''.

== Common runtime issues ==

=== I'm getting "dynamic load error" when installing a procedural language ===

Most commonly this means that the actual language DLL for the procedural language is missing. The PostgreSQL
DLLs only contains the language bindings, and require the language distribution DLLs to be present
in the system PATH. For a list of the current required DLLs for the different procedural languages,
please see [http://pginstaller.projects.postgresql.org the installation instructions].

To find out exactly which DLL files are missing, you can use the ''depends'' tool from Microsoft.
It is available in the Windows Support Tools, that are on the Windows CD as a separate install. Just run
''depends plpython.dll'' (for PL/python) to show which imports are missing.

=== I'm seeing a lot of postgres.exe processes even though I only started the server once ===

This is normal. PostgreSQL uses a multi-process architecture. In an empty system you will see anything from two to
five processes. Once clients start to connect, the number of processes will increase.

=== How do I set an environment variable? ===

PostgreSQL uses environment variables for several settings. To change an environment variable in most
Windows versions, go into Properties for My Computer, then into Advanced. Note that there are two sets of
environment variables - one for the system which applies to all users and one for the current user. If you
want an environment variable to affect the PostgreSQL service, you must change the system variable. After
changing a system variable, you must restart the service.

=== I cannot run with more than about 125 connections at once, despite having capable hardware ===

When running as a service, you may experience failures with more than approximately 125 simultaneous connections.
This can happen because some of the libraries that PostgreSQL is dependent on are dependent on user32.dll which allocates
memory from an area known as the Desktop Heap. The desktop heap is assigned to each logon session, with non-interactive
sessions typically being assigned 512KB. Each postgres process that runs typically consumes approximately 3.2KB of desktop
heap, which coupled with other overhead can exhaust the allocated heap at somewhere around 125 connections. This doesn't
happen when running from the command line (or more precisely, happens with much higher numbers of connections) because the
interactive logon session is typically allocated 3MB of Desktop Heap.

You can increase the non-interactive Desktop Heap by modifying the third SharedSection value in the registry as described
in this [http://support.microsoft.com/kb/184802 Microsoft Knowledgebase article]. Note that this should be done
with great care as specifying a value that is excessively high may prevent your system from booting.

[[Category:FAQ]] [[Category:Windows]]

== Windows version-specific issues ==

==== Can I install a 32-bit PostgreSQL on 64-bit Windows? ====

Recent 32-bit versions of PostgreSQL (8.3 and newer) can be installed and used on 64-bit Windows XP and above,
though they retain the 32-bit limits on maximum process address space (and thus shared memory).

You can connect to the 32-bit postgresql server from 64-bit programs on the computer the server is running on
or other computers if a 64-bit libpq or psqlODBC driver is installed where the program is running.

Because 32-bit versions of the PostgreSQL server only install a 32-bit libpq and pgsqlODBC, only 32-bit programs
on the computer the server was installed on can use the database unless a 64-bit ODBC driver or libpq
is installed as an add-on.

==== Where is the PostgreSQL ODBC driver? I'm running 32-bit PostgreSQL on 64-bit Windows ====

You need to use the 32-bit ODBC administrator to set up data sources for 32-bit
applications using 32-bit drivers.

Unless you've also installed a [[#What about 64-bit ODBC drivers?|64-bit version]] of
[http://psqlodbc.projects.postgresql.org psqlODBC], a 32-bit install of PostgreSQL will
only have a 32-bit ODBC driver. The 32-bit ODBC driver may only be used by 32-bit programs,
and ''will not show up in the 64-bit ODBC administrator''.

This gets confusing because on 64-bit windows <code>c:\windows\system32\odbcad32</code> is the ''64-bit''
ODBC driver administrator, despite the name. This is a historical artifact of Windows development.
Apparently many apps and installers depend on odbcad32.exe having that name and path,
so Microsoft landed up being stuck with it despite the now-stupid name, which made sense back
in the 16- to 32-bit transition but makes none now. It's the same reason the
"system32" directory is still called that on 64-bit Windows. PostgreSQL can't do anything about this.

See: [http://support.microsoft.com/kb/942976 http://support.microsoft.com/kb/942976]

You'll see in that article that the 32-bit ODBC administrator on 64-bit Windows is:

<pre>
%systemdrive%\Windows\SysWoW64\odbcad32.exe
</pre>

You can launch this from "Start->Run" using the path above. You will see the PostgreSQL ODBC drivers in the
32-bit ODBC administrator.

You 'can not' use a 32-bit ODBC driver in a 64-bit application. That means that you'll still only be
able to use the PostgreSQL ODBC driver with 32-bit applications unless you install a 64-bit ODBC driver
as well.

==== Can I use a 64-bit ODBC program with a 32-bit PostgreSQL server? ====

Only if you have a 64-bit [http://psqlodbc.projects.postgresql.org|psqlODBC] driver installed. See the installation section.

Running & Installing PostgreSQL On Native Windows

2012-06-21T23:26:09Z

Gabrielle: /* What do I need to install PostgreSQL on Windows? */ remove spurious bracket

{{Languages}}

== Supported Platforms ==
=== What versions of Windows does PostgreSQL run on?===

PostgreSQL is supported on Windows XP and above, at least as of version 9.0. It will run on 32 and 64 bit systems.

Versions of the server are not tested on new operating system versions that are released after a newer major version of the server was released. For example, Windows 7 was released after PostgreSQL 8.4, so PostgreSQL 8.3 will not be supported on it. Similarly, when the upcoming RHEL 6 is released, only PostgreSQL 9.0.x will be supported on it. We aim to support new versions of Windows in the PostgreSQL major version following their release at the latest.

For information about platforms supported by the One-click installer, please see the installer download page, off the main [http://www.postgresql.org/download/windows download page for windows].

For information on non-Windows platforms see the [[FAQ|main FAQ]] and the [http://www.postgresql.org/download/ main download page].

=== What Windows platforms are NOT supported? ===

The PostgreSQL installers are not tested or supported on:

* Windows XP Embedded
* Windows 2000
* Windows NT 4
* Windows NT 3.5.x
* Windows 95/98/ME/3.x
* Windows CE
* Windows Mobile

These platforms are not supported. Please do not ask the mailing list for help with any of these platforms.

Please read the troubleshooting notes on [[Troubleshooting Installation#Installation fails on windows embedded|installation on embedded versions of windows]] for some more information about embedded windows.

=== I heard that NT4 and Windows 2000 are supported. Is that true? ===
Although not officially supported, PostgreSQL may run on Windows NT4 and Windows 2000
with a few minor issues including:
* The installer may not work correctly, thus you will need to install PostgreSQL manually from the binary .zip release, or compile it yourself.
* PostgreSQL uses a feature in the NTFS filesystem called 'reparse points' to implement tablespaces. Reparse points are not available in NT4, hence tablespaces cannot be used on NT4.
* There is no 'runas.exe' included in Windows NT4 as standard, making it difficult to start PostgreSQL from an administrative account.
It should also be noted that very little testing has been done on NT4.
* No testing is done on Windows NT 4 or Windows 2000, so newer versions may not work on these platforms.

Please do not ask for help with these obsolete platforms on the mailing list. Some of the [http://www.postgresql.org/support/professional_support professional support] companies may be able to assist you, though.

=== What about Windows 95/98/ME? ===

PostgreSQL requires functionality that is not available on these
platforms and will not run on them. If you need to run PostgreSQL
on these platforms, you can look at the
[http://www.postgresql.org/files/documentation/faqs/text/FAQ_CYGWIN Cygwin]
port, which has basic support for 9x platforms.

=== Is there a 64-bit build of PostgreSQL for Windows? ===

Yes. A [[64bit Windows port]] was released for [[PostgreSQL 9.0]].

32-bit builds of previous versions of PostgreSQL generally run fine on 64-bit Windows. Though they cannot practically use more than about 1GB of shared_buffers directly, they can still benefit from more than 4GB of memory because the Windows kernel will use that memory to cache disk reads.

=== What about 64-bit ODBC drivers? ===

At time of writing there was 64-bit support in the [http://psqlodbc.projects.postgresql.org/ psqlODBC] source code, but no official binary releases of 64-bit ODBC drivers. Check the psqlODBC website for details.

== Installation ==

=== What do I need to install PostgreSQL on Windows? ===

See [http://www.postgresql.org/download/windows the PostgreSQL for Windows download page] for various ways to download and install PostgreSQL on Windows.

The easiest way to install PostgreSQL on Windows is with the
One Click installer package maintained by EnterpriseDB, which you can get from the page linked to above. This will install PostgreSQL along with
pgAdmin (a graphical administration and management program), a selection of 'contrib' modules to provide additional specialised functionality, and a choice of procedural languages. A program called StackBuilder will be installed to help you download and install any additional components, like ODBC or JDBC drivers, that you may need.

=== What do I need to compile PostgreSQL from source code? ===

See the [http://www.postgresql.org/docs/current/static/install-windows.html documentation]
for instructions on how to compile PostgreSQL for windows, including details about supported compilers and tools.

=== Why do I need a non-administrator account to run PostgreSQL under? ===

When a hacker gains entry to a computer using a software bug in a
package, she gains the permissions of the user account under which the
service is run. Whilst we do not know of any such bugs in PostgreSQL,
we enforce the use of a non-administrative service account to minimise
the possible damage that a hacker could do should they find and utilise
a bug in PostgreSQL to hack the system.

This has long been common practice in the Unix world, and is starting to
become standard practice in the Windows world as well as Microsoft and
other vendors work to improve the security of their systems.

Note, that with the release of PostgreSQL 8.2, it is possible to run under
a administrative account. PostgreSQL 8.2 and above are able to irrevocably
give up administrative rights at startup thus ensuring the rest of the
system remains secure in the extremely unlikely event that PostgreSQL
becomes compromised.

=== Can I install PostgreSQL on a FAT partition? ===

Use of PostgreSQL on FAT32 file systems is not supported or tested, because
FAT32 is a terrible file system to run any database on.

PostgreSQL's number one priority is the integrity of your data. FAT and
FAT32 filesystems simply do not offer the reliability or crash-safety required.
In addition, the lack of security features offered by FAT make it
impossible to secure the raw data files from unauthorised modification.
Finally, PostgreSQL utilises a feature called 'reparse points' to
implement tablespaces. This feature is not available on FAT partitions.

The NTFS file system is a journalled filesystem offering much better
reliability and crash recovery. In addition, it has a comprehensive
access control system and offers the reparse point functionality used
by PostgreSQL.

For this reason, the PostgreSQL installer package will not initialise
a database cluster on anything but an NTFS partition. The server and
utilities may be installed on any partition type.

It is recognised however, that in rare cases FAT partitions may be the only choice.
In such cases, you can simply install PostgreSQL as normal, but without initialising the
database cluster. When the installation has finished, manually run
the 'initdb.exe' program on the FAT partition. Security and
reliability will be compromised however, and any attempts to create
tablespaces will fail. Do not use PostgreSQL on FAT32 in production.

=== What filesystem permissions does PostgreSQL require? ===
The PostgreSQL service account needs ''read'' permissions on
all directories leading up to the service directory. It needs ''write'' permissions ''only''
on the data directory. Specifically, it should ''not'' be granted anything other than ''read''
permissions on the directories containing binary files. (All directories below the installation
directory are set by the installer, so unless you change something, there should be no problem with this).

PostgreSQL also needs ''read'' permissions on system DLL files like kernel32.dll and user32.dll
(among others), which is normally granted by default, and on the CMD.EXE binary, which may in some
scenarios be locked down and need opening.

If you are running PostgreSQL on a multi-user system, you should remove the permissions from all
non-administrative users from the PostgreSQL directories. No user ''ever'' needs permissions on the
PostgreSQL files - all communication is done through the libpq connection. Direct access to data files
can lead to information disclosure or system instability!

=== Why can't I select Unicode as an encoding? ===

Starting with PostgreSQL 8.1, the UTF-8 unicode encoding is fully supported on Windows. The Unicode ODBC driver supports UTF-16, and the JDBC driver also has full unicode support.

The PostgreSQL server does not support the 2-byte UTF-16 or 4-byte UTF-32 Unicode encodings for internal data storage or on-the-wire communication. Beause UTF-16 is the default encoding on Windows, and what people on Windows usually mean when they say "Unicode", you might expect this to be a problem, but in practice it's fine, as the ODBC and JDBC drivers take care of this. Programs using libpq directly need to be aware of this, but not much else does.

=== I installed in a non-english language, but all messages show up in english! ===
The language choice made during the installation only selects which language is used by the installer. To
change the language of the messages of the installed product, make sure you have installed the ''National language
support'' feature. Then edit your postgresql.conf file and change the value of the ''lc_messages'' parameter
to the language you want.

== Common installation errors ==

=== PostgreSQL and/or the installer crashes at startup, fails to start or hangs on start ===

By far most common reasons for installation and runtime problems with PostgreSQL on Windows are Windows Scripting Host issues, antivirus software problems and 3rd-party (non-Microsoft) software firewalls. People also sometimes have trouble with the postgres service account password.

The following articles cover these issues. Please read them and follow their instructions before asking for help with installer problems.

==== Antivirus software ====

If you have any antivirus software installed, you '''must''' exclude the data directories that are to be used by PostgreSQL and '''must''' exclude postgresql.exe process. If that still does not help, it may be required to completely uninstall the antivirus software from the machine.

Antivirus software can interfere with PostgreSQL's operation, because PostgreSQL requires file access commands in Windows to behave exactly as documented by Microsoft, and many antivirus programs contain errors or accidental behavior changes that cause these commands to misbehave subtly. Most programs do not care because they access files in fairly simple ways. Because PostgreSQL is continuously reading from and writing to the same set of files from multiple processes, it tends to trigger programming and design mistakes in antivirus software, particularly problems related to concurrency. Such problems can cause random and unpredictable errors, or even data corruption.

Antivirus software is also likely to dramatically slow down PostgreSQL's operation. For that reason, you should at least exclude postgres.exe and the data directories so the scanner ignores them.

===== What Anti-Virus software is compatible? =====

The systems used to build the Windows installers all run either Sophos AV or AVG Free Edition, and
those systems pass a full set of PostgreSQL regression tests running those programs.
Microsoft Security Essentials is also known to work.

Specific issues have been reported with the ''nod32'' antivirus
product. If you are using this product, add "postmaster.exe" to the list
of excluded processes (available under advanced options). This has been
reported to fix the problem.

Specific issues have also been reported with McAfee and Panda anti-virus
software and NetLimiter network monitoring software. While some people do have
PostgreSQL working with these software packages, there is no specific or even
recommend solutions that have not worked in some cases, so the issues would appear
to be installation specific, sometimes even requiring uninstallation.

==== Software firewalls ====

If you have any 3rd-party firewall software installed on your machine, try either disabling it or uninstalling it. There's really no need for 3rd party firewalls on Windows XP and above, as the built-in firewall provided by Microsoft does an excellent job already. Some badly-written 3rd party firewalls do not uninstall correctly, so after uninstallation you might have to [http://support.microsoft.com/kb/299357 tell Windows to repair its network settings].

If you had a 3rd-party firewall and have now uninstalled it, make sure to turn Windows Firewall back on, as many products turn it off during installation and fail to turn it back on during uninstallation.

==== The installer exits with a runtime installation error? ====

The installer may exit with an error like: ''An error occured executing the Microsoft VC++ runtime installer''. This can only happen on Windows.

There are two main reasons why this may occur:

1) The Windows Scripting Host is unable to execute VBscripts. This can occur if the scripting host is disabled (which is unusual), or if the installation is broken. A sign of this problem is a message like ''CScript Error: Can't find script engine "VBScript" for script "C:\...''. It can often be resolved by re-registering the VBscript interpreter - click ''Start'' -> ''Run'' and enter the following and click ''OK'':

regsvr32 %systemroot%\system32\vbscript.dll

If that fails, on older versions of Windows you can try [http://www.microsoft.com/downloads/en/results.aspx?freetext=windows+script+host&displaylang=en&stype=s_basic updating the scripting host].

2) The installer is unable to properly read and write files to the system ''TEMP'' directory. This can occur if the ''TEMP'' or ''TMP'' environment variables are set to non-standard values, and can be recognised by errors in the logfile indicating that scripts could not be executed or found. To resolve this issue, ensure the ''TEMP'' and ''TMP'' variables are set to their correct values.

==== Trouble with passwords for the postgres user ====

Dave Page wrote a [http://pgsnake.blogspot.com/2010/07/postgresql-passwords-and-installers.html blog post] explaining what the different passwords are used for, and how to overcome common problems such as resetting them.

==== PATH environment variable ====

There is also an issue if you have installed ''cygwin'', and the cygwin\bin directory is present
in the system PATH variable. There are DLL files in the cygwin directory related to interpreted languages (TCL,
perl, python) that contain bugs that can cause the installer or the installed version of PostgreSQL to either hang
or crash. Remove the cygwin\bin directory from your path before running the installer!

Problems have also been observed when the PATH environment variable contains directories containing versions of libssl and/or libintl.

==== I'm getting permissions errors when installing/running initdb ====

Make sure the PostgreSQL service account has permissions on the directories leading up to the one
you have installed into. The installer will set permissions on the install directory but not on
parent directories of it.

You may also see related errors show up as The database Cluster initialisation failed during the One Click installer. Check your install-postgresql log
but it is usually related to permission errors. The following thread may help,

http://forums.enterprisedb.com/posts/list/2044.page#7503

Or alternatively, you can fix up the directory permissions and then manually restart the initcluster.vbs script like this for v9,

cscript //NoLogo "<install_path>/installer/server/initcluster.vbs" "postgres" "postgres" "<password>" "<install_path>" "<data_path>" 5432 "DEFAULT"

==== The installer claims the specified account is an administrator, but it isn't! ====

Most likely, the specified account is an administrator or power user,
even though you aren't aware of it. The check used by the installer
specifically checks for membership in the Administrators or
Power Users group. Work your way backwards using Local Users and Groups -
open the Administrators group, see who's a member. Then check any
groups (domain or local) that are a member of the Administrators group,
and any groups members of that group etc. PostgreSQL checks any level
of nested groups.

==== I'm getting an error message that says PostgreSQL cannot be installed from a Terminal Services session ====

This is unfortunately so. The PostgreSQL backend won't run from a TS session, and in order to do initdb the installer
has to start a standalone backend. Therefore, installation has to be performed from the console. Note that if you are
using Windows Server 2003, you can get remote access to the actual console and not just an administrative session.
To do this, start the Remote Desktop Connection by executing mstsc /console, and then connect as usual.
This will lock the local console of the server and give you control over that session. In this scenario,
PostgreSQL should install just fine.

==== I get the error "the user has not been granted the requested logon type at this computer" or similar ====

Make sure the specified PostgreSQL account has the "Log on as a service"
and "Log on locally" rights. The "Log on locally" is only required for
the install part, and can be removed once the installation is completed
if security policies require it. (Rights are granted and revoked using
the "Local Security Policy" MMC snapin. "Log on locally" is default,
and "Log on as a service" will normally be granted automatically by
the installer).

If you still have this problem, enable auditing (also using
the "Local Security Policy" snapin) and let us know what other rights
were required in your setup.

Note that if your computer is a member of a domain, the settings of
the security policies may be controlled at the domain level using
Group Policy.

==== How do I delete the service account - it's not listed under users! ====

Windows sometimes hide some accounts from the GUI tools, so they cannot be removed from there. This includes
the auto-created service account for PostgreSQL (that may be left over from a previous installation). To delete this
account, use the NET command on the commandline:
NET USER <username> /DELETE
Where <username> is the windows login name of the user, for example ''postgres''.

== Common runtime issues ==

=== I'm getting "dynamic load error" when installing a procedural language ===

Most commonly this means that the actual language DLL for the procedural language is missing. The PostgreSQL
DLLs only contains the language bindings, and require the language distribution DLLs to be present
in the system PATH. For a list of the current required DLLs for the different procedural languages,
please see [http://pginstaller.projects.postgresql.org the installation instructions].

To find out exactly which DLL files are missing, you can use the ''depends'' tool from Microsoft.
It is available in the Windows Support Tools, that are on the Windows CD as a separate install. Just run
''depends plpython.dll'' (for PL/python) to show which imports are missing.

=== I'm seeing a lot of postgres.exe processes even though I only started the server once ===

This is normal. PostgreSQL uses a multi-process architecture. In an empty system you will see anything from two to
five processes. Once clients start to connect, the number of processes will increase.

=== How do I set an environment variable? ===

PostgreSQL uses environment variables for several settings. To change an environment variable in most
Windows versions, go into Properties for My Computer, then into Advanced. Note that there are two sets of
environment variables - one for the system which applies to all users and one for the current user. If you
want an environment variable to affect the PostgreSQL service, you must change the system variable. After
changing a system variable, you must restart the service.

=== I cannot run with more than about 125 connections at once, despite having capable hardware ===

When running as a service, you may experience failures with more than approximately 125 simultaneous connections.
This can happen because some of the libraries that PostgreSQL is dependent on are dependent on user32.dll which allocates
memory from an area known as the Desktop Heap. The desktop heap is assigned to each logon session, with non-interactive
sessions typically being assigned 512KB. Each postgres process that runs typically consumes approximately 3.2KB of desktop
heap, which coupled with other overhead can exhaust the allocated heap at somewhere around 125 connections. This doesn't
happen when running from the command line (or more precisely, happens with much higher numbers of connections) because the
interactive logon session is typically allocated 3MB of Desktop Heap.

You can increase the non-interactive Desktop Heap by modifying the third SharedSection value in the registry as described
in this [http://support.microsoft.com/kb/184802 Microsoft Knowledgebase article]. Note that this should be done
with great care as specifying a value that is excessively high may prevent your system from booting.

[[Category:FAQ]] [[Category:Windows]]

== Windows version-specific issues ==

==== Can I install a 32-bit PostgreSQL on 64-bit Windows? ====

Recent 32-bit versions of PostgreSQL (8.3 and newer) can be installed and used on 64-bit Windows XP and above,
though they retain the 32-bit limits on maximum process address space (and thus shared memory).

You can connect to the 32-bit postgresql server from 64-bit programs on the computer the server is running on
or other computers if a 64-bit libpq or psqlODBC driver is installed where the program is running.

Because 32-bit versions of the PostgreSQL server only install a 32-bit libpq and pgsqlODBC, only 32-bit programs
on the computer the server was installed on can use the database unless a 64-bit ODBC driver or libpq
is installed as an add-on.

==== Where is the PostgreSQL ODBC driver? I'm running 32-bit PostgreSQL on 64-bit Windows ====

You need to use the 32-bit ODBC administrator to set up data sources for 32-bit
applications using 32-bit drivers.

Unless you've also installed a [[#What about 64-bit ODBC drivers?|64-bit version]] of
[http://psqlodbc.projects.postgresql.org psqlODBC], a 32-bit install of PostgreSQL will
only have a 32-bit ODBC driver. The 32-bit ODBC driver may only be used by 32-bit programs,
and ''will not show up in the 64-bit ODBC administrator''.

This gets confusing because on 64-bit windows <code>c:\windows\system32\odbcad32</code> is the ''64-bit''
ODBC driver administrator, despite the name. This is a historical artifact of Windows development.
Apparently many apps and installers depend on odbcad32.exe having that name and path,
so Microsoft landed up being stuck with it despite the now-stupid name, which made sense back
in the 16- to 32-bit transition but makes none now. It's the same reason the
"system32" directory is still called that on 64-bit Windows. PostgreSQL can't do anything about this.

See: [http://support.microsoft.com/kb/942976 http://support.microsoft.com/kb/942976]

You'll see in that article that the 32-bit ODBC administrator on 64-bit Windows is:

<pre>
%systemdrive%\Windows\SysWoW64\odbcad32.exe
</pre>

You can launch this from "Start->Run" using the path above. You will see the PostgreSQL ODBC drivers in the
32-bit ODBC administrator.

You 'can not' use a 32-bit ODBC driver in a 64-bit application. That means that you'll still only be
able to use the PostgreSQL ODBC driver with 32-bit applications unless you install a 64-bit ODBC driver
as well.

==== Can I use a 64-bit ODBC program with a 32-bit PostgreSQL server? ====

Only if you have a 64-bit [http://psqlodbc.projects.postgresql.org|psqlODBC] driver installed. See the installation section.

IRC2RWNames

2012-06-21T23:08:31Z

Gabrielle: /* List of IRC nicks with their respective real world names */ link to my user page here

=== List of IRC nicks with their respective real world names ===

You can find many PostgreSQL users and developers chatting in [irc://irc.freenode.net/postgresql #postgresql on freenode]. Here's more information about some of the regulars there:

{| border="1"
|-
!Nickname || Real Name
|-
|ads || Andreas Scherbaum
|-
|agliodbs, aglio2 (freenode), jberkus (oftc) || Josh Berkus
|-
|ahammond || Andrew Hammond
|-
|alvherre || Alvaro Herrera
|-
|andres || Andres Freund
|-
|Assid || Satish Alwani
|-
|aurynn || Aurynn Shaw
|-
|BlueAidan/BlueAidan_work || [[user:davidblewett | David Blewett]]
|-
|bmomjian || Bruce Momjian
|-
|cbbrowne || Christopher Browne
|-
|cce || Clark C. Evans
|-
|chicagoben || Benjamin Johnson
|-
|crab || Abhijit Menon-Sen
|-
|Crad || Gavin M. Roy
|-
|daamien || Damien Clochard
|-
|DarcyB || Darcy Buskermolen
|-
|darkixion || Thom Brown
|-
|davidfetter || David Fetter
|-
|dbb || Brian Hamlin / darkblue_b
|-
|dcolish || [http://www.unencrypted.org Dan Colish]
|-
|dcramer || Dave Cramer
|-
|DeciBull, TheCougar || Jim C. Nasby
|-
|dennisb || Dennis Björklund
|-
|depesz || Hubert Lubaczewski
|-
|devrimgunduz || Devrim Gündüz
|-
|digicon || [http://digicondev.blogspot.com Zach Conrad]
|-
|dim || Dimitri Fontaine
|-
|direvus || Brendan Jurd
|-
|drbair || Ryan Bair
|-
|DrLou || Lou Picciano
|-
|duck_tape || Adi Alurkar
|-
|dvl || [http://langille.org/ Dan Langille]
|-
|eggyknap || Joshua Tolley
|-
|endpoint_david || David Christensen
|-
|f3ew/devdas || Devdas Vasu Bhagat
|-
|feivel || Michael Meskes
|-
|elein || Elein Mustain
|-
|gleu || Guillaume Lelarge
|-
|gorthx || [[User:Gabrielle|Gabrielle Roth]]
|-
|grzm || Michael Glaesemann
|-
|gsmet || Guillaume Smet
|-
|gregs1104 || Greg Smith
|-
|G_SabinoMullane || Greg Sabino Mullane
|-
|HarrisonF || Harrison Fisk
|-
|ioguix || Jehan-Guillaume de Rorthais
|-
|indigo || Phil Frost
|-
|intgr || Marti Raudsepp
|-
|JanniCash || Jan Wieck
|-
|jconway || Joe Conway
|-
|jdavis, jdavis_ || Jeff Davis
|-
|jkatz05 || Jonathan S. Katz
|-
|johto || Marko Tiikkaja
|-
|jurka || Kris Jurka
|-
|justatheory || David Wheeler
|-
|jpa || Jean-Paul Argudo
|-
|jwp || James Pye
|-
|j_williams || Josh Williams
|-
|kgrittn || Kevin Grittner
|-
|klando || Cédric Villemain
|-
|larryrtx || Larry Rosenman
|-
|linuxpoet, postgresman || Joshua D. Drake
|-
|lluad || Steve Atkins
|-
|lsmith || Lukas Smith
|-
|magnush || Magnus Hagander
|-
|marco44 || Marc Cousin
|-
|markwkm || Mark Wong
|-
|mastermind || [[user:mastermind | Stefan Kaltenbrunner]]
|-
|mbalmer || [[user:mbalmer | Marc Balmer]]
|-
|merlin83 || Chua Khee Chin
|-
|merlinm || Merlin Moncure
|-
|metatrontech || Chris Travers
|-
|miracee || Susanne Ebrecht
|-
|Moosbert || Peter Eisentraut
|-
|neilc || Neil Conway
|-
|oicu || Andrew Dunstan
|-
|okbobcz || Pavel Stehule
|-
|pg_docbot || [[IRCBotSyntax]]
|-
|pgSnake || Dave Page
|-
|PJMODOS || Petr Jelínek
|-
|Possible || Robert Ivens
|-
|postwait || Theo Schlossnagle
|-
|prothid || R Brenton Strickler
|-
|psoo || Bernd Helmle
|-
|pyarra || Philip Yarra
|-
|raptelan || [[user:Cshobe|Casey Allen Shobe]]
|-
|rhaas || Robert Haas
|-
|RhodiumToad (formerly AndrewSN) || Andrew Gierth
|-
|Robe || [[user:Robe | Michael Renner]]
|-
|rotellaro || Federico Campoli
|-
|rz || Kirill Simonov
|-
|SAS || Stéphane Schildknecht
|-
|scrappy || Marc G. Fournier
|-
|selenamarie || Selena Deckelmann
|-
|SkippyDigits || Sherri Kalm
|-
|Snow-Man || Stephen Frost
|-
|Spritz || Matteo Beccati
|-
|sternocera || Peter Geoghegan
|-
|StuckMojo, MojoWork || Jon Erdman
|-
|swm || Gavin Sherry
|-
|vy || Volkan YAZICI
|-
|wulczer || Jan Urbański
|-
|xaprb || Baron Schwartz
|-
|xzilla, xzi11a || [[User:Xzilla|Robert Treat]]
|}

[[Category:Community]]

PDXPUG Talks

2012-05-17T23:30:04Z

Gabrielle: add 2012 talks to date

PDXPUG Talks

2012-01-09T00:53:03Z

Gabrielle: Rob Treat asked me for this at PgOpen. I'll make it pretty later.

Pdxpug

2012-01-09T00:11:01Z

Gabrielle: add link to list of past talks

Page to hold PDXPUG-specific files & such.

== Logo ==
Small version; not sure where the large one is

[[Image:pdxpug_logo.jpg|100|JPG]]

[[Media:pdxpug_logo.gif|or grab the GIF version]]

== Poster ==
[[Media:pdxpug_poster.pdf|PDF]]

== Flyers ==

* PGXPUG PgDay after-party flier (2011): Front [[Media:Party_invite_front.odt‎|ODT]] | Back [[Media:Party_invite_back.odt‎|ODT]]. You'll need the following fonts: Strait, monofur.

== Speaker Info ==

[[File:PDXPUGSpeakerInfo.odt]]

== Talks ==
[[PDXPUG Talks]]

File:PDXPUGSpeakerInfo.odt

2012-01-08T23:41:29Z

Gabrielle: uploaded a new version of "File:PDXPUGSpeakerInfo.odt"

Form letter we send out to new speakers. Be sure to FITB :)

File:PDXPUGSpeakerInfo2.odt

2012-01-08T23:40:50Z

Gabrielle: New version of speaker info sheet for PDXPUG meetings: meetings moved to Iovation.

New version of speaker info sheet for PDXPUG meetings: meetings moved to Iovation.

PatchReviewParty

2011-10-05T02:29:29Z

Gabrielle: /* At the PRP */ Update with instructions to apply patch with git

Part UG meeting, part hackathon: it's the Patch Review Party, and it's coming to a city near you - because you're going to have one! Your goal is to introduce people to the patch review process, add them to the RRReviewers pool, and review some patches.

==Stuff organizers (that's you!) need to do beforehand==
===Find some people to attend===
Have people sign up in advance. PDXPUG limits ours to 10-12 people, usually due to space limitations.

===Find a date & time===
3 hours seems to be the sweet spot - 2 hours is too short, and 4 is too large a chunk out of people's days. Weeknights (Sun - Thurs) work best for our group.

===Provide user support===
* beverages & food (potluck may be ok if you're doing it on the weekend)
* carpool setup/parking/easy access to public transit
* seating
* easy restroom access
* Internet access
* have the latest Pg & the patches on a USB key (because there's usually one person who forgets to get them)
* power
* some way of sharing info, eg a whiteboard, etherpad, or your group's IRC channel. For our first PRP, some non-local Pg experts and the current commitfest manager volunteered to sit in our group's IRC channel & answer questions. This was a big help.

Last, notify attendees of the Stuff They Need to Do Beforehand (next section).

==Stuff attendees need to do beforehand==
===Set up the current version of Pg===
(this step alone saves a significant amount of time)
git clone git://git.postgresql.org/git/postgresql.git
If it's been a few days since you cloned the repo, update it before the PRP with `git pull origin`.
configure && make && make check
Make sure you're doing this somewhere away from any other Pg installs you don't want to mess with.

===Review the relevant docs on the wiki===
http://wiki.postgresql.org/wiki/RRReviewers

http://wiki.postgresql.org/wiki/Reviewing_a_Patch

===Acquire patches===
For our first PRP, we had the CommitFest Manager assign our group some easy patches to review. Now, we generally choose our own from the current list of patches for review from https://commitfest.postgresql.org/action/commitfest_view/inprogress

Attendees can download their own patches (in advance if possible!), or the organizer can have them available by USB.

==At the PRP==
We've had good luck doing solo & paired reviewing. Pick whatever works best; our last PRP we had a mix & it worked fine. If it's your first one, you may want to pair people up beforehand, so you have new people working with more experienced people.

How to patch, if you've never done it before (old school):
patch -b -p0 < [patchfile]
Or, newer & easier with git:
git apply [patchfile]
...then run `configure && make check && make install` again.

Some tips:
* You can do a "git branch" before you apply the patch, if you want to keep your changes separate. (git branch [branch_name])
* Acquiring patches from https://commitfest.postgresql.org/action/commitfest_view/inprogress: Click the patch name, then the "Patch" link under comments to go to the -hackers mailing list, where you should find the patch as an attachment - make sure you get the most recent version.
* Check first that the patch is in the right format
* You may need to deal with Windows-style carriage returns; try:
** dos2unix
** perl -pi -e 's/\r\n/\n/;' [patchfile]
* If you're using patch, you might need to:
** alter the file paths at the top of the patch file to match what's in your git repo
** adjust the patch level (the -p argument to the patch command)

==Wrap-up & Followup==
Don't worry if not everyone completes their review at the PRP; some patches are just too complex for one evening. At the first PRP, and maybe when you have new people, you may need to find out what the status of the reviews are & make sure everyone follows up properly. (This saves the CommitFest Manager from having to do that.)

Pdxpug

2011-09-21T00:40:56Z

Gabrielle: add speaker info form letter

File:PDXPUGSpeakerInfo.odt

2011-09-21T00:39:16Z

Gabrielle: Form letter we send out to new speakers. Be sure to FITB :)

Form letter we send out to new speakers. Be sure to FITB :)

Postgres Open Entertainment

2011-09-21T00:25:39Z

Gabrielle: Idea bucket for fun stuff to do at PgOpen

== Ideas for 2012 ==

* Chocolate Tour
* Architecture Boat Tour (I'm told that this is the best one: http://caf.architecture.org/page.aspx?pid=574)
* Kayak Tour
* Bike Tour
* Mini golf "PgOpen at PgOpen"

Postgres Open Talks 2011

2011-09-20T00:50:07Z

Gabrielle: d'oh, put my talk on the wrong day :P

= Postgres Open Talks 2011 =

Here will be the Postgres Open talks.

== Tutorials: Wednesday September 14, 2011 ==

=== Mayfair Room ===
* [http://bunsen.credativ.com/~jco/2011/migrating.pdf Migration to PostgreSQL - preparation and methodology]
* [http://www.scribd.com/doc/65304692/Scaling-With-SkyTools Scaling With Skytools]

=== Governor's Suite ===
* [http://momjian.us/main/writings/pgsql/administration.pdf Mastering PostgreSQL Administration]

== Sessions: Thursday September 15, 2011 ==

=== Cotillion Room ===
* [http://www.pgexperts.com/document.html?id=53 Keynote: The next 25 years]
* [http://bonesmoses.org/presentations/nvram_fun_profit.pdf NVRAM for Fun and Profit]
* [http://wiki.postgresql.org/wiki/File:Pg_query_analysis_20110914.odp Identifying Slow Queries and Fixing Them Slides]

=== Mayfair Room ===
* [http://joshwilliams.name/talks/monitoring/ Monitoring the Heck out of Your Database]
* [http://www.slideshare.net/DBNess/honey-i-shrunk-the-database-9273383 Honey, I Shrunk the Database]
* [http://wiki.postgresql.org/images/0/0b/Postgresql_django_extensions.pdf Writing Django Extensions for PostgreSQL]
* [http://wiki.postgresql.org/images/8/8e/Logging.odp Logging - Not Just for Lumberjacks] (speaker notes included)

=== Governors' Suite ===

* [http://heroku-postgres-talk.heroku.com/ Heroku Postgres]
* [http://wiki.postgresql.org/images/5/58/Why_you_should_not_move_away_from_Oracle.pdf Why you should NOT move away from Oracle]
* [http://bunsen.credativ.com/~mme/2011/MissionImpossible.pdf Mission impossible? Can I replace my most important databases with PostgreSQL?]
* [http://wiki.postgresql.org/images/0/0c/BillingSystemForTELCO_technical.pdf Billing System for a TELCO based on PostgreSQL - technical description]
* [[media:HP_Postgres_Insight_RS.pdf|HP Performs Large-scale Deployment of Postgres with its Remote Support Software]]

=== Michigan Demos ===

* [http://www.enterprisedb.com/resources-community/webcasts-podcasts-videos/webcasts/postgres-cloud-introduction-postgres-plus-clou Postgres In the Cloud: an Introduction to Postgres Plus Cloud Server]

== Sessions: Friday September 16, 2011 ==

=== Cotillion Room ===

* [http://michael.otacoo.com/wp-content/uploads/2011/09/20110916_pgopen_xc.pdf Postgres-XC]
* [http://momjian.us/main/writings/pgsql/locking.pdf Unlocking the Postgres Lock Manager]

=== Mayfair Room ===
* [http://wiki.postgresql.org/images/7/79/Accelerating_Local_Search_PostgreSQL_91.pdf Accelerating Local Search With PostgreSQL 9.1]
* [http://bunsen.credativ.com/~jco/2011/plr-PostgresOpen-2011.pdf PL/R -- The Fast Path to Advanced Analytics]

=== Michigan Room ===

* [http://wiki.postgresql.org/images/0/0e/Center_of_your_dataverse.pdf PostgreSQL at the centre of your dataverse]
* [http://wiki.postgresql.org/images/5/56/Database_sing.pdf We write the code that makes the database sing]
* [http://wiki.postgresql.org/images/f/fa/Slony_Versus_Developers.pdf Slony Versus Developers]
* [http://wiki.postgresql.org/images/7/7f/Adam-lowry-postgresopen2011.pdf Postgres at Urban Airship]

[[Category:PostgreSQL Events]]

Postgres Open Talks 2011

2011-09-18T22:18:48Z

Gabrielle:

= Postgres Open Talks 2011 =

Here will be the Postgres Open talks.

== Tutorials: Wednesday September 14, 2011 ==

=== Mayfair Room ===
* [http://bunsen.credativ.com/~jco/2011/migrating.pdf Migration to PostgreSQL - preparation and methodology]

== Sessions: Thursday September 15, 2011 ==

=== Cotillion Room ===
* [http://www.pgexperts.com/document.html?id=53 Keynote: The next 25 years]
* [http://bonesmoses.org/presentations/nvram_fun_profit.pdf NVRAM for Fun and Profit]
* [http://wiki.postgresql.org/wiki/File:Pg_query_analysis_20110914.odp Identifying Slow Queries and Fixing Them Slides]

=== Mayfair Room ===
* [http://joshwilliams.name/talks/monitoring/ Monitoring the Heck out of Your Database]
* [http://www.slideshare.net/DBNess/honey-i-shrunk-the-database-9273383 Honey, I Shrunk the Database]
* [http://wiki.postgresql.org/images/0/0b/Postgresql_django_extensions.pdf Writing Django Extensions for PostgreSQL]

=== Governors' Suite ===

* [http://heroku-postgres-talk.heroku.com/ Heroku Postgres]
* [http://wiki.postgresql.org/images/5/58/Why_you_should_not_move_away_from_Oracle.pdf Why you should NOT move away from Oracle]
* [http://bunsen.credativ.com/~mme/2011/MissionImpossible.pdf Mission impossible? Can I replace my most important databases with PostgreSQL?]
* [http://wiki.postgresql.org/images/0/0c/BillingSystemForTELCO_technical.pdf Billing System for a TELCO based on PostgreSQL - technical description]

=== Michigan Demos ===

* [http://www.enterprisedb.com/resources-community/webcasts-podcasts-videos/webcasts/postgres-cloud-introduction-postgres-plus-clou Postgres In the Cloud: an Introduction to Postgres Plus Cloud Server]

== Sessions: Friday September 16, 2011 ==

=== Cotillion Room ===

* [http://michael.otacoo.com/wp-content/uploads/2011/09/20110916_pgopen_xc.pdf Postgres-XC]

=== Mayfair Room ===
* [http://wiki.postgresql.org/images/7/79/Accelerating_Local_Search_PostgreSQL_91.pdf Accelerating Local Search With PostgreSQL 9.1]
* [http://bunsen.credativ.com/~jco/2011/plr-PostgresOpen-2011.pdf PL/R -- The Fast Path to Advanced Analytics]
* [http://wiki.postgresql.org/images/8/8e/Logging.odp Logging - Not Just for Lumberjacks] (speaker notes included)

=== Michigan Room ===

* [http://wiki.postgresql.org/images/0/0e/Center_of_your_dataverse.pdf PostgreSQL at the centre of your dataverse]
* [http://wiki.postgresql.org/images/5/56/Database_sing.pdf We write the code that makes the database sing]

File:Logging.odp

2011-09-18T22:15:22Z

Gabrielle: Gabrielle Roth's "Logging: Not just for lumberjacks" talk on basic logging configuration for Pg. PgOpen 2011.

Gabrielle Roth's "Logging: Not just for lumberjacks" talk on basic logging configuration for Pg. PgOpen 2011.

Pdxpug

2011-08-20T17:30:22Z

Gabrielle: PDXPUG page for holding our graphics, flyers, etc.

File:Pdxpug poster.pdf

2011-08-20T17:26:32Z

Gabrielle:

File:Pdxpug logo.jpg

2011-08-20T17:26:07Z

Gabrielle:

File:Pdxpug logo.gif

2011-08-20T17:25:37Z

Gabrielle:

Flyers

2011-08-20T17:20:48Z

Gabrielle: moved pdxpug flyer to pdxpug page

Flyers

2011-08-13T03:08:07Z

Gabrielle: Add PDXPUG party flier so other people can use it.

== Flyers aimed at users / managers ==

* General Presentation ( Feb 2008, PG 8.3 ) : [[Media:Flyer pgeu.pdf|PDF]] | [[Media:Flyer pgeu.odt|ODT]]

* 9 Hot New Features in Version 9 ( July 2010, 9.0beta3 ) [[Media:9_new_in_9.pdf|PDF]] | [[Media:9_new_in_9.odt|ODT]]

* QuickFaq ( July 2010 ) [[Media:Flyer_quickfaq.pdf|PDF]]

== Flyers aimed at developers ==

== Flyers for events ==

* PGXPUG PgDay after-party flier (2011): Front [[Media:Party_invite_front.odt‎|ODT]] | Back [[Media:Party_invite_back.odt‎|ODT]]. You'll need the following fonts: Strait, monofur.

[[Category:Advocacy]]

File:Party invite front.odt

2011-08-13T02:57:26Z

Gabrielle: PDXPUG PgDay after-party flyer, front (party announcement)

PDXPUG PgDay after-party flyer, front (party announcement)

File:Party invite back.odt

2011-08-13T02:56:43Z

Gabrielle: PDXPUG PgDay after-party flyer, back (map to venue etc)

PDXPUG PgDay after-party flyer, back (map to venue etc)