Fork me on GitHub
#sql
<
2020-01-28
>
dharrigan07:01:57

@kulminaator have your instances had their autovacuum settings readjusted from the defaults?

kulminaator08:01:39

Yes we have had adjustments on those too, depending on apps

kulminaator08:01:07

On some we probably will go for additional automated vacuums from apps too.

dharrigan08:01:30

Yeah, it's probably the most important thing to tune for PostgreSQL

orestis09:01:44

So it’s not 100% worry-free, right? In the sense that I pay someone else to worry about tuning and tweaking and settings.

orestis09:01:57

I’m not too opposed to have to learn a few things, and it seems AWS limits the parameters you can tweak which is probably a good idea. They also have “Performance Insights” now which might help for some use cases. But it seems like I’d need to have some support from a DBA every once in a while.

dharrigan09:01:22

imho, if one is running any system, be it mysql, mariadb, postgresql, mongodb etc.., then having at least some understanding of how it works (where it works well, and where it does not) is still important, even with SaaS offerings

dharrigan09:01:50

Everything needs tweaking to suit particular use cases 🙂

kulminaator11:01:46

I dont think any storage is worry free, but it is easier than just postgres clusters on top of ubuntu and chef infra. That requires way more.

orestis12:01:43

Oh yeah I’m just spoiled because we use Mongo Atlas and Mongo ObjectRocket and they take care of mostly everything. Apart from storage/instance size/IO there’s not much else to tweak

kulminaator11:01:18

My team is pretty solid on db stuff, so i'm not too worried.

kulminaator11:01:47

If you want to do fast rollover upgrades then dont forget to enable logical replication so you can stream data to a newer instances via their db migration tool.

orestis12:01:00

Thanks for the tip, I’ll look into that

kulminaator11:01:31

Talking of fancy stuff, anyone using cockroachdb with java or clojure ? Happy / not happy ?

dharrigan12:01:44

Tis a horrible name

dharrigan12:01:56

It's just another hard sell to the boss - cockroach db?

😄 4
kszabo13:01:04

I mean, it’s persistently alive 🙂

👍 4
dharrigan12:01:04

I mean, pick a nicer sounding name

dharrigan12:01:24

DuracellBunnyDB

🔋 4
🐰 4
bananadance 4
dharrigan12:01:30

keeps on going and going and going....

kulminaator16:01:09

Name is horrible but design seems good

exit216:01:28

Anyone have advice on updating (batch) multiple rows via psql?

exit216:01:25

[UPDATE import.spaces (id, import_timestamp, record, table_name) VALUES (?, ?, ?, ?), (?, ?, ?, ?), (?, ?, ?, ?) 89dc51b1-9763-4ffc-99e3-a435d34f58aa #inst "2020-01-28T16:06:57.000000000-00:00" {"foo":"onelkajsdlfkjalskdjflkajsdf"} spaces 05566595-1703-4eb3-acb7-5ef56d8fcd95 #inst "2020-01-28T16:06:57.000000000-00:00" {"foo":"twokdsksksksk"} spaces 1832fe59-a0c9-42b8-871d-143c344c9993 #inst "2020-01-28T16:06:57.000000000-00:00" {"foo":"thsksksksksksk"} spaces]

exit216:01:34

I tried something like this but it doesn’t seem to work

hiredman17:01:19

that isn't correct sql syntax for update, that is insert syntax with the word update in front of it

exit217:01:20

Figured it out, thanks @hiredman