rhaas

4 ms·

1.
by rhaas 6mo ago
The infrastructure is intentionally pluggable to facilitate different viewpoints on questions like this. I hope we see various add-on modules pop up that fetch advice strings from various possible sources.
2.
by rhaas 3y ago
I agree that for many use cases, standbys and in particular time-delayed standbys are a better option than backups. That said, having off-line backups in tamper-proof storage is a good call, too.
3.
by rhaas 5y ago
I have been a PostgreSQL hacker since 2008 and a PostgreSQL user for many years before that. The first mention of my name in the PostgreSQL commit log is in 2003, and the first version of PostgreSQL that I used was 7.something; it couldn&#x
4.
by rhaas 5y ago
The only name I can find on the "Fundación PostgreSQL" web site is yours. The PostgreSQL core team membership is listed on postgresql.org and includes 7 members from 4 different companies. I agree that perhaps the PostgreSQL core
5.
by rhaas 9y ago
I wrote a previous post on why MVCC is interesting, and how it relates to the topic at hand. It's the first link in the article. I don't think that it's accurate to say to say that there are only two ways of doing this. The
6.
by rhaas 9y ago
Uh, indexes in postgres point to the tuple, not the page. Except for BRIN.
7.
by rhaas 9y ago
The first release of PostgreSQL that had synchronous replication was released in September 2011. https://www.postgresql.org/docs/9.1/static/release-9-1.html
8.
by rhaas 9y ago
The work that has been done on transition tables is intended to enable future work on automatically updated materialized views; the idea is that the system will automatically derive a query to update the view based on the deltas between the
9.
by rhaas 9y ago
I agree with you that stored procedures are superior to client-side logic, because it means that you can have multiple routes of access to the database and all of them enforce the same business logic. But what exactly do you mean by "
10.
by rhaas 9y ago
Replication across major versions, for example to upgrade without downtime. Partial replication, to distribute shared data across a series of clusters, or for analytics and reporting as you mention. Replicating the data without replicatin
11.
by rhaas 9y ago
I hope that it will have that effect. We need a few other features first: partitionwise join, partitionwise aggregate, asynchronous query, and ideally hash partitioning.
12.
by rhaas 14y ago
Yep, see http://rhaas.blogspot.com/2010/11/mysql-vs-postgresql-part-1...
13.
Query Planner Enhancements in PostgreSQL 9.1(rhaas.blogspot.com)
9 points by rhaas 16y ago|0 comments
14.
Robert Haas: MySQL vs. PostgreSQL, Part 2: VACUUM vs. Purge(rhaas.blogspot.com)
41 points by rhaas 16y ago|2 comments