Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: I built this Postgres logger

rocketgraph.io

Post reply on HN
Print view View original

31–40 of 49 posts

Re: Show HN: I built this Postgres logger

#31

Post by _flux »

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? ;)

Well, I guess you could use https://www.postgresql.org/docs/16/sql-createeventtrigger.ht... to trigger on sql_drop

Maybe it could send a Slack message which you (some someone else) would need to react with (I think this site malforms that white checkmark unicode character though..) before it continues, or times out after a while with an error!

Re: Show HN: I built this Postgres logger

#32

Post by kvaranasi_ »

_flux wrote: post #31
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? ;)

Well, I guess you could use https://www.postgresql.org/docs/16/sql-createeventtrigger.ht... to trigger on sql_drop Maybe it could send a Slack message which you (some someone else) would need to react with (I think this site malforms that white checkmark unicode character though..) before it continues, or times out after a while with an error!

This is great. I plan on providing Postgres trigger templates that developers can easily load on Rocketgraph.

Re: Show HN: I built this Postgres logger

#33

Post by kvaranasi_ »

_flux wrote: post #31
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? ;)

Well, I guess you could use https://www.postgresql.org/docs/16/sql-createeventtrigger.ht... to trigger on sql_drop Maybe it could send a Slack message which you (some someone else) would need to react with (I think this site malforms that white checkmark unicode character though..) before it continues, or times out after a while with an error!

Postgres is one of the most amazing inventions that exit truly.

Re: Show HN: I built this Postgres logger

#34

Post by kvaranasi_ »

dewey wrote: post #30
kvaranasi_ wrote: post #28

Earlier quoted context omitted.

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.

Ok, yes this makes sense.

Re: Show HN: I built this Postgres logger

#35

Post by koliber »

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? ;)

If you want to find the developer who will drop your table by accident, ask your devs to raise their hands if they ever dropped a table by accident. Those that don’t raise their hand are the ones you watch carefully.

Re: Show HN: I built this Postgres logger

#38

Post by lazyant »

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? ;)

Like others have said, this is a control problem in prod (not using migrations in code and renaming instead of dropping). Anyways, as an fun exercise to get exactly what's asked, I wonder if this could be used https://tembo.io/blog/introducing-pg-later/ together with a trigger to trap the DROP, alert on Slack and run later if not aborted.

Re: Show HN: I built this Postgres logger

#39

Post by hobs »

kvaranasi_ wrote: post #29
dewey wrote: post #20

Earlier quoted context omitted.

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.

People using triggers for this just don't understand proper security - its a little harder but having your deployment process have the ability to drop tables and having your general user having read only query access (or insert powers on your own schema which nobody else can read) is stuff DBAs figured out in 90s and we keep forgetting.

Re: Show HN: I built this Postgres logger

#40

Post by jrockway »

lazyant wrote: post #38
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? ;)

Like others have said, this is a control problem in prod (not using migrations in code and renaming instead of dropping). Anyways, as an fun exercise to get exactly what's asked, I wonder if this could be used https://tembo.io/blog/introducing-pg-later/ together with a trigger to trap the DROP, alert on Slack and run later if not aborted.

Migrations are not your safety net, backups are. Migrations, like all code, are full of bugs.
Post reply on HN