<?xml version='1.0' encoding='utf-8'?>
<schedule><version>Firefly</version><conference><title>PGConf.EU 2011</title><start>2011-10-18</start><end>2011-10-21</end><days>4</days><baseurl>https://www.postgresql.eu/events/pgconfeu2011/schedule/</baseurl></conference><day date="2011-10-18"><room name="Other"><event id="218"><start>08:30</start><duration>00:30</duration><room>Other</room><title>Registration</title><abstract /><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/218/</url><track>Breaks</track><persons><person id="31">Undisclosed Speaker</person></persons></event></room><room name="Amsterdam 1"><event id="162"><start>09:00</start><duration>08:00</duration><room>Amsterdam 1</room><title>Performance From Start to Crash</title><abstract>This tutorial starts with an introduction to the most common setups tasks and best practices to get good performance from a PostgreSQL server.  And by the end, you'll learn how to tune a PostgreSQL server the only way that matters some days:  when the server performance problems are so bad it has crashed, and you have no idea what's wrong.  This is a unique chance to see the habits and tools used by someone who faces that problem constantly, watching the repair of a live demo server that's crashed due to overload.

PostgreSQL is a database system that can deliver excellent performance for a wide variety of applications.  But getting the performance related aspects of a new PostgreSQL deployment right can be stressful, particularly if you're new to the database and its quirks.  The first part of this tutorial goes over the most common things new PostgreSQL installations do that sabotages their potential performance, and how to avoid making some of those mistakes

And when performance drops far enough, it's possible for the server to slow to where it's essentially down, or even crash altogether.  Knowing what to do then is just as important, but it's hard to practice for that day.

Greg is going to login to a server that at the beginning is performing terribly.  By the end, it will be running smoothly.  You get to watch every step of the way, to see what change were made, and what information collected prompted them.  One day, you may find your PostgreSQL database server is unresponsive or down due to performance issues.  This session gives you a unique opportunity to prepare.  Before it happens to you (again?), you can watch how an expert who does this exact type of support and consulting every day responds.

The material covered will introduce you to:

* Avoiding common flaws made by new PostgreSQL deployments
* Basic PostgreSQL configuration tuning techniques
* Proactive monitoring you should be doing before your problems start
* Tools and techniques to locate the source of problems on a slow server
* PostgreSQL specific monitoring tools
* Good performance tuning methodology
</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/162/</url><track>Training, English</track><persons><person id="81">Greg Smith</person></persons></event></room><room name="Amsterdam 2"><event id="214"><start>09:00</start><duration>03:30</duration><room>Amsterdam 2</room><title>Streaming replication, hot standby and synchronous replication</title><abstract>PostgreSQL 9.0 added streaming binary replication and Hot Standby, and PostgreSQL 9.1 adds the ability to make this synchronous for even more security.

This session will start with a recap of the existing Warm Standby technology, and then move on to the changes in 9.0 for building both Warm and Hot standby solutions, and finally look at the improvements to this in 9.1 as well as the new synchronous functionality.</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/214/</url><track>Training, English</track><persons><person id="1">Magnus Hagander</person></persons></event></room><room name="Amsterdam 3"><event id="163"><start>09:00</start><duration>08:00</duration><room>Amsterdam 3</room><title>Mastering PostgreSQL Administration</title><abstract>This one day class covers all aspects of PostgreSQL administration, including installation, security, file structure, configuration, reporting, backup, daily maintenance, monitoring activity, disk space computations, and disaster recovery.

