Show HN: I built this Postgres logger • Hacker News Board

Re: Show HN: I built this Postgres logger

#21

Post by nswanberg » Thu, Aug 24, 2023, 1:43 PM UTC

rsyring wrote: post #4

> In the future we can connect these logs to slack so you can get slack alerts when a developer accidentally DROPs a table. What can you do about getting me a slack notice BEFORE a developer accidentally drops a table? ;)

Triboulet: "A noble has threatened to hang me!"

The Monarch: "Don't worry! If he hangs you I'll have him beheaded fifteen minutes later."

Triboulet: "Well, would it be possible to behead him 15 minutes before?

Re: Show HN: I built this Postgres logger

#22

Post by kvaranasi_ » Thu, Aug 24, 2023, 1:50 PM UTC

nswanberg wrote: post #21

rsyring wrote: post #4

> In the future we can connect these logs to slack so you can get slack alerts when a developer accidentally DROPs a table. What can you do about getting me a slack notice BEFORE a developer accidentally drops a table? ;)

Triboulet: "A noble has threatened to hang me!" The Monarch: "Don't worry! If he hangs you I'll have him beheaded fifteen minutes later." Triboulet: "Well, would it be possible to behead him 15 minutes before?

Hahahah. I literally Googled who Triboulet was.

Re: Show HN: I built this Postgres logger

#23

Post by e12e » Thu, Aug 24, 2023, 2:07 PM UTC

This looks great:)

> Use https://rocketgraph.io/ And setup a project.

What will the price and terms be?

Re: Show HN: I built this Postgres logger

#24

Post by codegeek » Thu, Aug 24, 2023, 2:08 PM UTC

rsyring wrote: post #4

> In the future we can connect these logs to slack so you can get slack alerts when a developer accidentally DROPs a table. What can you do about getting me a slack notice BEFORE a developer accidentally drops a table? ;)

"BEFORE a developer accidentally drops a table?"

Ideally, you don't want developer(s) to have access to destruct data especially things like DROP. Now, a lot of small businesses may not have the resource to have separate DBAs etc but the rule still applies.

This is more a control problem than a code problem. Having said that, you could write triggers to stop DELETE or DROPs from happening if you cannot control the access.

Re: Show HN: I built this Postgres logger

#25

Post by kvaranasi_ » Thu, Aug 24, 2023, 2:12 PM UTC

e12e wrote: post #23

This looks great:) > Use https://rocketgraph.io/ And setup a project. What will the price and terms be?

1 week free trail. And for HN users I can give more time for the free trail. It'll be $50/mo. But it is worth a lot more.

But hey, you can sign up and create a project without your credit card. Once free trail ends, you can pay with stripe. Let me know how you like it.

Re: Show HN: I built this Postgres logger

#26

Post by kvaranasi_ » Thu, Aug 24, 2023, 2:13 PM UTC

codegeek wrote: post #24

rsyring wrote: post #4

> In the future we can connect these logs to slack so you can get slack alerts when a developer accidentally DROPs a table. What can you do about getting me a slack notice BEFORE a developer accidentally drops a table? ;)

"BEFORE a developer accidentally drops a table?" Ideally, you don't want developer(s) to have access to destruct data especially things like DROP. Now, a lot of small businesses may not have the resource to have separate DBAs etc but the rule still applies. This is more a control problem than a code problem. Having said that, you could write triggers to stop DELETE or DROPs from happening if you cannot control the ac…

Interesting idea to use Triggers.

Re: Show HN: I built this Postgres logger

#27

Post by dom_hutton » Thu, Aug 24, 2023, 2:22 PM UTC

rsyring wrote: post #4

> In the future we can connect these logs to slack so you can get slack alerts when a developer accidentally DROPs a table. What can you do about getting me a slack notice BEFORE a developer accidentally drops a table? ;)

Modify your schema through migrations that go through code review :p

Re: Show HN: I built this Postgres logger

#28

Post by kvaranasi_ » Thu, Aug 24, 2023, 2:28 PM UTC

dewey wrote: post #20

kvaranasi_ wrote: post #7

Earlier quoted context omitted.

Hey wait, you have a point though. We can put our custom locks onto tables that doesn't let anyone delete a particular table. Let me think over it. Saving this comment for later. Thanks for the idea man.

Uhm, why would you not use PG permissions for that? That's what they are for.

I am assuming that the developer has necessary permissions. If he/she accidentally deletes the table, then that's a problem.

Re: Show HN: I built this Postgres logger

#29

Post by kvaranasi_ » Thu, Aug 24, 2023, 2:30 PM UTC

dewey wrote: post #20

kvaranasi_ wrote: post #7

Earlier quoted context omitted.

Hey wait, you have a point though. We can put our custom locks onto tables that doesn't let anyone delete a particular table. Let me think over it. Saving this comment for later. Thanks for the idea man.

Uhm, why would you not use PG permissions for that? That's what they are for.

Of course I could be wrong. Please share with me your thoughts.

Re: Show HN: I built this Postgres logger

#30

Post by dewey » Thu, Aug 24, 2023, 2:33 PM UTC

kvaranasi_ wrote: post #28

dewey wrote: post #20

Earlier quoted context omitted.

Uhm, why would you not use PG permissions for that? That's what they are for.

I am assuming that the developer has necessary permissions. If he/she accidentally deletes the table, then that's a problem.

That means that the process is wrong. it sounds like they are doing day to day work with credentials that can drop tables, which is dangerous and should probably be done through code-reviewed migration tooling.