nyuuzyou/wikis huggingface dataset:
PostgreSQL on RedHat Linux

If you have the packages already installed on your server, RedHat installation can be as easy as:
service postgresql start
In older versions you'll automatically get a call to service postgresql initdb the first time you do this that will create the database cluster; in recent versions you'll need to do that yourself before the above.
You can turn on and off whether PostgreSQL starts at boot like this:
chkconfig postgresql on/off
The default network configuration that RedHat initdb specifies uses the 'ident' mechanism for controlling access to the database, which is often not what people want. See Client Authentication for more information.
RedHat defaults to creating the database in /var/lib/pgsql/data. If you want to change that, or otherwise want to adjust the parameters uses when PostgreSQL is started, you can do that by editing /etc/sysconfig/pgsql/postgresql and putting changes into there. This is a standard shell script file included into the environment; here is a sample with the default parameters, you can pick just the lines from here you want to change and put new values there:
PGDATA=/var/lib/pgsql/data
PGPORT=5432
PGLOG=/var/lib/pgsql/pgstartup.log
PGOPTS=
PGOPTS can be used to set random other options; it is added to the end of the command line used to run the postmaster daemon. But note that any configuration parameters set this way cannot be changed on-the-fly while the postmaster is running. It's usually better to set custom values in postgresql.conf.
Also, if you want to change PGDATA from the default, be aware that the default SELinux configuration in recent Red Hat releases will prevent the postmaster daemon from writing anywhere except /var/lib/pgsql/data. You'll need to change the SELinux setup or at least relabel directory security contexts to put it someplace else. See PostgreSQL and SELinux for links to more information.
* RPM Installation by Devrim GÜNDÜZ & Lamar Owen
* An Almost Idiot's Guide to PostgreSQL YUM and subsequent 8.3.1 to 8.3.3 upgrade and subsequent Upgrade/Install PostgreSQL 8.4 with Yum.
* RPM Packaging
== Recent Fedora versions ==
Starting in Fedora 16, the configuration of the server has been changed relative to the above. See the release notes for details.
Category:Linux distribution
PostgreSQL Related Slides and Presentations

Here you can find links to various PostgreSQL related presentations
* FOSDEM, Brussels 2020
* PGConf Brazil 2019
* Swiss PGDay 2019
* FOSDEM, Brussels 2019
* PostgreSQL Conference Europe 2018
* PostgreSQL Meetup Genève, 2018-10-11
* PGConf Brazil 2018
* Swiss PGDay 2018
* PG Day France 2018
* PostgreSQL@SCaLE Conference 2018
* PGConf EU 2017
* Postgres Open SV 2017
* Swiss PGDay 2017
* PGConf US 2017
* PGDay Paris 2017
* Nordic PGDay 2017
* PostgreSQL@SCaLE Conference 2017
* FOSDEM, Brussels 2017
* PGConf.Asia 2016
* PGConf SV 2016
* PGDay Austin 2016
* PostgreSQL Conference Europe 2016
* PGConf US 2016
* Swiss PGDay 2016
* PGConf.ru, Moscow 2016
* FOSDEM, Brussels 2016
* PostgreSQL@SCaLE Conference 2016
* German speaking PostgreSQL Conference 2015
* PostgreSQL Conference Europe 2015
* PostgreSQL Sessions #7 Sep, 2015
* PostgresOpen 2015
* pgDay Paris 2015
* PGConf US 2015
* Nordic PGDay, Copenhagen, 2015
* FOSDEM, Brussels 2015
* Level Up Conference 2014 | Craig Kersteins | Postgres: A Data Platform
* PostgreSQL Conference Europe Talks 2014
* PostgreSQL Meetup Paris, 2014-09-08
* PGConf NYC 2014
* Nordic PGDay, Stockholm, 2014
* PgDay SCALE 12x, 2014
* FOSDEM, Brussels 2014
* PgDay Argentina 2013
* PGConf.DE 2013 - German-Speaking PostgreSQL Conference 2013
* PostgreSQL Conference Europe 2013
* Postgres Open 2013
* PGCon, Ottawa 2013
* PGDay NYC 2013
* FOSDEM, Brussels 2013
* PgDay Argentina 2012
* PostgreSQL Conference Europe 2012
* Postgres Open 2012
* PGConf.DE 2011
* PGBR 2011, São Paulo
* PostgreSQL Conference Europe 2011
* Postgres Open 2011
* FOSDEM, Brussels 2010
* PGDay.EU, Paris 2009
* PGCon, Ottawa 2009
* FOSDEM, Brussels 2009
* PgDay 2008 Rio de la Plata (Argentina)
* European PGDay 2008
* Netways Nagios Conference 2008
* FrOSCon, St. Augustin (near Bonn, Germany) 2008
* PostgreSQLConferenceWest2008
* PG UK 2008
* FOSDEM, Brussels 2008
* PGCon Brazil 2008
* PGCon Brazil 2007
* OSCon 2005
* OSCon 2004
* NUUG 2005
* Bruce Momjian Presentations
* PUG_Presentations
* PostgreSQL Coding
Category:Community
Category:PostgreSQL Events
PostgreSQL testing brainstorming: PGCon2013 unconference notes