This three part presentation series covers all aspects of PostgreSQL administration, including installation, security, file structure, configuration, reporting, backup, daily maintenance, monitoring activity, disk space computations, and disaster recovery. It shows how to control host connectivity, configure the server, find the query being run by each session, and find the disk space used by each database.</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/163/</url><track>Training, English</track><persons><person id="44">Bruce Momjian</person></persons></event></room><room name="Other"><event id="220"><start>12:30</start><duration>01:00</duration><room>Other</room><title>Lunch</title><abstract /><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/220/</url><track>Breaks</track><persons><person id="31">Undisclosed Speaker</person></persons></event></room><room name="Amsterdam 2"><event id="165"><start>13:30</start><duration>03:30</duration><room>Amsterdam 2</room><title>Slony, still a useful replication tool</title><abstract>The training will start with a quick overview of Slony's features and
its community. Then, we'll move to the installation and configuration of
Slony. That will allow us to see it working, which we'll bring us to
talk about the administration tasks it involves.</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/165/</url><track>Training, English</track><persons><person id="3">Guillaume Lelarge</person></persons></event></room></day><day date="2011-10-19"><room name="Other"><event id="219"><start>08:30</start><duration>01:00</duration><room>Other</room><title>Registration</title><abstract /><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/219/</url><track>Breaks</track><persons><person id="31">Undisclosed Speaker</person></persons></event></room><room name="Amsterdam 3"><event id="149"><start>09:30</start><duration>00:15</duration><room>Amsterdam 3</room><title>Welcome and opening</title><abstract>Welcome, opening of the conference and last-minute information</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/149/</url><track>General</track><persons><person id="1">Magnus Hagander</person></persons></event><event id="215"><start>09:45</start><duration>01:00</duration><room>Amsterdam 3</room><title>Keynote: Afilias Winning Bet on Open Source</title><abstract>In 2001, Afilias launched .INFO, the first new gTLD ever approved by ICANN.  To support its new registry platform, Afilias committed to using open source technology with PostgreSQL.  A great deal of consideration was taken to make this strategic choice, on costs, risks, quality and ongoing support for the technology.  Over the past 10 years, Afilias has realized numerous benefits and key learnings from its winning strategy and from its involvement in the open source communities.   Over the next 5 years, as the domain industry shifts considerably, so will its technologies, applications and business models.  What role will open source play in these future trends?</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/215/</url><track>General</track><persons><person id="97">Ram Mohan</person></persons></event></room><room name="Other"><event id="221"><start>10:45</start><duration>00:25</duration><room>Other</room><title>Coffee</title><abstract /><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/221/</url><track>Breaks</track><persons><person id="31">Undisclosed Speaker</person></persons></event></room><room name="Amsterdam 2"><event id="153"><start>11:10</start><duration>00:50</duration><room>Amsterdam 2</room><title>Introducing ISO 21090 Healthcare Datatypes</title><abstract>The HL7 standard is widely used to exchange medical information electronically. As a part of the standard, HL7 defines scalar communication data types like physical quantity, point in time and concept descriptor but also complex types such as interval types, collection types and probabilistic types. The HL7 data types in its second revision called R2 has become an ISO standard in 2008.
We describe an implementation in the PostgreSQL database server and show that the database server can effectively execute scientific calculations with units of measure, supports a large number of operations on time points and intervals, and can perform operations that are akin to a medical terminology server.
</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/153/</url><track>Developer, English</track><persons><person id="79">Yeb Havinga</person></persons></event></room><room name="Amsterdam 1"><event id="144"><start>11:10</start><duration>00:50</duration><room>Amsterdam 1</room><title>Migration to PostgreSQL - a holistic view</title><abstract>There are many reasons to migrate to PostgreSQL. There are many tools and people to help that migration; free and commercial. This talk will focus on other aspects of a migration, flash light on reasons why some users still use other databases. Aspects of power and fear; various aspects of lock-in shall be discussed; business aspects of migations and wagers of risks will be discussed in a entertaining manner.</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/144/</url><track>DBA, English</track><persons><person id="78">Harald Armin Massa</person></persons></event></room><room name="Amsterdam 3"><event id="148"><start>11:10</start><duration>00:50</duration><room>Amsterdam 3</room><title>PostgreSQL 9.1 - what's new</title><abstract>PostgreSQL 9.1 contains hundreds of updates and new features. This talk will give an overview of the most popular and important ones.</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/148/</url><track>DBA, English</track><persons><person id="1">Magnus Hagander</person></persons></event><event id="159"><start>12:10</start><duration>00:50</duration><room>Amsterdam 3</room><title>Look Out The Window Functions (and free your SQL)</title><abstract>Window functions provide answers to common questions from real-world use cases, so they are gaining currency among application developers.
Prior to their introduction in PostgreSQL 8.4, lots of people (including me) used to solve that kind of problems in a less efficient way by writing equivalent algorithms in imperative languages.

In this talk we will walk through some minimal examples to show the capabilities of window functions, explain their advantages over
imperative solutions, and summarize the reasons why people should invest resources in upgrading some of their queries to window functions.

The talk will also include benchmarks on larger datasets, version-awareness of the various features, and how well (or badly) do window functions relate with other PostgreSQL features.
</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/159/</url><track>Developer, English</track><persons><person id="34">Gianni Ciolli</person></persons></event></room><room name="Amsterdam 2"><event id="146"><start>12:10</start><duration>00:50</duration><room>Amsterdam 2</room><title>PostgreSQL at the center of your dataverse</title><abstract>A look at the new SQL/MED features in PostgreSQL 9.1 and how they can be used to connect PostgreSQL to any data source.

In this talk I will discuss the new SQL/MED features in PostgreSQL 9.1. We will examine how PostgreSQL can interface with external data sources, including files, web services, and both relational and non-relational databases, and how we may use that ability to our advantage.

Finally, we will review the code behind a simple Foreign Data Wrapper to another database to see how easy it can be to add support for new data sources with just a little C programming experience.</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/146/</url><track>Developer, English</track><persons><person id="2">Dave Page</person></persons></event></room><room name="Amsterdam 1"><event id="178"><start>12:10</start><duration>00:50</duration><room>Amsterdam 1</room><title>Geo in your database : PostGIS</title><abstract>It is usually stated that 80% of data has a spatial component. To be able to use this caracteristic at its full extent, companies and administrations set up geographical information systems.

GIS were historically desktop tools, but evolved into distributed architectures, strongly web-oriented. In this context, PostgreSQL with its PostGIS plugin are key components for the data storage and manipulation layer. Be it for cartographic visualization, custom spatial data manipulation, geo-BI or geomarketing, PostgreSQL/PostGIS answers the needs on par or better than its main competitors, namely Oracle Spatial, SQL Server or MySQL. 

Based on ISO and OGC norms, PostGIS let the user deal with simple geographical features (points, lines, polygons), or more complex ones. Spatial data indices lead to high performances to query those geographical features. Numerous operators and functions allow plenty of geometric processing capabilities : creation, modification, feature relationship computations (intersections, proximity…), and even more complex processes, such as geometry aggregation, convex hull, geometric simplification...

PostGIS also provides export functions, facilitating systems interoperability. JSON export makes it easy to write web applications based on OpenLayers, KML export gives a direct Google Earth visualization, GML aims at applications based on OGC standards (e.g. TinyOWS).

PostGIS is currently becoming an OSGeo project, which will increase its quality and organisation. The next 2.0 branch will be full of new features, such as rasters, routing, geodesy, 3D support and more. </abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/178/</url><track>DBA, English</track><persons><person id="56">Vincent Picavet</person></persons></event></room><room name="Other"><event id="222"><start>13:00</start><duration>01:00</duration><room>Other</room><title>Lunch</title><abstract /><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/222/</url><track>Breaks</track><persons><person id="31">Undisclosed Speaker</person></persons></event></room><room name="Amsterdam 1"><event id="174"><start>14:00</start><duration>00:50</duration><room>Amsterdam 1</room><title>Heralding the Death of NoSQL </title><abstract>The killer feature of many popular NoSQL databases is document based storage. It isn't often that real-word data is truly relational, and it's painful to persist rich domain models across millions of little tables in the pursuit of third normal form.

