Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Server crash occur and corrupt the database when deleting data from a table when table have multiple triggers, functions defined. #153

Closed
shahidullah79 opened this issue Mar 26, 2024 · 1 comment · Fixed by #165

Comments

@shahidullah79
Copy link

Create a database and populate it with the attached sql file which has different tables, functions, triggers etc defined.
Now try to delete data from emp table. e.g.
delete from emp where mgr=7698;

A server crash will occur.
delete from emp where mgr=7698;
INFO: Deleting employee 7499
INFO: ..Old salary: 1600.00
INFO: Deleting employee 7521
INFO: ..Old salary: 1250.00
INFO: Deleting employee 7654
INFO: ..Old salary: 1250.00
INFO: Deleting employee 7844
INFO: ..Old salary: 1500.00
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting reset: Failed.
The connection to the server was lost. Attempting reset: Failed.

It will also corrupt the database and no other functionality will work on this database.

Here is the sql file.
pg_tde-sample.log

@github-project-automation github-project-automation bot moved this to 📋 Backlog in PG-TDE Mar 26, 2024
@shahidullah79
Copy link
Author

Screenshot 2024-03-26 at 1 37 55 PM

Server Log file
postgresql-Tue.log

@codeforall codeforall linked a pull request Apr 2, 2024 that will close this issue
@github-project-automation github-project-automation bot moved this from 📋 Backlog to ✅ Done in PG-TDE Apr 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant