[Tickets #14964] Re: Postgresql12 dropped adsrc
[email protected] Sun, 17 Nov 2019 22:12:53 +0000
| Newsgroups | gmane.comp.horde.bugs |
|---|---|
| Message-ID | <[email protected]> |
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED. Ticket URL: https://bugs.horde.org/ticket/14964 ------------------------------------------------------------------------------ Ticket | 14964 Updated By | [email protected] Summary | Postgresql12 dropped adsrc Queue | Components Type | Bug State | Unconfirmed Priority | 1. Low Milestone | Patch | Owners | ------------------------------------------------------------------------------ [email protected] (2019-11-17 22:12) wrote: I can confirm that bug. I'm trying to fix it and I'll submit a patch ASAP on github. I've talked with the postgresql guys and it seems that that column has been deprecated for a long time and it even risked to contain stale data. They have suggested me to use pg_get_expr(adbin,adrelid), but on overall the current queries that use adsrc are a bit fragile and could use information_schema rather than interrogating pg specific columns and massaging strings. Currently I've some tentative code but I'm not able to replicate EXACTLY the return of one of the queries. namely original query return eg. nextval('public.horde_alarms_id_seq'::regclass) while mine returns nextval('horde_alarms_id_seq'::regclass) I'm going to subscribe to horde dev mailing list and propose some patch on github ASAP -- bugs mailing list Frequently Asked Questions: http://wiki.horde.org/FAQ To unsubscribe, mail: [email protected]