For v11 (Disco, still going along Debian) - there rebuilds are needed.
We probably want to track those in case some syncs would be needed after the FF and auto-sync stop. I'll add a postgresql-11 task for that
One worthwhile note for v11 is that extension that use heap_getattr()
need to be recompiled (because it was broken for fast defaults). And
that extensions recompiled against v11.2 will probably not load into
earlier minor releases, because heap_getattr() will reference
getmissingattr(), which previously was static.
They already work on that quoting:
> > I'm building a lot of extensions -- is there any easy way to find out which
> > extensions are using heap_getattr()?
>
> You should be able to just grep for it. Christoph has done so for
> Debian, I think:
> https://www.postgresql.org/message-id/20190206122229.GB10563%40msg.df7cb.de
For Debian, the list is postgresql-11, postgresql-rum, pglogical,
pgextwlist, citus, postgresql-plsh, wal2json, pg-cron:
For v11 (Disco, still going along Debian) - there rebuilds are needed.
We probably want to track those in case some syncs would be needed after the FF and auto-sync stop. I'll add a postgresql-11 task for that
One worthwhile note for v11 is that extension that use heap_getattr()
need to be recompiled (because it was broken for fast defaults). And
that extensions recompiled against v11.2 will probably not load into
earlier minor releases, because heap_getattr() will reference
getmissingattr(), which previously was static.
They already work on that quoting: /www.postgresql .org/message- id/201902061222 29.GB10563% 40msg.df7cb. de
> > I'm building a lot of extensions -- is there any easy way to find out which
> > extensions are using heap_getattr()?
>
> You should be able to just grep for it. Christoph has done so for
> Debian, I think:
> https:/
For Debian, the list is postgresql-11, postgresql-rum, pglogical,
pgextwlist, citus, postgresql-plsh, wal2json, pg-cron:
https:/ /codesearch. debian. net/search? q=heap_ getattr& perpkg= 1