== Build farm - composed of "animals" ==
* Currently run multiple instances per animal; each animal configures which contrib modules it builds (usually based on platform restrictions) but all tests are run
* No support for machine-to-machine testing at the moment (you can, however, run replication across two local instances)
* Peter Eisentraut had been doing a lot of work with Jenkins
Question around collecting data on where bugs are being found and fixed to determine a heat map of problem areas; discussion goes sideways about the conscious lack of a bug tracker for the project; possibility of using tagging in the bug emails to enable some level of analytics
Testing of clients (beyond psql); libpq is tested and that's what Python, PHP, Perl, etc generally build on, but there is likely not significant automated testing happening with these clients; however, that's generally considered out of scope for the PostgreSQL project proper
Automated fuzz testing of generated SQL, etc is apparently ongoing but the project only hears about it when they find a problem
== Performance farm ==
* Would like to have overall performance testing (with throughput / stress testing); Mark Wong is already doing this on a biweekly basis with DBT2 (because setup / teardown is hard)
* Would like to have individual SQL query regression testing to prevent future fiascos like the 9.2 subquery performance regression
* Only thing that's standing in the way is _time_ to write the performance testing infrastructure; hardware _is_ available (and can be dedicated for performance purposes to provide consistency)
* Build farm already has the ability to report basic profiling information, things like iozone would be useful to help filter out weirdness
Category:Unconference
PostgreSQL Tutorials

PostgreSQL Tutorial in docs The PostgreSQL docs are a great place to learn about Postgres, and the PostgreSQL Tutorial is the place to start.
Postgresql tutorial site General introduction to PostgreSQL for beginners
Postgres guide Covers fundamentals of setup, general SQL, backups, common tools, and Postgres specific tips. Also covers advanced features like HStore, arrays, JSON, and understanding performance.
A collection of video tutorials, blog posts, and Devart Academy for PostgreSQL users showing how to perform basic tasks with PostgreSQL databases using dbForge Studio for PostgreSQL. 
== Other Tutorials ==
* PostgreSQL Tutorial in detail
* Part 1: Getting Started With PostGIS: An almost Idiot's Guide: Walks you thru how to configure PostGIS, Load data, and do common spatial queries.
* Crunchy Data Postgres tutorials: Variety of topics from getting started to functions, CTEs, window functions. All tutorials runs in a local web browser.
Category:Howto
PostgreSQL全国用户会筹办