PLV8 embeds the super-fast V8 JavaScript engine into Postgres, which in turn makes Postgres the best document database in the world. It also brings the full power of arbitrary JavaScript functions to SQL.

We will go into what you can do today with PLV8, how it can be used to give Postgres near-native JSON support, and what it will bring in the future.</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/174/</url><track>Developer, English</track><persons><person id="87">Will Leinweber</person></persons></event></room><room name="Amsterdam 2"><event id="206"><start>14:00</start><duration>00:50</duration><room>Amsterdam 2</room><title>Best practices with Ora2Pg</title><abstract>This talk will start with an introduction to the project and its history. We will continue with the best practices using Ora2Pg for Oracle to PostgreSQL migration. We will cover much of the functionalities coming in the last release which contains significant speed improvement and new features. An overview of the future development of Ora2Pg will be provided. </abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/206/</url><track>French</track><persons><person id="94">Gilles Darold</person></persons></event></room><room name="Amsterdam 3"><event id="127"><start>14:00</start><duration>00:50</duration><room>Amsterdam 3</room><title>Explaining the Postgres Query Optimizer</title><abstract>The optimizer is the "brain" of the database, interpreting SQL queries and determining the fastest method of execution. This talk uses the explain command to show how the optimizer interprets queries and determines optimal execution. The talk will assist developers and administrators in understanding how Postgres optimally executes their queries and what steps they can take to understand and perhaps improve its behavior. </abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/127/</url><track>DBA, English</track><persons><person id="44">Bruce Momjian</person></persons></event></room><room name="Other"><event id="223"><start>14:50</start><duration>00:30</duration><room>Other</room><title>Tea</title><abstract /><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/223/</url><track>Breaks</track><persons><person id="31">Undisclosed Speaker</person></persons></event></room><room name="Amsterdam 1"><event id="203"><start>15:20</start><duration>00:50</duration><room>Amsterdam 1</room><title>Data Distribution with pg_amqp &amp; RabbitMQ</title><abstract>Expanding on the "On Rabbits and Elephants" lightning talk from pgCon 2011, this talk will cover how to implement scalable data-distribution models using RabbitMQ as the message broker for PostgreSQL trigger-based events. Using real-world examples and a live proof-of-concept demo, this talk will demonstrate the power and flexibility of using AMQP and RabbitMQ for publishing PostgreSQL based events.

Expanding on the "Golconde" model of data distribution, learn how to turn your PostgreSQL events into a fire hose of data that may be used for everything from trending and analysis to providing a data source to populate data warehouses and for use with CEP systems like Esper.</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/203/</url><track>Developer, English</track><persons><person id="19">Gavin M. Roy</person></persons></event></room><room name="Amsterdam 2"><event id="121"><start>15:20</start><duration>00:50</duration><room>Amsterdam 2</room><title>Asynchronous Notifications for Fun and Profit</title><abstract>Asynchronous notifications are a messaging mechanism built into
PostgreSQL to allow it to be used as a message broker in distributed
environments.

This talks sheds some light on asynchronous notifications and shows how
they can be used from various programming languages and how distributed
programs can be decoupled from each other.

If you want to now how the object oriented MVC paradigm or the Observer
design pattern can be applied to the PostgreSQL database, this talk is
for you.
</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/121/</url><track>Developer, English</track><persons><person id="28">Marc Balmer</person></persons></event></room><room name="Amsterdam 3"><event id="156"><start>15:20</start><duration>00:50</duration><room>Amsterdam 3</room><title>Synchronous Replication and Durability Tuning</title><abstract>One of the most anticipated features in PostgreSQL 9.1 is Synchronous Replication.  PostgreSQL has always respected the durability aspects of ACID compliance.  Extending that to reach onto multiple servers significantly expands the suitability of the database for business critical applications.  And you only have to pay for its overhead when you need it.

The inevitable downside of Synchronous Replication is its impact on server commit speed.  And recent trends in the database industry have proven some applications are willing to accept durability loss, when it must be sacrificed to reach performance goals.

But the innovative design used in PostgreSQL doesn't force you to make this sort of decision at the database level.  Every individual commit can specify its durability requirements at any time--even in the middle of a transaction!  Being able to classify your need at such a fine level allows PostgreSQL an unprecedented range of options in this area.  Mission critical data that needs synchronous commit can coexist with high volume/best effort data, with each transaction fine-tuned to its position in the reliability vs. speed trade-off spectrum.

This talk will cover:

