>
> Yes. Looks like the DBD::Pg module is what needs the upgrade.
>
Specifically, you will need DBD::Pg version 3.9.0 or higher, but I *highly*
recommend using the latest release you can (right now, that is 3.18.0)
Cheers,
Greg
, but when I connect and perform
>> some tasks in the app, I get:
>>
>> ERROR: column d.adsrc does not exist at character 331
>>
>> Some searching online yields that adsrc was removed in Pg 12.
>>
>
> 1. What is the application?
>
Netdot - an IPAM
OR: column d.adsrc does not exist at character 331
>
> Some searching online yields that adsrc was removed in Pg 12.
>
1. What is the application?
2. An upgraded version of the application (or at least the db driver)
probably won't reference it.
--
Death to , and butter sauce.
Don't boil me, I'm still alive.
lobster!
On Tue, Nov 5, 2024 at 2:45 PM Matt Zagrabelny wrote:
> ERROR: column d.adsrc does not exist at character 331
>
> Some searching online yields that adsrc was removed in Pg 12.
>
> Is there a way to recreate it?
>
>
That is a base catalog table. Its removal means the data i
## Matt Zagrabelny (mzagr...@d.umn.edu):
> I'd like to upgrade the database to Pg 15, but when I connect and perform
> some tasks in the app, I get:
>
> ERROR: column d.adsrc does not exist at character 331
That pg_attrdef.adsrc was already marked as "historical, and is best
not used" in 9.4: h
Greetings Pg folk,
I've got a legacy app connecting to a legacy Pg database (9.4).
I'd like to upgrade the database to Pg 15, but when I connect and perform
some tasks in the app, I get:
ERROR: column d.adsrc does not exist at character 331
Some searching online yields that adsrc w