* 用户会的目的
为了推动PostgreSQL在中国的发展现拟成立PostgreSQL用户会。用户会目的主要是通过组织大会、技术研讨会、网站等社区沟通平台；充实各种技术资料书籍；协调企业各使用的企业进行交，帮助企业顺利使用PostgreSQL,同时为技术人员提供更好的技术交流暨学习的社区，从而推动PostgreSQL在中国的发展。
Postgresql用户会将充实各种技术交流的平台，利用网站、QQ群、邮件列表为沟通交流的手段，定期在各个城市举行用户交流会，同时每年举行一次全国大会。用户会还将负责文档翻译，书籍的出版组织，同时在包括高校、其他技术社区中推广普及PostgreSQL, 加强企业及技术人员的交流。同时还积极培育技术开发人员社区，参与PostgreSQL本地化及功能开发，培养有能力开发PostgreSQL核心功能的技术人员。
* 用户会的形式
用户会可采用民间组织、公司、非正式组织的形式存在。目前暂时先采用非正式组织的形式，待用户会成立以后向民间组织或公司的形式发展。
* 用户会的组织架构
用户会的拟设一个委员会负责用户会的组织管理，还设一个理事会实际负责用户会的具体工作，同时在全国几个主要城市成立分会。委员会由5到7个成员组成，由会长负责组织和协调工作，会议的重要事务由委员会投票决定。委员会拟设几个方面的管理委员。 理事会主要由实际具体负责某一个方面的人员组成，如负责网站的理事，负责文档翻译的理事，及负责论坛管理的理事等。用户会拟在全国的各个大城市如北京、杭州、广州、成都设立分会，分会负责组织本地定期的活动，活动的经费由用户会提供。
*过渡委员会
在实际成立用户会之前拟设立一个过渡委员会，负责用户会的筹备工作。过渡委员会协助完成用户会的章程、网站、理事会的筹建，并在2011年底前正式成立用户会。筹建委员会包含下面的人员
 - 会长：负责全面的协调组织工作
 - 网站及文档管理委员：负责网站、论坛及文档翻译的组织协调工作
 - 各地分会及活动协调组织委员：管理协调各地分会，及活动的组织
 - 高校推动：负责在高校推动PG的普及
 - 开发社区培育委员：开发社区的培育
 - 宣传普及及对外关系委员：负责宣传推广，和其他开源社区的合作，及在Oracle,mysql等社区推动PG的发展
 - 企业赞助及协调：负责企业赞助组织和协调
 (初步名单：李元佳，陈爱声，周正中，萧少聪，孙鹏)
在委员会外还设无投票权的指导委员
 - 独立监察委员(无投票权)
 - 顾问委员(3名左右)(Dr. Tian, Feng from VMware, )
* 组织的经费来源
目前拟采用志愿者、企业赞助、参与者自费的形式筹集运用经费。各委员及理事是完全志愿的形式，而网站、服务器等实体由捐助的形式来支付，而会议的场地、每年大会的组织等这些需由企业赞助；各地的一些活动可以由参会人员AA。 
* 简单的时间计划
 9 月份 确定过渡委员会的人员组织
 10月份 拟定章程、理事会人员组织、各个城市分会的负责人
 11月份 确定用户会的运作形式、网站运作(可以管理会员、发布信息、论坛开始运作等)、和赞助企业协商好
 12月份 用户会对外宣布正式成立，各个城市的用户也开始运作
* 联系
 galylee@gmail.com
Category:Chinese
Postgres-R

== Project Overview ==
Postgres-R provides efficient, fast and consistent multi-master replication for shared nothing clusters. It integrates tightly into Postgres and is written in C as well. It is based on scientifically proven algorithms and uses a Group Communication System for all communication and consensus between the nodes.
== Project Status ==
Prototype, not ready for production
== Project Contacts ==
website: www.postgres-r.org
lead developer: Markus Wanner
mailing list: postgres-r-general on pgfoundry
== General Information ==
Scalability 	targeting dozens of servers and more.	
Read scaling 	yes 	linear to number of nodes
Write scaling 	yes 	very dependent on workload
Triggers/procedures/subtransactions 	yes 	fully supported and transparent to the application
Parallel query 	no 	currently not implemented, but planned
Failover/High Availability 	yes 	configurable for different levels of availability, dependent on GCS
Online provisioning 	yes 	nodes may be added or removed any time
PostgreSQL upgrades 	yes 	designed for upgrades, no official release, yet
Detached node/WAN 	no 	async operation is planned, though
PostgreSQL core modifications required	yes 	
Programming languages 	same as PostgreSQL core 	C, flex and bison.
Licensing 	same as PostgreSQL core 	BSD-like
Complete clustering solution 	no 	requires a GCS
PostgreSQL versions 	CVS HEAD 	
== Clustering Model ==
General Model: shared-nothing, eager (conflict-free), update everywhere (multi-master) database replication
Postgres-R is an extension to the relational database system Postgres, providing efficient, fast and consistent database replication for shared-nothing clusters. It is designed to be as transparent as possible to the client, stable and secure by default.
== Use Case ==
The primary use of Postgres-R is to build load-balancing and highly available database systems on commodity hardware. Furthermore, due to the flexible architecture of Postgres-R it is easily possible to extend or adjust the replication process to many different means. Compared to common single node database systems, a Postgres-R cluster is more reliable and scales better while being cheaper and more flexible. 
Category:Replication
Postgres Women

