Typically, we do implementations ourselves. That said, if it is a huge deployment or production, we might need help from a consultant or someone from the team who is an expert in the database. All in all, it's not that hard. It's not days of consultancy. It's a matter of hours or a single day.

It took us five minutes to deploy the solution.

My partner and I read the books and then just did it. I am on the development side. They get the new products in, and I and this other person evaluate them and learn them. We probably have three people in operations who are handling Postgres on the production side.

Both times I have been involved in an initial Postgres implementation, we have handled it in-house. It isn’t too hard to implement but you do need some base tech skills including Unix. I would not recommend trying to implement it on a Windows server.

I implemented in-house.

We handled the implementation process ourselves. We didn't need the assistance of any consultants or integrators. It was pretty straightforward, and therefore we didn't need the extra help.

I did the implementation of PostgreSQL. We have a team of three manages and fifteen engineers that do the maintenance of the solution.

I deploy it myself.

I implemented this solution by myself.

I have never tried implementing it with a vendor. I was always part of an in-house team and we never faced any issues that would make us need to use a vendor team.

We did not implement the database software. What we implement is the design of the database and its interfaces toward third party systems and in-house applications. In the world of databases the person or team dealing with how data must be stored and accessed must possess complete knowledge about the processes being involved. It is not uncommon that web developer ask for accesses, which they are not entitled to and it is important to be able to offer an alternative. The most typical is a test database instance that web developers can use as playground.

In-house. That said, it's very easy to spin up an instance using Amazon Web Service's RDS product.

All in-house. My advice is to try to keep things simple, it is harder to learn from complex setups where the setup itself is a problem too, work on complexity once you feel comfortable with the expertise you have gained.

I was able to handle the implementation myself. I did not need the help of a consultant or integrator. 

I have deployed them to Oracle recently. I've also deployed it in the cloud. There's really nothing special about the cloud, as long as I use the PostgreSQL machine I can deploy it anywhere. I want to deploy it on the Google cloud platform, and Amazon Web Services as these are well known virtual machines.

We have special expertise in providing various database solutions to our global customers and we implement customer solutions with help of our in-house DBAs.

It's very easy, and you only need to familiarize yourself with its file structure. Sometimes you need to write your own plugin, so sometimes it is better to have it implemented by a vendor.

I have always implemented in-house and sometimes I've looked around for vendor sources just to understand with what they come more.

Definitiely they help reduce the learning curve and there are promises for richer scalability options.

We did the implementation ourselves but it is always recommended to use an expert.

I do it myself. I have been doing it for a long time. For its deployment and maintenance, one DevOps person is sufficient.

In-house because we a are a technology company. I always advise to look for a consulting company, sometimes the default configuration is not enough and the tool can become a bottleneck if it isn't properly configured.

In-house. There is a lot of good information on the web and stackoverflow.

Did the implementation in house. Not for everyone, but then, if you are installing and utilizing a standalone SQL Server you have to be a pretty computer savvy person.

I recommend PostgreSQL without doubt because my experience of almost 20 years with this product has shown me that PostgreSQL has certain features that make it highly reliable: high scalability, robustness, available for multiple platforms, extensible with little effort and without additional cost, designed for high volume environments, easy to manage and extensive online support.

We were helped in the implementation by the vendor. You should always let an expert do the implementation as if it is configured incorrectly it can have a big impact on performance.

I did it in-house. The only advice is to read and learn from PostgreSQL documentation and related books or blogs. PostgreSQL is easy to start, but is a complex RDBMS with many screws to adjust.

We had help from a company from Norway, one from South Africa, and one other from Dubai.

Our initial implementation was done in-house. As long as you follow the step-by-step directions, everything worked great. We also have a managed services company that helps manage the PROD/Staging configuration as well.

Strictly in-house, and I would say anyone attempting implementation should hire the expertise to get the system correct.

We deployed it in-house.

Postgres has great documentation and various open source tools available for maintenance. However, it is recommended to work with Postgres consulting services companies to expedite design and implementation.

We did it in-house.

Implementation and installation was carried out in house.

I did the implementation of PostgreSQL myself, and did not need a vendor or technical team to help me.

Implementation was completely in-house. On our case, it was much better to train the team to use a new RDBMS than to use external consultant; after all, our team is a development team.

I did it myself with help from the internet. For beginners, I would advise you to read the documentation that is available. Also, you should read some books such as "PostgreSQL: Up and Running, 2nd Edition". "PostgreSQL Administration Essentials", "PostgreSQL 9 Administration Cookbook, 2nd Edition". Alternatively, you could look into getting professional help if you are in hurry.

We did the implementation through an in-house IT engineer.

We have a team of approximately five engineers that manage the solution.

While the initial setup is easily done by any member of Ops team, it's important to have a dedicated DBA resource to take care of it. PostgreSQL has superb documentation, it is probably the best documented IT project. We have an in-house team and almost never have to use external consultants. PostgreSQL is very much different from the most popular RDBMS, so it's best to seek a PostgreSQL-focused professional for the in-house team.

It's very easy, and you only need to familiarize yourself with its file structure. Sometimes you need to write your own plugin, so sometimes it is better to have it implemented by a vendor.

We did it in-house.

We implemented it through a vendor as using this kind of service is easy and fast to get started. You don't need experts, and you can keep concentrating on your core business. However, when you grow the costs grow, and as in our case, it might be hard to leave the vendor.

We did an in-house implementation for PostgreSQL. The documentation made it easy to do and was very simple to follow.

I have always implemented it in-house, and as all solutions for everything on vast areas, is highly recommended read guides on how to install it.

We implemented it in-house.

I did the implementation of this solution myself and it was more complex than MySQL.

We did it all in-house. You should read all the official documentation as all the answers are there.

In a vendor team, we develop products for different segments stores. In the implementation, keep in mind the configurations and platforms that are available, it certainly will save time and avoid potential problems.

We did it in-house.

We used a vendor team.

In house. You do need someone that knows PostgreSQL or that can spend time learning about the product.

We did it in-house.

We did it in-house.

We implemented it with our in-house team.

It's my understanding that the solution was handed in-hours. We didn't use an integrator, reseller, or a consultant for the deployment.

We did it in-house.

I implemented it myself and don’t have any particular advice about it. Today I would consider implementing it via Docker.

I implemented in-house. PostgreSQL databases needs some maintenance but that can be easily automated by a skilled administrator.

We use an in-house team.

It was done in-house.

I have used GoDaddy hosting, and Amazon EC2 with PostgreSQL. I don't have any problems.

We implemented it in-house.

It's very easy, and you only need to familiarize yourself with its file structure. Sometimes you need to write your own plugin, so sometimes it is better to have it implemented by a vendor.

We implemented it in-house.

The implementation was done with our in-house team. My advice is to get training.

We did it in-house, but only to test different databases.