* How Synchronous Replication is implemented in PostgreSQL 9.1
* High Availability considerations when using Sync Rep
* Available transaction level durability options, and their expected commit performance in common scenarios
* Evaluating and improving the impact of latency on performance</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/156/</url><track>DBA, English</track><persons><person id="81">Greg Smith</person><person id="17">Simon Riggs</person></persons></event></room><room name="Amsterdam 2"><event id="168"><start>16:20</start><duration>00:50</duration><room>Amsterdam 2</room><title>Review of Patch Reviewing</title><abstract>Patch reviewing is an important part of moving PostgreSQL forward. It's critical for anyone submitting patches to PostgreSQL to also understand how to review patches, too. This talk will go through the steps of patch review, including the most important piece- code review.</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/168/</url><track>Developer, English</track><persons><person id="84">Stephen Frost</person></persons></event></room><room name="Amsterdam 1"><event id="125"><start>16:20</start><duration>00:50</duration><room>Amsterdam 1</room><title>Troubleshooting Slony</title><abstract>Slony is a trigger based replication system for PostgreSQL that supports multiple replication sets, cascaded replicas and controlled switchovers.   Sometimes database administrators find that their Slony clusters are not behaving as they expect.  This talk will describe the steps to take to troubleshoot a Slony cluster.   The audience will learn about the different components that make up Slony and will learn how data flows through a Slony cluster.  Common issues encountered with Slony clusters will also be discussed.</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/125/</url><track>DBA, English</track><persons><person id="73">Steve Singer</person></persons></event></room><room name="Amsterdam 3"><event id="201"><start>16:20</start><duration>00:50</duration><room>Amsterdam 3</room><title>Metering the smart way - a smart grid for the datacenter</title><abstract>Green IT is all over the place but in reality most modern datacenters don't really have the necessary monitoring in place to actually figure out what all the power is used for.
This talk is about using a very IT centric approach to the whole building automation problem of gathering, analying and applying changes out of thousends of sensors and metering devices.
The presented solution is using PostgreSQL as a central datastore and business logic container, getting external datafeeds from both traditional Modbus and M-Bus devices and more "modern" devices using IP-based communication.
The Talks will also give some insight into how the experience gained with using PostgreSQL in this kind of scenary is used in a field prototype for a an actual smartmeter deployment at a medium sized utility company.</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/201/</url><track>Developer, English</track><persons><person id="61">Stefan Kaltenbrunner</person></persons></event></room></day><day date="2011-10-20"><room name="Amsterdam 3"><event id="158"><start>09:30</start><duration>00:50</duration><room>Amsterdam 3</room><title>Improving VACUUM Suction</title><abstract>PostgreSQL's transaction visibility model has one major downside.  Every block written to the database has to be revisited and rewritten at least once, to perform multiple types of visibility cleanup.  Those writes are even more frequent if older items are regularly updated or deleted from the database.

While the default settings in the database work fine for smaller installations, larger ones can find that this vacuum cleanup work is extremely hard to handle.  If your PostgreSQL installation reaches the terabyte scale, you will end up grappling with vacuum problems.  The only question is how long you can put it off, not whether you'll have to deal with the issue.

And making changes to the configuration parameters involved requires changing some difficult to understand tuning parameters.  But there are several options available to help here, particularly if you learn how to track and tune the background activity done by the autovacuum daemon.  This session will cover:

* Monitoring if VACUUM is working
* Logging troublesome vacuum work
* Avoiding peak periods with server configuration changes
* Understanding and estimating the activity of cost-based vacuuming
* Improvements proposed for PostgreSQL 9.2 (with backports to earlier versions via source code builds)</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/158/</url><track>DBA, English</track><persons><person id="81">Greg Smith</person></persons></event></room><room name="Amsterdam 1"><event id="183"><start>09:30</start><duration>00:50</duration><room>Amsterdam 1</room><title>londiste 3 et slony 2.1</title><abstract>Ces deux systèmes de réplication asynchrone préparent chacun une nouvelle version. Elles apportent un lot considérable d'améliorations tant sur les fonctionnalités que sur l'administration et mettent à niveau les deux systèmes.

Voyons comment londiste s'est ouvert à des scénarios plus complexes et comment slony a facilité la vie de l'administrateur.
</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/183/</url><track>French</track><persons><person id="57">Cédric Villemain</person></persons></event></room><room name="Amsterdam 2"><event id="209"><start>09:30</start><duration>00:50</duration><room>Amsterdam 2</room><title>vFabric Data Director</title><abstract>VMware vFabric Data Director is self-service database provisioning and
cloud automation platform that enables organizations to offer
database-as-a-service (DBaaS) inside their datacenters.  PostgreSQL is the first database enabled on Data
Director.  This session will give you an in-depth look at vFabric Data
Director with PostgreSQL and a technical deep dive into vPostgres which is PostgreSQL modified to run better in virtualized environments taking advantage of vmware vSphere platform.

This session is sponsored by VMWare.</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/209/</url><track>General</track><persons><person id="95">Poojan Kumar</person></persons></event></room><room name="Other"><event id="224"><start>10:20</start><duration>00:30</duration><room>Other</room><title>Coffee</title><abstract /><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/224/</url><track>Breaks</track><persons><person id="31">Undisclosed Speaker</person></persons></event></room><room name="Amsterdam 1"><event id="182"><start>10:50</start><duration>00:50</duration><room>Amsterdam 1</room><title>Serializable Snapshot Isolation</title><abstract>Before PostgreSQL 9.1, serializable isolation level was not in fact fully serializable, as the SQL specification intended. 9.1 introduces a new feature called Serializable Snapshot Isolation, which fixes that. In this presentation, I will explain the anomalies that can occur without Serializable Snapshot Isolation, how SSI avoids them, and what you need to know about SSI when developing applications on PostgreSQL.</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/182/</url><track>Developer, English</track><persons><person id="11">Heikki Linnakangas</person></persons></event></room><room name="Amsterdam 3"><event id="172"><start>10:50</start><duration>00:50</duration><room>Amsterdam 3</room><title>Leveraging filesystem snapshots to provide copies of production data for testing </title><abstract>Developers hate working with test data. It isn't representative of the working dataset. However, providing multiple full copies of production is slow to refresh and consumes lots of disk. This talk will show how you can use filesystem snapshots to produce copies of your production environment without service interruption and with minimal overhead.

Some of the advantages of using the proposed strategy over a plain dump/restore include:

* Nightly refreshes of the copies of prod with mere seconds of dev downtime
* Provide multiple copies using only slightly more than the space of one copy
* Revert a copy back to the nightly refresh almost instantly
* Provide a new copy almost instantly, using almost no additional disk
* No production downtime involved