== What is Postgres Women ==
Postgres Women is a non-profit organization created to encourage and support women to become active members of the PostgreSQL community and foster recognition of their contribution to PostgreSQL development. We firmly believe that by developing a community with a diverse field of contributors, PostgreSQL has an opportunity to truly become the most advanced open source database not only in technological standards, but also in terms of widespread and diverse community involvement.
Be a Postgres Women ally by joining and supporting individuals who identify as women. Contact us via Twitter or mailing-list. Slack channel is in the Postgres team channel as #pgsql-women.
Postgres-XC-GSOC

== Postgres-XC Google Summer of Code 2010 ==
Postgres-XC (previously also known as Postgres-2) is applying for Google Summer of Code 2010.
The idea list for contributions include:
* Support for multiple coordinators. Secondary coordinators register with the primary coordinator. DDL (CREATE TABLE, etc.) goes first through primary coordinator, which synchronizes changes amongst the nodes. Long term we also allow for tracking if secondary coordinators are out of date, and for copying over catalog information to the secondaries.
* Add support for cursors, first for forward only without ORDER BY.
* Backup & Restore
* Expand capability of pooler to handle session parameters.
We prefer to focus on the first item, support for multiple coordinators
Category:Replication
Category:Clustering
Category:Google Summer of Code
PostNuke

== PostNuke ==
PostNuke is a web content management system implemented in PHP.
PostgreSQL support will ship with the upcoming 8.0 release, and any major bugs are considered release blockers. Greg Smith has a project he needs this for and has been fleshing out the port. This bug report shows the current open issues. To give an idea where the likely remaining weak spots are at, re-installation really needs testing. The big open question here is how compatible random PostNuke extensions will be running against a PG database.
Category:Software Ports
Project Hosting

PostgreSQL provides several way to integrate with External Projects, both inside and outside of the core database itself. The PostgreSQL Development Group (PGDG) provides some resources toward hosting PostgreSQL projects.
Some add-on projects are considered critical to PostgreSQL adoption. One such category are drivers for popular programming languages that are not shipped with the database itself (JDBC, ODBC, others). Critical projects can request space on git.postgresql.org along with a mailing list.
github is a popular site for hosting projects using the git SCM. It provides some basic project tools such as an issue tracker, wiki, and releases. There is a PostgreSQL mirror at github you can fork to easily create patches against the database source code. github doesn't provide a good way to provide any sort of mailing list for the project. Some projects have combined github for the main project hosting with Google groups to provide an archived mailing list.
Other sites that are possible places to host a PostgreSQL related project at include:
* sourceforge
* Google code
* Launchpad
* bitbucket
* TuxFamily
Each of these sites has a different mix of features it supports. Support for the preferred SCM of the developer is often the first thing considered, since some of these sites only support one of them. For example, github only handles git, and Launchpad only supports Bazaar.
Category:Community
Category:Development
Proposal for alpha releases

(Current: Alpha release process -- This page is just the proposal for historical reference.)
Idea: make regular formal releases during the development cycle, for easier testing and earlier feedback
Process:
# Commit fest declared closed
# Verify that build farm is green
# Copy commit fest applied patches info to temporary release notes
# Tag
# Run script to build tarball (make distcheck)
# Double-check (by second person)
# Upload
# Announce
Naming:
* proposal: sth. like postgresql-8.5.alpha.200907
* exact punctuation needs further thought, to make readability, sorting, and packageability sane
* the date reflects the closed commit fest, even if the release is made in the following month
Announcing:
* Would like announcements in the technical online press, but don't overdo it.
TBD:
* Complete automation of tarball build (esp. docs, man pages)
* Commit fest release note extraction
* Press contacts and announcement template
Category:PostgreSQL 8.4Category:Release notes
ProposalTemplate

== Proposal Template For a New Feature ==
One-line Summary: Explain in one line regarding the feature so that most hackers can go through it and see if is interesting enough to read the rest of the proposal.
Business Use-case: Explain the problem that you are trying to solve with the proposal.
User impact with the change: What will change from the perspective of existing PostgreSQL user? (Maybe if it is a new feature they never had that syntax support or currently it gives some error, etc.)
Implementation details: If you already have an idea on how it can be implemented.
Estimated Development Time: Man-hours estimated for the proposal to be implemented. (If not sure, mention unknown)
Opportunity Window Period: An end-date if by which if it is not completed, it will be useless to work on the implementation
Budget Money: A range that the sponsor has in mind for the price of development of the proposal
Contact Information: Contact information of the sponsor
Category: Include the text: [[Category:Proposals]] so that MediaWiki categorizes your proposal appropriately.
!
Category:Getting a patch accepted
Próximos eventos

