This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-10-11
Channels
- # beginners (57)
- # boot (9)
- # clara (9)
- # cljs-dev (12)
- # clojure (98)
- # clojure-boston (1)
- # clojure-dusseldorf (12)
- # clojure-france (1)
- # clojure-greece (1)
- # clojure-spec (41)
- # clojure-uk (86)
- # clojurescript (60)
- # code-art (2)
- # data-science (5)
- # datomic (5)
- # duct (1)
- # fulcro (14)
- # graphql (2)
- # lein-figwheel (4)
- # luminus (1)
- # midje (1)
- # off-topic (19)
- # om (10)
- # onyx (13)
- # pedestal (5)
- # portkey (59)
- # re-frame (31)
- # reagent (1)
- # ring (14)
- # ring-swagger (1)
- # rum (5)
- # shadow-cljs (90)
- # spacemacs (5)
- # specter (47)
- # sql (9)
- # uncomplicate (95)
- # vim (32)
heroku pg:outliers
is showing this at the top of the pack for me: https://gist.github.com/jeaye/65b9d35839d5152118fde4fbe78e6c19
After collecting all of my queries, I'm not issuing that anywhere. However, I also don't see it in clojure.java.jdbc
.
@jeaye No idea what that is. As you suspect, it's not coming from java.jdbc
directly (it looks like a very PostgreSQL-specific query?) but that doesn't mean it's not being triggered by the PostgreSQL driver in response to something java.jdbc
is asking it to do... Never heard of it being reported before tho'...
Thanks, sean. I did end up finding it here: https://github.com/pgjdbc/pgjdbc/blob/master/pgjdbc/src/main/java/org/postgresql/jdbc/TypeInfoCache.java#L184
Interesting. Looks like it only calls that for user-defined types tho'?