A few methods of snapshotting will be discussed including LVM2 (the Linux Volume Manager), btrfs, and SAN/NAS.</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/172/</url><track>DBA, English</track><persons><person id="86">Jon Erdman</person></persons></event></room><room name="Amsterdam 2"><event id="138"><start>10:50</start><duration>00:50</duration><room>Amsterdam 2</room><title>Extensions are good for business logic</title><abstract>PostgreSQL 9.1 features extensibility to the next level.  While this often is a concern for C-developers among us, this talk will detail why extensions are a first-class facility for anyone doing Stored Procedures, whatever their implementation language.

If you ever did type CREATE OR REPLACE FUNCTION, be it in LANGUAGE SQL, then you're in!</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/138/</url><track>DBA, English</track><persons><person id="14">Dimitri Fontaine</person></persons></event><event id="175"><start>11:50</start><duration>00:50</duration><room>Amsterdam 2</room><title>Exposing the power of PostgreSQL to Ruby </title><abstract>Powerful datatypes such as hstore and json give PostgreSQL the most compelling feature of many NoSQL databases, which is management of semi structured data. Unfortunately the popular Ruby ORMs try very hard to equalize all databases, so these and other features often go unnoticed or underappreciated. 

While there are some Ruby libraries providing application-level bindings for these features, they are generally new or otherwise not well-known. Developers are also often further discouraged by having to sacrifice the benefits of their ORM to use these libraries. Fortunately, the situation is starting to improve.

We will go in to detail what was needed to bring hstore support to Ruby, survey the current PostgreSQL and Ruby landscape, and discuss what needs to happen in the near future to improve their relationship.</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/175/</url><track>Developer, English</track><persons><person id="87">Will Leinweber</person></persons></event></room><room name="Amsterdam 3"><event id="185"><start>11:50</start><duration>00:50</duration><room>Amsterdam 3</room><title>A PostgreSQL Service: Advantages and Trade-offs</title><abstract>Given easy access to an unlimited pool of pay-by-the-second databases, new use cases emerge.

For example, if creating a new database replica is simply a matter of specifying a single command line, why not run all analytics on powerful, short-lived clones rather than on the production master?

Further, by taking advantage of a database service, you can get access to an environment with multiple layers of robust backup systems, a set of tools to make you more productive, and offload some of the work to a provider.

But these conveniences come with a cost; virtualized resources are often less performant than dedicated hardware and force a developer to take different considerations when designing their application, and as a user, you are asked to relinquish some of the powers you may be accustomed to, such as SSH access and cluster superuser.

This talk will also touch on some of the technology we've built to provide back to the community and some of the core features we're hoping to help bring into future releases of Postgres.</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/185/</url><track>DBA, English</track><persons><person id="90">Peter van Hardenberg</person></persons></event></room><room name="Amsterdam 1"><event id="105"><start>11:50</start><duration>00:50</duration><room>Amsterdam 1</room><title>Fast GiST index build</title><abstract>Currently GiST index don't have any bulk load functionality. It have to create new index by entry insertion one by one. Thus, GiST index build can be very slow when index doesn't fit to cache. This talk presents application of buffer tree to GiST index build. This application allows to dramatically reduce IO load during GiST index build. Also tradeoffs between CPU and IO load and index quality is planned to being discussed. </abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/105/</url><track>DBA, English</track><persons><person id="64">Alexander Korotkov</person></persons></event></room><room name="Other"><event id="225"><start>12:40</start><duration>01:00</duration><room>Other</room><title>Lunch</title><abstract /><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/225/</url><track>Breaks</track><persons><person id="31">Undisclosed Speaker</person></persons></event></room><room name="Amsterdam 1"><event id="150"><start>13:40</start><duration>00:50</duration><room>Amsterdam 1</room><title>More Mistakes Were Made</title><abstract>Ever have a code release go horribly wrong? Have a routine Postgres upgrade turn into 12 hours of downtime? Had to field angry phone calls from engineers, customers and your boss?

Sometimes things go horribly wrong. This talk will teach you how to plan for the worst, minimize risk and recover gracefully from failure.

In an ideal world, code would have complete test coverage, releases would be seamless and databases wouldn’t require downtimes to upgrade. The fact is, most companies still have to manage systems upgrades and code deployment that includes downtime. This talk is for you.

Elements to successful downtimes include: proper testing, automated checks for success, completely failback plans, and a timeline. Postgres-specific information for HA, failover and disaster recovery will be included.

We’ll go over useful tools for keeping track of what is going on before, during and after a downtime, and talk through good and bad communication for employees and customers.

We’ll also talk about how non-technical people can evaluate technical change. And how having the right stakeholders involved from the beginning of the planning process reduces risk.

Stories to illustrate success and failure will come from Selena Deckelmann’s 15 years in education, public and private sectors, as a consultant, DBA and IT manager.</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/150/</url><track>DBA, English</track><persons><person id="65">Selena Deckelmann</person></persons></event></room><room name="Amsterdam 2"><event id="170"><start>13:40</start><duration>00:50</duration><room>Amsterdam 2</room><title>Writing Django Extensions for PostgreSQL</title><abstract>Django is a popular open-source web framework written in Python that makes it easier for developers to write sophisticated applications. Django also provides the means to be "easily" extended, allowing the developer to write new features without creating messy hacks. "Easily" is best used in quotes, as while the interface is well-defined, it can take a bit of effort to get your extension to work the way you want it to.