== Eventos PostgreSQL ==
La mayoría de los eventos específicos de PostgreSQL se les realiza un seguimiento en la página de Eventos de PostgreSQL. Esta es una lista de eventos en los que se espera, o les gustaría tener, una presencia de PostgreSQL. Por favor, mantenga los acontecimientos en orden por fecha de inicio y siga los ejemplos existentes. Por favor, también etiquete los acontecimientos con la categoría MediaWiki "Eventos PostgreSQL". Si usted va a ser la organización de un stand de PostgreSQL, por favor, adhiera a a las BoothPolicies. La Coordinacion de las conferencias PostgreSQL Europa esta aqui.
 
Evento 	Página Web 	Fecha 	País 	Ciudad 	Actividades
PgDay Argentina 2013	4ta Jornada Nacional de PostgreSQL 2013	14 de Noviembre de 2013 	Argentina	Buenos Aires	Charlas y Talleres
PgDay Ecuador 2013 	3er Jornada de PostgreSQL 2013 	27 de noviembre del 2013 	Ecuador 	Quito 	Charlas
PgDay Cuba 2013 	5to PGDay Cubano 	28 y 29 de noviembre del 2013	La Habana	Cuba 	Conferencias y Entrenamientos
Para ver la lista completa de eventos relacionados a PostgreSQL ver Events
== Vinculos Externos ==
* O'Reilly conferences
* "Open Source and Linux events in 2008"
Category:PostgreSQL Events
Category:Advocacy
Pseudo encrypt constrained to an arbitrary range

pseudo_encrypt outputs random-looking unique values in the 32-bit range (-2,147,483,648 (-231) through 2,147,483,647 (231 - 1))
To constrain values to a smaller domain [0..N] where N is for instance a power of 10, the Cycle-Walking Cipher technique can be used on top of the Feistel Network.
A variant of pseudo_encrypt() is necessary, with the following changes implemented:
* Reduce the block size to the nearest even power of 2 greater than the range size. For example for the range [0..10,000,000], the nearest is 224 (16,777,216). Shifts and masks will be adjusted in the code for 2 half-blocks of 12 bits each.
* Suppress the self-inverse property, so that a value wouldn't cycle back immediately to itself. It's done by inverting the blocks when they're recombined at the end of the loop.
* Add an outer loop that applies the cipher until the result belongs to the expected range. This is done below in a separate function for clarity.
Sample source code for a 24-bit range:
CREATE FUNCTION pseudo_encrypt_24(VALUE int) returns int AS $$
DECLARE
l1 int;
l2 int;
r1 int;
r2 int;
i int:=0;
BEGIN
 l1:= (VALUE >> 12) & (4096-1);
 r1:= VALUE & (4096-1);
 WHILE i < 3 LOOP
 l2 := r1;
 r2 := l1 # ((((1366 * r1 + 150889) % 714025) / 714025.0) * (4096-1))::int;
 l1 := l2;
 r1 := r2;
 i := i + 1;
 END LOOP;
 RETURN ((l1 << 12) + r1);
END;
$$ LANGUAGE plpgsql strict immutable;
CREATE FUNCTION bounded_pseudo_encrypt(VALUE int, max int) returns int AS $$
BEGIN
 loop
 value := pseudo_encrypt_24(value);
 exit when value <= max;
 end loop;
 return value;
END
$$ LANGUAGE plpgsql strict immutable;
Sample output:
=> select i,bounded_pseudo_encrypt(i, 10000000) as rnd from generate_series(0,10) as x(i);
 i | rnd 
----+---------
 0 | 7388415
 1 | 4878904
 2 | 3247539
 3 | 7670618
 4 | 6551624
 5 | 1212319
 6 | 6156301
 7 | 893851
 8 | 337577
 9 | 4289
 10 | 316941
Query proving that the output is unique, and that the set of values covers exactly the intended range
(might take a few minutes to run)
=> select count(distinct rnd) from
 (select bounded_pseudo_encrypt(i, 10000000) as rnd
 from generate_series(0,10000000) as x(i)
 ) as list
 where rnd between 0 and 10000000;
 count 
----------
 10000001
Psqlrc

