Good to know. Thank you!
On Fri, Jun 20, 2025 at 7:17 AM David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Thursday, June 19, 2025, Laurenz Albe wrote:
>
>> On Thu, 2025-06-19 at 23:05 +0200, Phillip Diffley wrote:
>> > Postgres has a to_jsonb function that will convert a value into it
Hello all,
Platform: Rocky Linux release 9.4 (Blue Onyx)
I try to migrate from version 16.7 to 17.5. When executing pg_upgrade —check I
get the following:
could not load library "$libdir/dblink": ERROR: could not load library
"/opt/postgresql-17.5/lib/dblink.so": /opt/postgresql-17.5/lib/dbl
Hello Laurenz, thanks for your quick reply.
The issue was having the old postgres library in LD_LIBRARY_PATH. Once I
removed it, everything started to look good! In all the past years this was not
a problem though. But anyway: All good now!
Thanks again: peter
> On 20 Jun 2025, at 14:00, Laur
On 6/19/25 07:54, Dominique Devienne wrote:
On Thu, Jun 19, 2025 at 4:18 PM Adrian Klaver wrote:
On 6/19/25 06:09, Dominique Devienne wrote:
Hi. Little mystery we don't understand. v17.
Does 'all' include the public schema?
No. We don't touch `public` at all, beside pgcrypto ending up insid
On Thu, Jun 19, 2025 at 8:09 AM Dominique Devienne
wrote:
> Hi. Little mystery we don't understand. v17.
>
> Create new DB, owned by dedicated new ROLE.
> Create extension (pgcrypto) in our case. Installed in public, owned by
> DB owner role.
> Create schemas and populate them inside the DB.
> Th
On Fri, 2025-06-20 at 13:49 +0200, Peter Röthlisberger wrote:
> Hello all,
>
> Platform: Rocky Linux release 9.4 (Blue Onyx)
>
> I try to migrate from version 16.7 to 17.5. When executing pg_upgrade —check
> I get the following:
>
>
> could not load library "$libdir/dblink": ERROR: could not
On Thu, Jun 19, 2025 at 6:35 PM Laurenz Albe wrote:
>
> On Thu, 2025-06-19 at 15:09 +0200, Dominique Devienne wrote:
> > Hi. Little mystery we don't understand. v17.
> > We're stumped for now.
>
> So are we. Why do you keep us guessing instead of posting a reproducer?
Hi. Simply because there's
Thanks all,
I just changed the timezone setting in postgresql.conf file. That resolved
this issue.
On Thursday 19 June, 2025 at 07:41:16 pm IST, Adrian Klaver
wrote:
On 6/18/25 23:23, sivapostg...@yahoo.com wrote:
> Hello,
> May be a very basic question. We all here are new to Linux
On 6/20/25 09:35, Dominique Devienne wrote:
> On Thu, Jun 19, 2025 at 6:35 PM Laurenz Albe wrote:
>>
>> On Thu, 2025-06-19 at 15:09 +0200, Dominique Devienne wrote:
>>> Hi. Little mystery we don't understand. v17.
>>> We're stumped for now.
>>
>> So are we. Why do you keep us guessing instead
