Live data from Hacker News

Jepsen: Amazon RDS for PostgreSQL 17.4

jepsen.io

11–20 of 153 posts

Re: Jepsen: Amazon RDS for PostgreSQL 17.4

#11
post #5

This is in such a thick academic style that it is difficult to follow what the problem actually might be and how it would impact someone. This style of writing serves mostly to remind me that I am not a part of the world that writes like this, which makes me a little sad.

In the beginning, when you read papers like this, it can be hard work. You can either give up or put some effort in to try to understand it. Maybe look at some of the other Jepsen reports, some may be easier. Or perhaps an introductory CS textbook. With practice and patience it will become easier to read and eventually write like this.

You may not be part of that world now, but you can be some day.

EDIT: forgot to say, i had to read 6 or 7 books on Bayesian statistics before i understood the most basic concepts. A few years later i wrote a compiler for a statistical programming language.

Re: Jepsen: Amazon RDS for PostgreSQL 17.4

#12
post #2

I thought this kind of bullshit was only supposed to happen in MongoDB!

Do people still use MongoDB in production? I was quite surprised to read that Stripe uses MongoDB in the early days and still today and I can't imagine the sheer nightmares they must have faced using it for all these years.

mongodb is a public company with a market cap of 14.2 billion dollars. so yes, people still use it in production

Re: Jepsen: Amazon RDS for PostgreSQL 17.4

#13
post #2

I thought this kind of bullshit was only supposed to happen in MongoDB!

Do people still use MongoDB in production? I was quite surprised to read that Stripe uses MongoDB in the early days and still today and I can't imagine the sheer nightmares they must have faced using it for all these years.

MongoDB has come a long way. They acquired a world-class storage engine (WiredTiger) and then they hired some world-class distsys people (e.g. Murat Demirbas). They might still be hamstrung by early design and API choices but from what I can tell (never used it in anger) the implementation is pretty solid.

Re: Jepsen: Amazon RDS for PostgreSQL 17.4

#14
post #5

This is in such a thick academic style that it is difficult to follow what the problem actually might be and how it would impact someone. This style of writing serves mostly to remind me that I am not a part of the world that writes like this, which makes me a little sad.

In the beginning, when you read papers like this, it can be hard work. You can either give up or put some effort in to try to understand it. Maybe look at some of the other Jepsen reports, some may be easier. Or perhaps an introductory CS textbook. With practice and patience it will become easier to read and eventually write like this. You may not be part of that world now, but you can be some day. EDIT: forgot to sa…

[deleted]

Re: Jepsen: Amazon RDS for PostgreSQL 17.4

#15
It's not entirely clear but this isn't an issue in multi instance upstream Postgres clusters?

Am I correct in understanding either AWS is doing something with the cluster configuration or has added some patches that introduce this behavior?

Re: Jepsen: Amazon RDS for PostgreSQL 17.4

#16
post #5

This is in such a thick academic style that it is difficult to follow what the problem actually might be and how it would impact someone. This style of writing serves mostly to remind me that I am not a part of the world that writes like this, which makes me a little sad.

In the beginning, when you read papers like this, it can be hard work. You can either give up or put some effort in to try to understand it. Maybe look at some of the other Jepsen reports, some may be easier. Or perhaps an introductory CS textbook. With practice and patience it will become easier to read and eventually write like this. You may not be part of that world now, but you can be some day. EDIT: forgot to sa…

I’ll look to do so, and appreciate your pointers. Thank you for being kind!

Re: Jepsen: Amazon RDS for PostgreSQL 17.4

#17
post #2

I thought this kind of bullshit was only supposed to happen in MongoDB!

I think zookeeper is still the only distributed system that got through jepsen without dataloss bugs, though at high cost: https://aphyr.com/posts/291-jepsen-zookeeper

Didn't FoundationDB get a clean bill of health?

Re: Jepsen: Amazon RDS for PostgreSQL 17.4

#18
post #6

Earlier quoted context omitted.

Postgres is not a distributed system in this configuration usually though is it?

The result is for “Amazon RDS for PostgreSQL multi-AZ clusters” which are certainly a distributed system. I’m not well versed in RDS but I believe that clustered is the only way to use it.

No, you can have single instances

Re: Jepsen: Amazon RDS for PostgreSQL 17.4

#19
post #5

This is in such a thick academic style that it is difficult to follow what the problem actually might be and how it would impact someone. This style of writing serves mostly to remind me that I am not a part of the world that writes like this, which makes me a little sad.

[flagged]

Hello ChatGPT.

Re: Jepsen: Amazon RDS for PostgreSQL 17.4

#20
post #5

This is in such a thick academic style that it is difficult to follow what the problem actually might be and how it would impact someone. This style of writing serves mostly to remind me that I am not a part of the world that writes like this, which makes me a little sad.

[flagged]

Great summary, could you share the prompt you used?
Post reply on HN