This presentation will demonstrate how to write extensions for PostgreSQL that take advantage of its native datatypes and features. We will briefly cover the basics of the Django ORM that serves as the interaction layer with the database, and then go through some example extensions that map Python to native PostgreSQL datatypes, e.g. geometric types, time intervals, enumerated types, and more. The talk will conclude with some thoughts on where it is better to use pure SQL than writing a Django extension. Some familiarity with Django will be assumed for this talk.</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/170/</url><track>Developer, English</track><persons><person id="6">Jonathan S. Katz</person></persons></event></room><room name="Amsterdam 3"><event id="160"><start>13:40</start><duration>00:50</duration><room>Amsterdam 3</room><title>Debugging complex SQL queries with writable CTEs</title><abstract>There are many reasons to prefer declarative languages such as SQL instead of imperative ones; for instance, the machine can make optimisations that you couldn't possibly (or just didn't) see.
Furthermore, future versions of the machine can become more clever and optimise better, while your imperative code will stand still.

On the other hand, the more you delegate the machine and the more difficult it becomes to fix problems when they happen.
For instance, this is the case when you have a very complex query with lots of subqueries, and even using EXPLAIN output you still can't understand why the output differs from what you expected.

In this talk we show how CTE (a.k.a. WITH queries), and more precisely the writable ones introduced in PostgreSQL 9.1, can provide a valuable debugging and tracing tool.
We will provide concrete examples and try to point out pitfalls.</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/160/</url><track>Developer, English</track><persons><person id="34">Gianni Ciolli</person></persons></event></room><room name="Amsterdam 2"><event id="191"><start>14:40</start><duration>00:50</duration><room>Amsterdam 2</room><title>Port databases from MySQL to PostgreSQL</title><abstract>Since the purchase of MySQL by Sun and later by Oracle, many users are confused and look around for alternatives. PostgreSQL is one of these alternatives and see's a raising number of companies and users porting away from MySQL. This talk shows how to port a database from MySQL to PostgreSQL, is also discussed common pitfalls and problems.</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/191/</url><track>DBA, English</track><persons><person id="30">Andreas Scherbaum</person></persons></event></room><room name="Amsterdam 3"><event id="202"><start>14:40</start><duration>00:50</duration><room>Amsterdam 3</room><title>What use are the statistics views?</title><abstract>This talk will present the statistics gathered by the collector. It will decrypt each statistics views, and explain how to use them. Some related tools will be discussed.</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/202/</url><track>DBA, English</track><persons><person id="3">Guillaume Lelarge</person></persons></event></room><room name="Amsterdam 1"><event id="166"><start>14:40</start><duration>00:50</duration><room>Amsterdam 1</room><title>Connecting the Debian and PostgreSQL worlds</title><abstract>PostgreSQL is an ecosystem with a large number of add-on modules and extensions that provide additional functionality. Like the server itself, these are distributed in source form. On the other hand, Debian is an operating system that provides a well-integrated set of pre-built binary packages. Each Debian distribution includes one or two major PostgreSQL versions, along with a collection of modules and extensions for these versions.

Our project aims to fill the missing gaps in this selection. We provide packages for the PostgreSQL versions supported by the PostgreSQL developers but not yet/not anymore in Debian, and build the available modules and extensions for these. This extends to several architectures, as well to providing Ubuntu packages. Eventually, we would like to provide an official repository at apt.postgresql.org. The project is still in the early development phase. This talk gives an overview on the challenges and goals of the project.</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/166/</url><track>Developer, English</track><persons><person id="82">Christoph Berg</person></persons></event></room><room name="Other"><event id="226"><start>15:30</start><duration>00:30</duration><room>Other</room><title>Tea</title><abstract /><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/226/</url><track>Breaks</track><persons><person id="31">Undisclosed Speaker</person></persons></event></room><room name="Amsterdam 3"><event id="217"><start>16:00</start><duration>00:50</duration><room>Amsterdam 3</room><title>Lightning talks</title><abstract>Lightning Talks - the high intensity part of conference which only
uses 5 minutes of attention span at a time.

The rules for Lightning Talks are easy: you can talk about anything,
but not longer than 5 minutes. The audience really prefers the talks
to be related to PostgreSQL (the worlds most advanced OpenSource
Database, the project, the community, the conference, the ecosystem)

To optimally prepare for your awesome Lightning Talk: give your
presentation as HTML, OpenOffice, PDF, PPT or Prezi to the Lightning
Talk Man Harald Armin Massa hours before the scheduled time. If you
cannot do that, please make sure your laptop/tablet/mobilephone is
able to communicate with the projector, especially that you have all
necessary adapters and Jobs-plugs and you have the correct drivers,
settings and licences.
</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/217/</url><track>General</track><persons><person id="78">Harald Armin Massa</person></persons></event></room></day><day date="2011-10-21"><room name="Amsterdam 3"><event id="199"><start>09:30</start><duration>00:50</duration><room>Amsterdam 3</room><title>PostgreSQL Roadmap</title><abstract>Although PostgreSQL doesn't publish an official roadmap, Simon is often the developer people ask about what's happening next on the PostgreSQL project. Here is his personal viewpoint on life, the universe and databases. He will use the voodoo phrases NoSQL, DevOps, Cloud and Multi-master and then tell you what's actually going to happen, when and why. </abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/199/</url><track>General</track><persons><person id="17">Simon Riggs</person></persons></event></room><room name="Amsterdam 1"><event id="210"><start>09:30</start><duration>00:50</duration><room>Amsterdam 1</room><title>What's new in pgpool-II 3.1</title><abstract>We'll try to present here what's new in pgpool-II version 3.1 to be released sept/oct 2011.

We'll also talk a bit of what will be in later version, and how pgpool-II will use PG 9.1 features.
</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/210/</url><track>DBA, English</track><persons><person id="13">Jean-Paul Argudo</person></persons></event></room><room name="Amsterdam 2"><event id="126"><start>09:30</start><duration>00:50</duration><room>Amsterdam 2</room><title>Relational Database Designer for pgAdmin</title><abstract>Luis Ochoa took care of one of the PostgreSQL GSoC 2011 projects : a database designer for pgAdmin. And Guillaume Lelarge was his mentor.

