Postgres DDL Transaction Control Sucks
I come from an Oracle background so I am used to a few rules when it comes to DDL.
- Don’t perform DDL in a production database until you’ve done it in a test instance.
- DDL is permanent unless you have flashback or want to restore.
That might sound like a limitation but I don’t see it that way. You *SHOULD* test everything before running it in production. And flashback is much more powerful than simply having commit and rollback for DDL.
Today I was trying out some changes to my code (that runs outside of the database) and needed to do a quick test that would delete some rows.
I did a quick
create table xyz as select * from abc;
I ran a quick test on some prep data:
The func() hit an error and rolled back.
I fixed the error and reran the function. It worked so I ran my external program. It deleted the data and committed the changes.
I then tried to put the records back in the first table from the second table.
Oops. Second table no longer exists. The rollback from the stupid func() also rolled back my create table.
In Oracle, I would have several options to recover my data. For one, the create would automatically have committed. But in Oracle, I wouldn’t have needed the table, I would just flashback and restore my data.
Fortunately, this was just a test bed database and the data isn’t really critical. Had it been critical, I would have taken steps to be sure it was backed up. So, no big deal really.
And, yeah, I know Ingres and SQL Server (and probably Sybase) work like Postgres. Doesn’t make it a good thing.
My next whine will be transaction control is stored procedures. But at least that will be coming from EnterpriseDB at some point.
You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.