On Fri, Apr 8, 2022 at 7:57 AM Nikolay Samokhvalov <samokhva...@gmail.com> wrote:
> On Thu, Apr 7, 2022 at 8:10 AM Jan Wieck <j...@wi3ck.info> wrote: > >> So **IF** Active Record is using that feature, then it can dump any >> amount of garbage into your PostgreSQL database and PostgreSQL will >> happily accept it with zero integrity checking. >> > > It's DISABLE TRIGGER ALL > https://github.com/rails/rails/blob/831031a8cec5bfe59ef653ae2857d4fe64c5698d/activerecord/lib/active_record/connection_adapters/postgresql/referential_integrity.rb#L12 > A side-note on this, which of course won't help the OP at this point, but if the general best practice of not running the application with a highly privileged account is followed, the problem won't occur (it will just fail early before breaking things). DISABLE TRIGGER ALL requires either ownership of the table or superuser permissions, none of which it's recommended that the application run with. Doesn't help once the problem has occurred of course, but can help avoid it happening in the future. -- Magnus Hagander Me: https://www.hagander.net/ <http://www.hagander.net/> Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