This talk will show how pgAdmin database designer works, from a user perspective, and the benefits of using it instead of handmade scripts with SQL/DDL database models. Its future within pgAdmin will be discussed. And the two speakers would love to hear your suggestions, and feature requests.</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/126/</url><track>Developer, English</track><persons><person id="3">Guillaume Lelarge</person><person id="74">Luis Ochoa</person></persons></event></room><room name="Other"><event id="227"><start>10:20</start><duration>00:30</duration><room>Other</room><title>Coffee</title><abstract /><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/227/</url><track>Breaks</track><persons><person id="31">Undisclosed Speaker</person></persons></event></room><room name="Amsterdam 3"><event id="157"><start>10:50</start><duration>00:50</duration><room>Amsterdam 3</room><title>Bottom-up Database Benchmarking</title><abstract>Databases have unique consistency and workload requirements that still make hardware performance and choice critical.  And particularly with the complexity of today's hardware, running your own bottom-up benchmarks is vital for defending against the very common hardware vendor errors you should expect to happen to you eventually, not be surprised by.  A large percentage of new server hardware ships with at least one major performance issue.  Deploy a production server without making sure the hardware itself performs as expected, and troubleshooting the resulting problems is vastly more difficult.

And the information you need to know to make informed hardware changes changes constantly.  This session covers recent, unique research into database performance tuning, including a variety of custom-designed tools aimed at this area.  The _stream-scaling_ project provides a new way to visualize how memory performance scales with the number of active cores involved in the workload, a vital component to quantify on today's many core designs when running a database server.  _stream-scaling_ highlights the speed vs. capacity trade-offs in server memory you must be aware of to size the latest server hardware appropriately.  The recently developed _seek-scaling_ uses the same approach to reinvent measuring disk speed for databases much larger than the RAM in the server.  _seek-scaling_ makes it easy to compare traditional disk arrays against the latest memory and flash based devices.  And the benchmarking automation set of _pgbench-tools_ is now easier than ever to use for comparing the performance of different systems or server configurations.</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/157/</url><track>DBA, English</track><persons><person id="81">Greg Smith</person></persons></event></room><room name="Amsterdam 1"><event id="186"><start>10:50</start><duration>00:50</duration><room>Amsterdam 1</room><title>Reliable Cloud Databases with WAL-E</title><abstract>WAL-E is an open source tool designed to continuously archive your business's Postgres data to Amazon's S3 cloud storage service. It can help with recovery from failures even when the individual database servers are not individually very reliable, which is the case in many common cloud database deployments.

Individual systems in any environment can't be relied on to save critical data perfectly. No matter how much reundancy your database server includes, you still need to save backups elsewhere. The fact that no single machine can ever be reliable enough is particularly obvious when deploying servers onto a cloud deployment such as Amazon's EC2 service. Individual nodes are never expected to be as reliable as a traditional dedicated database server.

The architecture at cloud service provider Heroku solves this problem by reversing the normal approach to mission critical database deployment: they make the backups the most reliable part of the system. PostgreSQL's write-ahead log (WAL) mechanism can be used to make streaming, real-time backups of your database. The WAL-E tool developed there archives this data into Amazon's S3 storage, which so far boasts a perfect track record for storing all data ever committed to it. This approach is currently in use protecting over 100,000 Postgres databases, and has allowed Heroku to survive major interruptions in Amazon's cloud infrastructure with minimal data loss. In this session, learn how and why WAL-E was implemented, and how you can use it to keep your own data safe and secure.</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/186/</url><track>DBA, English</track><persons><person id="91">Daniel Farina</person></persons></event></room><room name="Amsterdam 2"><event id="154"><start>10:50</start><duration>00:50</duration><room>Amsterdam 2</room><title>New plugin architecture in phpPgAdmin and what to expect from it</title><abstract>This summer, thanks to the Google Summer of Code (GSoC), Leonardo Augusto Sápiras, a student from Brazil, rewrote the whole plugin architecture in phpPgAdmin.

Discover with Leonardo and Jehan-Guillaume de Rorthais, one of the phpPgAdmin project developer, this plugin architecture, its status and how plugins will integrate with phpPgAdmin.

Then, this is a great opportunity to discover the existing plugins, and the future ones that were waiting for this project to end up !</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/154/</url><track>Developer, English</track><persons><person id="5">Jehan-Guillaume (ioguix) de Rorthais</person><person id="96">Leonardo Augusto Sapiras</person></persons></event></room><room name="Amsterdam 3"><event id="147"><start>11:50</start><duration>00:50</duration><room>Amsterdam 3</room><title>The PostgreSQL replication protocol, tools and opportunities</title><abstract>The new binary replication protocols and tools in PostgreSQL 9.0 and 9.1 are a popular new feature - but they can also be used for other things than just replication! PostgreSQL 9.1 includes server changes to allow standalone tools to request and respond according to the replication protocol. From these, tools like pg_basebackup allow a number of new possibilities. And the infrastructure put in place in 9.1 opens opportunities for further enhancements - some already on the drawing board and some just wild ideas so far.

