David Steele
Senior Data Architect at Crunchy Data Solutions
David Steele is Principal Architect at Crunchy Data, the Trusted Open Source Enterprise PostgreSQL Leader. He has been actively developing with PostgreSQL since 1999.
David loves taking on big data challenges. Before Crunchy Data he was Data Architect at Resonate, an online media company using PostgreSQL to drive its transactional and data warehousing databases. Before that, he helped drive global mobile text messaging at Sybase365.
David's current project is pgBackRest, which will be the subject of this talk.
Upcoming presentations
No upcoming presentations...
Past presentations
Backups are a critical part of any enterprise database solution but they are often done poorly or skipped altogether, which can lead to data loss in the event of hardware failure or some other disaster. With the proper tools and procedures data loss can be minimized or entirely avoided, saving valuable enterprise data and time.
In this talk we'll cover database backup best practices and how ...
Nov 20 2020
Many of us have had auditors ask for information that is difficult to provide with core PostgreSQL. Who made changes to table X in the last six months? When was table Y's DDL last modified and was that during a maintenance window? Who has viewed table Z? An extension available for PostgreSQL 9.5, pgAudit, seeks to answer these and many other questions by providing more detailed logging and fine...
pgBackRest is open source software developed to perform efficient backup on PostgreSQL databases that measure in tens of terabytes and greater. It supports per file checksums, compression, partial/failed backup resume, high-performance parallel transfer, asynchronous archiving, tablespaces, expiration, full/differential/incremental, local/remote operation via SSH, hard-linking, restore, and mor...
There are many advantages to maintaining full build scripts for your database. They allow you to create your database from scratch, run unit tests, and serve as a useful reference to the current state of the database. However, in production full build scripts are only run once per database. After that it is an endless sequence of update scripts. How do you to keep the full build and update scri...