> [2] https://www.postgresql.org/message-id/flat/20140317185255.20724.49675% > 40wrigleys.postgresql.org > > -- > David Rowley http://www.2ndQuadrant.com/ > PostgreSQL Development, 24x7 Support, Training & Services >
> https://www.postgresql.org/message-id/flat/20140317185255.20724.49675% 40wrigleys.postgresql.org *Wow, so BUG #9606 has been known since 2014-03-17, but no one has bothered to fix it?As I've said before, instead of fixing the problem, the resolution seems to be to "make it go away". I've seen that logic echoed in other situations outside of the IT environment.The fact remains, my code works (or worked) because I was only interested in finding tables that were newly created without a primary key. While I acknowledge that bug, the situation where the primary key is dropped is extremely rare and would only happen in the rare case where the primary key needed to be altered or replaced by another key, in which case the problem is moot. Since PostgreSQL is a relational database,I cannot think of a situation where a DBA would allow the primary key to just be dropped/removed altogether.I was hoping that at least one other person would see my point of view, but by the harsh replies I've been getting, I feel more like a whistle blower that insiders think I also should be made to "go away". Well, you are right. This old Viet Vet shall now end this conversation and his career.I just need a way to do so quietly and painlessly.The truth is absolute and cannot be changed.Perception is not the truth.Flerp!* -- *Melvin Davidson* *Maj. Database & Exploration Specialist* *Universe Exploration Command – UXC* Employment by invitation only!
