Bruce Momjian

VP, Postgres Evangelist, EDB

Bruce Momjian is a co-founder of the PostgreSQL Global Development Group, and has worked on PostgreSQL since 1996 as a committer and community leader. He is a frequent speaker and Postgres evangelist and travels worldwide appearing at conferences to help educate the community on the business value of Postgres advances and new technology enhancements. He is the author of PostgreSQL: Introduction and Concepts, published by Addison-Wesley. 

 

 

Read Blogs

Storing the Original Time Zone

In a previous blog entry I suggested storing the original time zone offset in a separate column if clients need to know the stored time in the original time zone. There is some more complexity to this issue that I would like to cover. First, when I suggested using select extract(timezone from current_timestamp), I assumed the user was also storing the current_timestamp value in the database. If...
EDB Labs

Materialized Views and Foreign Data Wrappers

You might know that Postgres supports materialized views and foreign data wrappers (fdw). Briefly, materialized views allow for queries to be materialized and refreshed on demand. Foreign data wrappers allow data to be pulled from foreign data sources, like Nosql stores and other Postgres servers. What you might not have considered is that materialized views and foreign data wrappers can be used...

Session State Failover

On the server side, high availability means having the ability to quickly failover to standby hardware, hopefully with no data loss. Failover behavior on the client side is more nuanced. For example, when failover happens, what happens to connected clients? If no connection pooler is being used, clients connected to the failed machine will need to reconnect to the new server to continue their...
EDB Labs

Playing with IPv6

Now that everyone is using IPv6 it might be time to start playing with it. Postgres has had full IPv6 support for years, so Postgres is a good place to start, particularly with IPv6-aware data types.

Odd Month Arithmetic

You might be aware of the interval data type, which allows mathematical operations on date, time, and timestamp values. This can lead to odd behavior, but this email posting showed me a new oddity when dealing with months containing a different number of days. First, let's summarize how many days are in the first five months of 2017: 2017-01 31 2017-02 28 2017-03 31 2017-04 30 2017-05 31 Let's add...

Use with Time Zone

If you often use the timestamp data type, you might not be making full use of it. In these queries: CREATE TABLE tztest (x TIMESTAMP); INSERT INTO tztest VALUES (CURRENT_TIMESTAMP); SELECT * FROM tztest; x ---------------------------- 2016-10-25 18:49:20.220891 SHOW timezone; TimeZone ------------ US/Eastern SET timezone = 'Asia/Tokyo'; SELECT * FROM tztest; x ---------------------------- 2016-10...

PL/Java Adoption

PL/Java has been around since 2005, but it has regularly struggled to gain users. Unfortunately, a lot of these problems are specific to the Java language and hamper its adoption. First, there are a limited number of people who know both Java and the Postgres backend code. Fortunately Chapman Flack has recently resumed PL/Java development. Second, there is the deployment complexity of binding PL...
EDB Labs

When to Use Server-Side Logic

The use of server-side logic, particularly stored procedures, has been a highly contentious topic among database professionals for decades.
Business Transformation

Which NoSQL Database for New Project?

Oh, how I love the title of this 2014 Slashdot request, "Which NoSQL Database For New Project?" The user already knows the type of clients (iPhones and Android phones)

You Don't Need Every Feature of Your Previous Database

In a March blog post I talked about the mismatch between what people expect from Postgres in terms of hints, and what exists. In this blog post I would like to cover the more general case of when people should expect feature parity with their previous database, and when such expectations are unreasonable. First, imagine if every database had the features of every other database — that would be...