Re: CREATE SUBSCRIPTION fails with long passwords

From: Mike Lissner <mlissner(at)michaeljaylissner(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Paul Mansueto Namuag <paulnamuag(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: CREATE SUBSCRIPTION fails with long passwords
Date: 2019-05-28 23:41:58
Message-ID: CAMp9=EzwXkLosLjGmsLE-S5F0kUojX6j3zJcg9Sf=91ktEEO6g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

---one month passes---

Just to close this loop, because I like things closed. I wasn't able to
reproduce this in the end. I'll keep trying, but seems like I must have
mis-diagnosed the issue, I think.

Thanks for all the suggestions and help here. This kind of help and support
is so wonderful and valuable.

Mike

On Thu, Apr 25, 2019 at 6:59 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Paul Mansueto Namuag <paulnamuag(at)gmail(dot)com> writes:
> > Possibly the password might have non-ascii or something causing it to
> > unmatched but when stripped off, that non-ascii wasn't included.
>
> Oh --- another variant of that theory, if there's any non-ASCII in the
> password, is that you're getting bit by an encoding conversion issue.
> That is, whatever the client is sending is in a different encoding
> from the way the password was stored.
>
> regards, tom lane
>

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2019-05-29 14:20:22 BUG #15823: application server could not be contacted
Previous Message Nick Anderson 2019-05-28 13:24:34 RE: Re: Re: RE: Re: Re: BUG #15769: The database cluster intialisation failed.