Thanks Daniel.
That's a big help to me!
--Original--
From:
"Daniel Gustafsson"
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
--Original-
e document to make a clarification or suggestion to the user?
BR,
Sean He (iih...@qq.com)
nitely (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 Thu, 18 Mar 2021 17:59:34
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
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
terest in these experiences, contact me offline (or
via PostgreSQL Slack) and I can setup a call to answer questions in a
higher-bandwidth setting such as Zoom or Google Hangouts.
I'm sorry for being late to the reply party, I've been watching posts in this
thread accumulate for a while and haven