Ingress
An early relational database system developed by Stonebraker at UC Berkeley in the 1970s, which became Postgres and was later commercialized by Ingress Corporation.
As defined in Turing Award Winner: Disagreeing with Google, Postgres, Future Problems | Mike Stonebraker
Where it comes up · 1
Most important claims · 9 of 9Search all claims for “Ingress” →
- A customer of Ingress needed to calculate interest on financial bonds using a non-standard date arithmetic where March 15 minus February 15 equals 30 days (because months have fixed 30-day lengths for bond calculations), which Ingress couldn't support because date subtraction was hardcoded.Turing Award Winner: Disagreeing with Google, Postgres, Future Problems | Mike Stonebraker
- Ingress failed as a commercial product in 1972 because it was based on a conceptually superior but commercially immature approach, whereas Oracle succeeded through aggressive sales and marketing tactics despite inferior technology, teaching Stonebraker that business success requires more than technical merit.Turing Award Winner: Disagreeing with Google, Postgres, Future Problems | Mike Stonebraker
- The commercial Ingress Corporation was founded in 1980 to move Ingress to supported platforms (VMS, DEC) and provide commercial support, becoming the pathway to commercial viability after academic prototyping had proven the relational model's validity.Turing Award Winner: Disagreeing with Google, Postgres, Future Problems | Mike Stonebraker
- PostgreSQL's core architectural innovation was implementing an extensible type system allowing users to define arbitrary custom data types with efficient support, enabling applications from GIS to financial bond calculations that could not be supported by fixed-type systems like Ingress.Turing Award Winner: Disagreeing with Google, Postgres, Future Problems | Mike Stonebraker
- Unix becoming the dominant operating system enabled Ingress to achieve wide academic adoption because it was a free database system that ran on the free, popular Unix platform.Turing Award Winner: Disagreeing with Google, Postgres, Future Problems | Mike Stonebraker
- Stonebraker's tenure at Berkeley depended on publishing significant research during his first five years; the Ingress project served as his 'ticket to getting tenure,' which was achieved in 1976.Turing Award Winner: Disagreeing with Google, Postgres, Future Problems | Mike Stonebraker
- Ingress could not efficiently support geographic information systems (GIS) because its fixed set of primitive data types (integers, floats, text strings) could not be extended to handle GIS types like points, lines, and polygons, which required custom indexing and operations.Turing Award Winner: Disagreeing with Google, Postgres, Future Problems | Mike Stonebraker
- Query optimization was the hardest part of building the original Ingress system, and it remains the most algorithmically difficult challenge in database implementation across the industry.Turing Award Winner: Disagreeing with Google, Postgres, Future Problems | Mike Stonebraker
- Ingress failed in the academic market because Arizona State University could not deploy it without COBOL support on Unix, forcing them to use an unsupported operating system, unsupported database system, and the absence of COBOL left the project unviable.Turing Award Winner: Disagreeing with Google, Postgres, Future Problems | Mike Stonebraker