Just to touch on this again, this is the output of the pkg upgrade that messed
this up:
New packages to be INSTALLED:
postgresql13-client: 13.5
Installed packages to be UPGRADED:
bash: 5.1.8 -> 5.1.12
bash-completion: 2.11,2 -> 2.11_1,2
bind-tools: 9.16.22 -> 9.16
> On Jan 20, 2022, at 9:38 AM, Christoph Moench-Tegeder
> wrote:
>
> ## Dan Mahoney (free...@gushi.org):
>
>> On doing a routine pkg upgrade at the dayjob, the perl module p5-DBD-pg
>> forced an upgrade from postgresql12-client to postgresql13-client (which
>> uninstalled postgresql12-server
## Dan Mahoney (free...@gushi.org):
> On doing a routine pkg upgrade at the dayjob, the perl module p5-DBD-pg
> forced an upgrade from postgresql12-client to postgresql13-client (which
> uninstalled postgresql12-server).
p5-DBD-Pg uses the "default" postgresql version, which switched from
12 to 1
Am 20.01.22 um 14:01 schrieb Dan Mahoney:
>
>
>> On Jan 20, 2022, at 3:54 AM, Kurt Jaeger wrote:
>>
>> Hello,
>>
>> [postgres flavors]
>>> This feels like the ideal kind of port that could be flavored so
>>> it works with any installed postgres version. I'm willing to submit
>>> patches, how ha
> On Jan 20, 2022, at 3:54 AM, Kurt Jaeger wrote:
>
> Hello,
>
> [postgres flavors]
>> This feels like the ideal kind of port that could be flavored so
>> it works with any installed postgres version. I'm willing to submit
>> patches, how hard would it be?
>
> If it needs to interoperate wi
Hello,
[postgres flavors]
> This feels like the ideal kind of port that could be flavored so
> it works with any installed postgres version. I'm willing to submit
> patches, how hard would it be?
If it needs to interoperate with php flavors (which it probably
does), it's probably a high level of