psqlrc is the configuration file read by the [psql client]. psql will typically read both a systemwide psqlrc and the per-user one (in ~/.psqlrc on unix-ish systems)
It allows a lot of customization of psql, including defining macros to implement new commands.
TODO: Needs curation. This is a work in progress, collecting existing examples of psqlrc configuration, in the hope someone will go through and pull out some interesting snippets, and maybe a kitchen sink psqlrc that has all the good bits in it.
== Articles ==
* https://robots.thoughtbot.com/an-explained-psqlrc
* https://www.digitalocean.com/community/tutorials/how-to-customize-the-postgresql-prompt-with-psqlrc-on-ubuntu-14-04
* https://opensourcedbms.com/dbms/psqlrc-psql-startup-file-for-postgres/
* https://www.if-not-true-then-false.com/2009/postgresql-psql-psqlrc-tips-and-tricks/
* https://www.citusdata.com/blog/2017/07/16/customizing-my-postgres-shell-using-psqlrc/
* http://pavdmyt.com/better-postgresql-cli-experience-with-psqlrc-tweaks/
* http://www.craigkerstiens.com/2013/02/21/more-out-of-psql/
* http://merlinmoncure.blogspot.com/2012/09/psql-now-with-splash-of-color.html
* http://i-dba.blogspot.com/2014/02/colorizing-psql-prompt-guide.html
* https://simply.name/yet-another-psql-color-prompt.html
* https://www.periscopedata.com/blog/optimizing-your-psql.html
* https://www.depesz.com/2008/05/18/silencing-commands-in-psqlrc/
* https://www.commandprompt.com/blog/psql_tip_change_history_location/
== Examples ==
* https://github.com/e7e6/psqlrc/blob/master/psqlrc
* https://github.com/aziz/dotfiles/blob/master/psqlrc
Psycopg

Psycopg is a PostgreSQL database adapter for the Python programming
language. It conforms to DB-API 2.0
standard.
It is currently at version 2.x, which is a complete rewrite of the original 1.x code to
provide new-style classes for connection and cursor objects and other
sweet candies. Like the psycopg1, psycopg2 was written with the aim of
being very small and fast, and stable as a rock.
Psycopg is designed for heavily multi-threaded applications that create and destroy
lots of cursors and make a conspicuous number of concurrent INSERTs or UPDATEs.
Version 2.2 introduces async support and is compatible with coroutine libraries, allowing its use with nonblocking I/O libraries such as Eventlet, gevent, uGreen.
== Installation ==
From version 2.7 psycopg is distributed as binary package on PyPI:
 $ pip install -U pip # make sure your pip is up-to-date
 $ pip install psycopg2
== Links ==
* Homepage
* Documentation
* Recent changes
* FAQ (An older faq is also available)
* Source code Web interface
* Examples: Using psycopg2 with PostgreSQL
== Mailing Lists ==
* Manage subscription
* Archives
== Getting GIT repo ==
 git clone https://github.com/psycopg/psycopg2.git
Category:Python
Category:Language interface
PUGFrankfurtMain

= Postgres User Group Frankfurt (am Main) =
https://www.meetup.com/Postgres-User-Group-Frankfurt-am-Main/. 
= Upcoming Events =
* Thursday March 21, 2019
** Special MeetUp with Magnus Hagender about Postgres Replication
= Past Events =
* Thursday February 8, 2018 at Proventa Office - First Meetup (Link in German)
* Thursday May 17, 2018 at Proventa Office - Second Meetup (Link in German)
** Robert Haas will present on the brand new zHeap development
** Ilya Kosmodemiansky will present on the things PostgreSQL wanted to learn from commercial databases
* Tuesday July 17, 2018
** Bruce Momjian will present...
* Thursday August 9, 2018 
* Thursday November 8, 2018 
** Stefanie Janine Stölting (PostgreSQL Consultant) will give a talk on "PostgreSQL JSON Features"!
** Together with Jürgen Putz we will discuss "Graphics in the PG Documentation".
* Thursday February 7, 2019 
** Ilya Kosmodemiansky (Data Egret) presents us with the hottest news in the post-world world.
** Jan Karremans (EDB) presents the EFM demo!
= Ideas for future events =
Proposed Agenda:
* 19:00 - 19:15 - Coffee / Beer / Snacks / Pizza
* 19:15 - 19:45 - Presentation 1
* 19:45 - 20:15 - Presentation 2
* 20:15 - 20:30 - Coffee / Beer / Snacks / Pizza
* 20:30 - 21:00 - Q&A / Expert Exchange
* 21:00 - end - Open discussion
 
Category:Users group