or "How We Can Overtake Every Other Database" According to Jeff Barr, the Chief Evangelist for Amazon Web Services, "Over the past few years, PostgreSQL has become the preferred open source relational database for many enterprise developers and start-ups, powering leading geospatial and mobile applications." Through the hard work from the major contributors of our community and certain market events in the data world, it is indeed true that many new projects, both open and closed source, are defaulting to PostgreSQL as their data storage choice. So what is preventing PostgreSQL from becoming the default database for everyone? We will explore the PostgreSQL Advocacy efforts to date which has brought us to this crossroads, and how through a combination of our ongoing product development and a bit of community marketing prowess, we as a community can make "PostgreSQL" as household technology name over the next five years. According to Jeff Barr, the Chief Evangelist for Amazon Web Services, "Over the past few years, PostgreSQL has become the preferred open source relational database for many enterprise developers and start-ups, powering leading geospatial and mobile applications." Through the hard work from the major contributors of our community and certain market events in the data world, it is indeed true that many new projects, both open and closed source, are defaulting to PostgreSQL as their data storage choice. We know that PostgreSQL is an amazing product, and those who know the realm of technology agree. So what is preventing PostgreSQL from becoming the default database for everyone? In order to solve this problem, we will first explore the PostgreSQL advocacy efforts to date. We will take a look at what features have helped propel PostgreSQL into its "newfound" limelight and what the community has done to create a "buzz" around PostgreSQL to capture more users. We will then arrive at the present day crossroads, and look at different strategies to more effectively market ourselves as a product and a community, including how to: Actively make more people aware of PostgreSQL and what it can offer Make it easier for new people to adopt PostgreSQL Determine the pain points of our current users and figure out how to fix them Measure the success of our advocacy efforts Through these combined efforts on the development and advocacy fronts, we as a community can make PostgreSQL as household technology name over the next five years.