March 20 ChatGPT outage: Here’s what happened

Re:March 20 ChatGPT outage: Here’s what happened by anarazel on Friday March 24, 2023 @05:51PM (#35296130)

I agree that redis can handle some query volumes and client counts that postgres can't.

But FWIW I can easily saturate a 10GBit ethernet link with primary key-lookup read-only queries, without the results being ridiculously wide or anything.

Because it didn't need any setup, I just used:

  SELECT * FROM pg_class WHERE oid = 'pg_class'::regclass;

I don't immediately have access to a faster network, connecting via tcp to localhost, and using some moderate pipelining (common in the redis world afaik), I get up to 19GB/s on my workstation.

[ Parent | on HN ]

Re:March 20 ChatGPT outage: Here’s what happened by e12e on Saturday March 25, 2023 @10:21AM (#35302896)

> SELECT * FROM pg_class WHERE oid = 'pg_class'::regclass;

This selects every column (*) from every table (ObjectID is of type regclass)?

[ Parent | on HN ]

Re:March 20 ChatGPT outage: Here’s what happened by anarazel on Saturday March 25, 2023 @11:15AM (#35303467)

Sorry, I should have used something more standard - but it was what I had ready...

It just selects every column from a single table, pg_class. Which is where postgres stores information about relations that exist in the current database.

[ Parent | on HN ]