On Sun, Jan 17, 2021, at 21:32, Tom Lane wrote:
>Well, SGML is actually plenty easy to parse as long as you've got xml
>tooling at hand. We'd never want to introduce such a dependency in the
>normal build process, but making something like findoidjoins depend on
>such tools seems within reason. I
"Joel Jacobson" writes:
> A bit of background:
> I'm working on an extension where I need SQL access to this reference
> information. My extension is successfully automatically helping me to
> find problems in extension update-scripts, where an update from a
> version to a version would give a di
On Sun, Jan 17, 2021, at 18:16, Tom Lane wrote:
> I kind of wonder whether findoidjoins has outlived its purpose and
> we should just remove it (along with the oidjoins test script).
A bit of background:
I'm working on an extension where I need SQL access to this reference
information.
My extensi
"Joel Jacobson" writes:
> The below references are already properly documented in
>https://www.postgresql.org/docs/current/catalog-pg-event-trigger.html
> but missing in src/tools/findoidjoins/README.
> Join pg_catalog.pg_event_trigger.evtowner => pg_catalog.pg_authid.oid
> Join pg_catalog.pg_
The below references are already properly documented in
https://www.postgresql.org/docs/current/catalog-pg-event-trigger.html
but missing in src/tools/findoidjoins/README.
Join pg_catalog.pg_event_trigger.evtowner => pg_catalog.pg_authid.oid
Join pg_catalog.pg_event_trigger.evtfoid => pg_cata
