From: | Benedict Holland <benedict(dot)m(dot)holland(at)gmail(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | Ramesh Maddi <mymail(dot)ramesh(at)gmail(dot)com>, Luca Ferrari <fluca1978(at)gmail(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Understanding PostgreSQL installer debug log |
Date: | 2019-08-09 14:57:59 |
Message-ID: | CAD+mzox3_7Q2SK-w9od__NV7i+T064yv2=Q__i0v20y28OCP5g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
It looks like your encoding is correct. You are getting letters. If your
encoding was just wrong. You would end up with a lot of strange characters.
If this is tied to one client, it sounds like an encryption issue and
mounting drives for logging that the client cant de-encrypt.
Thanks,
~Ben
On Fri, Aug 9, 2019, 10:45 AM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
wrote:
> On 8/9/19 4:25 AM, Ramesh Maddi wrote:
> > Our product is certified along with PostgreSQL 9.6.6 only. We cannot use
> > further version of PostgreSQL at this time in production until it is
> > certified for our product( which is integrated may other components)
> > and is officially released.
> >
>
> >
> > Coming to *Luca's *question, I understand that using Yum/RPM is better
> > way of installation. That would be our future plan. But for this
> > particular issue, we need to identify debug steps.
>
> Might try the EDB forum:
>
> https://postgresrocks.enterprisedb.com/t5/EDB-Postgres/bd-p/EDBPostgres
>
> >
> > Thanks for your insight.
> > -- Ramesh
> >
>
>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com
>
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Fink (PDF) | 2019-08-09 15:03:47 | RE: pg_wal fills up on big update query |
Previous Message | Luca Ferrari | 2019-08-09 14:50:05 | Re: Updating 3-table dataset |