On Thu, Mar 7, 2019 at 12:49 PM Andres Freund <and...@anarazel.de> wrote: > On 2019-03-07 08:52:21 -0500, Robert Haas wrote: > > On Wed, Mar 6, 2019 at 6:11 PM Andres Freund <and...@anarazel.de> wrote: > > > slot that's compatible with the "target" table. You can get compatible > > > slot callbakcs by calling table_slot_callbacks(), or directly create one > > > by calling table_gimmegimmeslot() (likely to be renamed :)). > > > > Hmm. I assume the issue is that table_createslot() was already taken > > for another purpose, so then when you needed another callback you went > > with table_givemeslot(), and then when you needed a third API to do > > something in the same area the best thing available was > > table_gimmeslot(), which meant that the fourth API could only be > > table_gimmegimmeslot(). > > > > Does that sound about right? > > It was 3 AM, and I thought it was hilarious...
It is. Just like me. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
