<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><br id="lineBreakAtBeginningOfMessage"><div><br><blockquote type="cite"><div>On Jan 7, 2025, at 3:56 PM, Paul Ramsey <pramsey@cleverelephant.ca> wrote:</div><br class="Apple-interchange-newline"><div><span style="caret-color: rgb(0, 0, 0); font-family: HelveticaNeue; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;">The BRIN API has a lot of good stuff now, which would be good to add to simplify some of the other code (check for empty, check for contained, check for mergeable) I am not sure when in the history of BRIN it was added, do you have a quick feel for that?</span><br class="Apple-interchange-newline"></div></blockquote></div><br><div>I will answer my own question here, the extended BRIN API exists as far back as 11 at least, so “since forever” effectively for our purposes.</div><div><br></div><div><a href="https://www.postgresql.org/docs/11/brin-extensibility.html">https://www.postgresql.org/docs/11/brin-extensibility.html</a></div><div><br></div><div>P</div></body></html>