Re: Is there still password max length restrictions in PG?

Thanks Daniel.   That's a big help to me! -- Original -- From: "Daniel Gustafsson"

Re: Is there still password max length restrictions in PG?

Hi,  Thanks for your information.  Even using SCRAM,  when specified the content of "password",  still there is a basic request about the length of it.  From the source code, seems there is no restriction, right??? Is it reasonable??? BR, Sean He -

Is there still password max length restrictions in PG?

estriction for the password of a user??? Need some document to make a clarification or suggestion to the user? BR, Sean He (iih...@qq.com)

Re: PG13 fails to startup even though the current transaction is equal to the target transaction

ger, we could wait indefinitely (if the parent service has no more incoming transactions, which means no more WAL to replay). Are you recommending that we wait until another transaction happens on the parent DB? Thanks, Sean On Mon, Mar 22, 2021 at 3:59 AM Kyotaro Horiguchi wrote: > At

PG13 fails to startup even though the current transaction is equal to the target transaction

t this seems like an off by one error? What do you think? Is this a bug? Is this expected? Is this user error on our end? Thanks! Sean

Re: BUG #15781: subselect on foreign table (postgres_fdw) can crash (segfault)

Not sure if this is the right avenue to follow up on this. The patch works fine. However, we're working on a modified version of the postgres_fdw in which we're trying to push as much as possible to the remote nodes, including ordering and limits. The patch causes the upper paths for the ordering a

Re: WAL prefetch

ed down to ~8K. We have to read the entire record in before we can modify half of the page. I suspect eliding prefaulting FPWs will always be a performance loss for nearly all hardware. * If there is sufficient interest in these experiences, contact me offline (or via PostgreSQL Slack) and I