On 2023/04/18 17:24, Florian Obser wrote:
> On 2023-04-18 15:47 +02, Landry Breuil wrote:
> > Le Tue, Apr 18, 2023 at 09:04:00AM +0100, Stuart Henderson a écrit :
> >> On 2023/04/18 09:05, Landry Breuil wrote:
> >> > What do postgresql users do when upgrading databases with extensions ?
> >> > Use
On 2023-04-18 15:47 +02, Landry Breuil wrote:
> Le Tue, Apr 18, 2023 at 09:04:00AM +0100, Stuart Henderson a écrit :
>> On 2023/04/18 09:05, Landry Breuil wrote:
>> > What do postgresql users do when upgrading databases with extensions ?
>> > Use the manual dump/restore way ?
>>
>> That's what I
On 2023/04/18 15:47, Landry Breuil wrote:
> Le Tue, Apr 18, 2023 at 09:04:00AM +0100, Stuart Henderson a écrit :
> > On 2023/04/18 09:05, Landry Breuil wrote:
> > > What do postgresql users do when upgrading databases with extensions ?
> > > Use the manual dump/restore way ?
> >
> > That's what I
Le Tue, Apr 18, 2023 at 09:04:00AM +0100, Stuart Henderson a écrit :
> On 2023/04/18 09:05, Landry Breuil wrote:
> > What do postgresql users do when upgrading databases with extensions ?
> > Use the manual dump/restore way ?
>
> That's what I did last time I needed it. I thought the pkg-readme
>
On 2023/04/18 09:05, Landry Breuil wrote:
> What do postgresql users do when upgrading databases with extensions ?
> Use the manual dump/restore way ?
That's what I did last time I needed it. I thought the pkg-readme
mentioned this but I just checked and I see it doesn't so at least we
shoukd add
Hi,
recently updated one of my servers to 7.3, and in doing so updated from
psql 14 to 15. Went for the pg_upgrade path which requires
postgresql-previous, all looked fine.. until it tried dumping one of my
DBs which uses the postgis extension.
the general idea was that it failed accessing $libdi