</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/147/</url><track>DBA, English</track><persons><person id="1">Magnus Hagander</person></persons></event></room><room name="Amsterdam 1"><event id="171"><start>11:50</start><duration>00:50</duration><room>Amsterdam 1</room><title>Accelerating Local Search with PostgreSQL 9.1</title><abstract>KNN-GiST indexes in PostgreSQL 9.1 are really cool - I actually try to find scenarios in projects to use them. Some of the queries they are designed to speedup are actually fairly common text search queries. Others are in the realm of geospatial comparisons or text-similarity searches. This presentation will demonstrate the power of KNN-GiST indexes on geospatial and text searching queries, but also their present limitations through some of my experimentations. I will also discuss some of the theory behind KNN (k-nearest neighbor) as well as some of the applications this feature can be applied too.</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/171/</url><track>Developer, English</track><persons><person id="6">Jonathan S. Katz</person></persons></event></room><room name="Amsterdam 2"><event id="142"><start>11:50</start><duration>00:50</duration><room>Amsterdam 2</room><title>Mission impossible? Can I replace my most important databases with PostgreSQL?</title><abstract>Databases are the most crtitical systems in corporate IT. This presentation is about using PostgreSQL as an Open-Source alternative to existing proprietary databases following the path of other Open-Source software that made its way into corporate IT over the years. This presentation reflects on 12+ years of experience in business usage of Open-Source and give some rules on how to make a migration and the subsequent Open-Source usage work. Also it will show some Return of Investment calculation using real life examples that were actually done over the years.</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/142/</url><track>General</track><persons><person id="46">Michael Meskes</person></persons></event></room><room name="Other"><event id="228"><start>12:40</start><duration>01:00</duration><room>Other</room><title>Lunch</title><abstract /><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/228/</url><track>Breaks</track><persons><person id="31">Undisclosed Speaker</person></persons></event></room><room name="Amsterdam 2"><event id="169"><start>13:40</start><duration>00:50</duration><room>Amsterdam 2</room><title>Find your slow queries, and fix them!</title><abstract>Where, oh where, is all that time going?  What in the world is that database thing *doing*?!  This talk will help you understand what's happening (and why) and  how to analyze poor query performance.  We'll also go over steps and strategies to take to improve them and get the performance (and scalability!) you need.</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/169/</url><track>Developer, English</track><persons><person id="84">Stephen Frost</person></persons></event></room><room name="Amsterdam 3"><event id="152"><start>13:40</start><duration>00:50</duration><room>Amsterdam 3</room><title>Managing Terabytes</title><abstract>Size can creep up on you. Some day you may wake up to a multi-terabyte Postgres system handling over 3000 tps staring you down. Learn the best ways to manage these systems as they grow, and find out what new features starting with 9.0 have made life easier for administrators and application developers working with big data.

This talk will lead you through solutions to problems Postgres faces when it gets big: backups, transaction wraparound, bloat, huge catalogs and upgrades. You need to monitor the right things, find the gems in DBA-friendly database functions and catalog tables, and know the right places to look to spot problems early. We’ll also go over monitoring best practices and open source tools to get the job done.

Working with multiple versions of Postgres back to version 8.2 will be included, and as well as tips on making the most out of new features in 9.1. War stories will be taken from real-world work with Emma, an email marketing company with a few large databases, and from a private company attempting to move from Oracle to Postgres.
</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/152/</url><track>DBA, English</track><persons><person id="65">Selena Deckelmann</person></persons></event></room><room name="Amsterdam 1"><event id="211"><start>13:40</start><duration>00:50</duration><room>Amsterdam 1</room><title>Migrer à PostgreSQL: comment s'y prendre?</title><abstract>Cette présentation a pour cible les décideurs qui ont naturellement déjà des bases de données en production dans des systèmes propriétaires et qui cherchent à migrer à PostgreSQL une ou plusieurs d'entre elles, ou qui cherchent à utiliser PostgreSQL pour un nouveau projet.

La difficulté est cependant double:
* d'une part, il va falloir utiliser un nouveau SGBD
* d'autre part, il va falloir très probablement comprendre l'Open Source et ce que cela implique

Ainsi, on cherche dans cette présentation à donner les clés d'une adoption réussie de PostgreSQL: ce qu'il faut faire et ce qu'il ne faut pas faire. La présentation se concentrera surtout sur les méthodes et beaucoup moins sur la technique, bien qu'on y présentera quelques outils forts utiles (ora2pg par exemple, mais aussi des outils de tests, de benchmarking, etc).

La présentation sera illustrée de cas réels, issus de l'expérience du speaker, cependant, les noms des comptes ne pourront être divulgués...
</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/211/</url><track>French</track><persons><person id="13">Jean-Paul Argudo</person></persons></event></room><room name="Other"><event id="229"><start>14:30</start><duration>00:30</duration><room>Other</room><title>Tea</title><abstract /><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/229/</url><track>Breaks</track><persons><person id="31">Undisclosed Speaker</person></persons></event></room><room name="Amsterdam 3"><event id="216"><start>15:00</start><duration>00:50</duration><room>Amsterdam 3</room><title>Funding The Future:  The Role of PostgreSQL in the Post Oracle Era</title><abstract>Enterprises and IT operations are undergoing a massive transformation fueled by the explosion of data in the organization and re-platforming to utility-based cloud computing.  New technologies in data management are emerging that will become increasingly important as users begin to prioritize finding the meaning in their data over how data is stored and managed.  This is forcing a fundamental shift in how IT spending must be allocated.  In order to fund the future, PostgreSQL along with other open source technologies are delivering the best price-performance alternative to enable this shift, and will play a central role in cloud and bare metal deployments.</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/216/</url><track>General</track><persons><person id="33">Ed Boyajian</person></persons></event><event id="145"><start>15:50</start><duration>00:40</duration><room>Amsterdam 3</room><title>Closing</title><abstract>The closing session for the conference; prizes, observations, thanks and announcements.</abstract><url>https://www.postgresql.eu/events/pgconfeu2011/schedule/session/145/</url><track>General</track><persons><person id="2">Dave Page</person></persons></event></room></day></schedule>